A wallet backup is a recovery plan

Inherited archive entry · retained from the earlier edition. Its factual, legal and policy claims have not all been reverified for 19 September 2026. Research scope.

Start with what can authorize a payment

A wallet is an arrangement for managing keys and constructing transactions. A displayed balance is not the thing that authorizes a transfer; signing material is. The Bitcoin developer guide describes full-service, signing-only, and hardware-wallet arrangements and explains how hierarchical deterministic wallets derive many keys from a root. Those distinctions matter when a device fails or a provider disappears.

Why one seed changed backups

BIP32 specifies a tree of related keys derived from a root. In a compatible setup, preserving the right root and derivation information can recover keys created later, instead of requiring a fresh backup for every new address. That is an operational gain. It also concentrates risk: someone with the relevant private root can derive spending keys, while an owner who loses it may lose the only recovery path.

The phrase 'I have the seed' can conceal missing details. Wallet software may use different mnemonic formats, derivation paths, passphrases, account structures, scripts, or additional signers. The developer guide's statement about a root seed is explicitly tied to a particular wallet program and settings. A generic phrase found in a drawer does not establish that the intended accounts can be restored in the intended software.

Separate resilience from secrecy

A single copy can be lost to fire, water, accident, or simple misplacement. Multiple copies can reduce that risk while increasing exposure to theft or disclosure. The correct balance depends on the actual threat model and on the value at risk; no universal storage trick resolves both sides. For a shared-control wallet, a recovery plan must also account for the required number of signers and what happens if one is unavailable.

Do not conduct a 'recovery test' by typing a live secret into an unfamiliar website or sending it to someone offering help. A legitimate editorial correction or support inquiry can describe the wallet version and symptoms without revealing private material. Use the wallet vendor's current official procedure and a controlled environment for any actual restoration. This article cannot verify a reader's particular configuration or guarantee that a chosen backup is complete.

A written plan without the secret

• Which wallet implementation, version, account type, and recovery procedure apply?
• What material is needed beyond the seed, such as a passphrase or co-signer?
• Who can find the procedure if the owner cannot act, without casually exposing the secret?

The most useful record is a map of dependencies kept apart from the keys themselves. Self-custody moves responsibility from a service to a person and their process. That can be a deliberate choice; it does not make mistakes reversible.