In this guide

Bitcoin

Bitcoin inheritance: what to preserve

The Bitcoin-specific inheritance picture: keys, seed standards, software wallets, UTXO reality, and how preservation differs from exchange accounts.

Bitcoin is a common example of self-custody crypto in an estate, and it behaves differently from exchange balances. Understanding what the artefacts actually are determines what can be preserved and what cannot.

The artefacts

  • Seed phrase (recovery words), many Bitcoin wallets use BIP-39 recovery phrases of 12, 15, 18, 21 or 24 words, but not all Bitcoin wallets use BIP-39; Electrum, for example, uses its own seed format, and older wallets may use wallet-specific formats. First identify the original wallet and seed format before attempting recovery. Whoever holds the words can derive the keys. Found on paper, metal, or in a password manager.
  • Private keys / extended keys, older wallets may hold keys directly (wallet.dat files, exported keys). Not standard practice today but common in older estates.
  • Hardware wallet — the device keeps the keys offline. Depending on the model and configuration, a device that still works can provide access with the correct PIN, or recovery material may be needed to restore the wallet on compatible hardware. If an extra passphrase was used for the wallet concerned, that may also be needed. So preserve the device and all the recovery material found, securely and appropriately.
  • Software wallet files, desktop/mobile wallet data, browser wallets, wallet.dat from legacy clients.
  • Passphrase, an extra word or phrase on top of the seed (BIP-39 passphrase). Without it, the seed phrase alone is insufficient. Heirs rarely know it exists.
  • Lightning wallet or node? Do not automatically treat a Lightning wallet or node like an ordinary on-chain Bitcoin wallet. Depending on the implementation, channel backups, recovery files, wallet or node data, or other implementation-specific data may be necessary in addition to key material. For a self-hosted Lightning node, preserve the complete original node or app data unchanged, and identify the implementation used before attempting recovery.

What Bitcoin inheritance involves

  • Limited support. There is no exchange to call for self-custody Bitcoin; support may exist, but there is usually no central party that can simply restore access. What is possible depends on the wallet used and the configured recovery method; the estate’s access depends on what was left behind.
  • Keys, not accounts. Keys provide the ability to sign transactions and control the crypto; they do not by themselves establish legal ownership. Possession of a device is not possession of the keys.
  • UTXO reality. Bitcoin value is represented in UTXOs locked by spending conditions; spending them requires meeting those conditions, often with one or more valid cryptographic signatures and sometimes with additional script conditions; a “balance” is an interpretation of the chain, not a ledger line (see why a visible wallet balance does not prove access or ownership).
  • The wrong move can be irreversible. One reset, one firmware update, one batch of wrong guesses can lock or destroy the only access.

The inheritance sequence

  1. Preserve everything exactly as found, devices, papers, drives (preservation checklist).
  2. Identify the artefacts, is it an exchange account, a hardware wallet, words, a file? (what did I find?)
  3. Establish authority before attempting anything (legal authority vs technical access).
  4. Only then plan access, and if access is genuinely blocked, read wallet recovery: what is realistically possible before contacting anyone.

Planning ahead

If you own Bitcoin, the standards to plan around are the same ones in crypto inheritance planning and, for multi-key setups, bitcoin multisig inheritance.

What matters

  • Recovery words are often crucial, but also preserve the original device and other wallet data. If the recovery words are missing, a device that still works with the correct PIN can remain an access route. If access to the device is also missing, the absence of the recovery material becomes much more important. The words alone are not enough in every configuration to rebuild the wallet (for example with a BIP-39 passphrase or Lightning). Keep the device, the words and other wallet data as separate secrets.
  • The passphrase is the hidden variable. If a passphrase was set on top of the seed (BIP-39), the seed alone opens a different, usually empty, wallet. Heirs rarely know it exists, preserve any separate note or hint.
  • A visible balance is not access. A watch-only wallet or a block-explorer page shows funds but cannot spend them (why a visible wallet balance does not prove access or ownership).
  • The seed standard matters. BIP-39 is widely used, but Bitcoin wallets may also use Electrum seeds, legacy wallet-specific formats or other recovery constructions; SLIP-39 uses multiple shares and is yet another recovery model. First determine the format before entering or testing words (wallet recovery: what is realistically possible).

Sources and useful links

  1. Bitcoin Core, managing wallets (wallet.dat)Source accessed: 2026-08-09
  2. BIP-39, Mnemonic code for generating deterministic keysSource accessed: 2026-08-09