How to Prepare a Wallet Access Plan for Your Heirs
Plan wallet recovery for your heirs with a private inventory, offline backups, passphrase requirements and practical steps to verify access.

An inheritance plan for a wallet combines a private inventory, recovery instructions and controlled access to the necessary backups. It should let an authorized person locate the correct backup, identify its format and follow the official procedure when appropriate. Technical access alone does not establish who has a legal right to the funds.
Bitcoin.org recommends thinking about a testament and making a plan so family members know how to access backups. This guide turns that idea into a maintainable technical inventory without assuming a particular jurisdiction or promising that a document replaces a succession process.
What the authorized person should be able to find
Start with an inventory sheet that contains neither the recovery words nor a passphrase. It should answer these questions:
- Which wallets, devices and accounts exist, and which manufacturer or official application is associated with each one.
- Which networks and assets each account uses, and which public addresses identify it.
- Which backup standard applies: for example, a BIP39 mnemonic or a compatible SLIP39 backup.
- How many words the backup has, its language and whether an additional passphrase was used under that standard.
- Where each physical backup is kept, which controlled access procedure applies and when the inventory was reviewed.
- Whether an account was imported with a private key or xprv, a watch-only xpub or a multisignature configuration that needs its own backup.
A public address helps confirm that recovery shows the expected account, but it cannot recover a private key. Record a complete address and its network in the inventory without treating it as a secret. You can also record the account, derivation path, address type and index used for the comparison. The guide to why the same seed phrase can show different addresses explains why these details matter.
The inventory must contain no private keys or xprv. An xpub allows activity monitoring, but cannot sign or spend. Identify imported accounts that need their own backup. For multisignature wallets, record the policy, threshold, configuration and how to locate the necessary signer backups separately.
Keep the inventory private: it links holdings, accounts and backup locations, even though it cannot authorize spending. Plan how the instructions will be found if the main contact becomes unavailable.
Separate inventory, instructions and secrets
Someone may need to know that a passphrase exists without finding it next to the words. A BIP39 passphrase is an additional input: a different word, space or capital letter can open another valid and apparently empty wallet. It is not the device PIN, an application password or the SeedAddress input password. State where the plan stores it, but never put a real passphrase in an ordinary email or an unprotected note.
Instructions can describe the order of operations without copying secrets. For example: identify the manufacturer, read its official documentation, restore the exact backup format on a compatible device, check the network and compare a recorded public address before signing or moving funds. Trezor explains its 12-, 20- and 24-word wallet backups, and Ledger documents how to protect a recovery phrase. Always use the current documentation for the specific device.
Do not turn a manual split of words into a supposed threshold backup. Storing fragments in separate places can leave the backup incomplete and reveal part of the secret. If you need a multi-part scheme, use a compatible format whose reconstruction rules are documented; splitting BIP39 words by hand does not create that protection.
Write down the recovery procedure
The plan should still be useful if the original device no longer works:
- Confirm which backup belongs to the wallet and do not combine words from different backups.
- Verify the standard, word count, language and passphrase without entering any secret into a website, chat or online checker.
- Follow the manufacturer's official flow on a compatible trusted device. Never send the words to a repair service or to someone promising to recover funds.
- Check the network, account, address type and derivation path. Compare a complete public address already recorded in the inventory.
- Review imported accounts, multisignature wallets and assets on other networks as well. Restoring a phrase does not automatically include a private key imported later. For multisignature wallets, check the policy, threshold, configuration and signer backups required by the software.
- Keep the original device and backup available until recovery and every relevant account have been verified.
A BIP39 backup can restore a compatible wallet, but it does not necessarily contain multisignature rules, participants, labels or every imported account. The inventory should point to those details without including private keys, xprv or cleartext phrases. If a backup has been exposed, assess the incident and, when appropriate, migrate to a new wallet created from random entropy; changing a PIN or application password does not rotate keys that can already be derived.
What changes when you use SeedAddress
SeedAddress has a different recovery boundary. Its v1 flow derives a BIP39 mnemonic locally from the selected coordinates, the input password, the word-list language and the requested word count. It uses a precision-9 geohash and HMAC-SHA-256. The public location adds no random entropy, so a 24-word output does not guarantee 256 bits of random security; the inherited five-character minimum exists for compatibility and is not a recommendation for a new password.
A SeedAddress plan should keep an independent offline copy of the mnemonic and the exact inputs required to reproduce it. Record the selected coordinates rather than only the visible place name, because a later search may return another point. Record the exact language and word count. A location or address alone cannot recover the wallet, and reproducing the input is not a substitute for an offline backup.
SeedAddress does not generate the wallet's private keys or addresses, and its input password does not automatically become a BIP39 passphrase. The authorized person must follow the recovery procedure for the wallet that received the mnemonic. The SeedAddress recovery guide details the inputs; the migration guide explains how to move to a wallet created with random entropy if these limits do not fit the intended use.
Review the plan and check the backups
Update the inventory when you add an account, change devices, use a new passphrase or move a physical backup. Record the date and remove outdated locations. Reviewing links and addresses checks documentation and account identification, but does not prove that the backup is recoverable.
You can rehearse the procedure with an empty practice wallet kept separate from the funds. To verify the real wallet's backup, its owner can use the device's official backup-check feature, if available, following the manufacturer's instructions. Keep the original device and backup available, and ensure that the review does not expose secrets to other people.
The authorized person should know what to do if a backup is missing or the device is locked: preserve it, do not reset it or guess PINs, and identify available access paths first. If a phrase appears in a photograph or online service, treat that as a separate incident, do not share the words and follow the appropriate process before deciding whether migration is needed. The guide to an exposed seed phrase explains why changing a local password is not enough.