Wallet Backup: Seed vs Descriptor

A wallet backup protects your ability to recover funds, but not all backups capture the same information — and the gap between a seed backup and a descriptor backup has cost people real money. A seed phrase, typically twelve or twenty-four words, encodes the master private key from which every address is derived. That is necessary, but on its own it does not record how the keys are used: which script type, which derivation paths, how many cosigners, or how far along the address chain you have travelled. Two different wallets can derive completely different addresses from the same seed, and a recovery performed with the wrong assumptions can show a zero balance while your coins sit untouched on paths the software never checked.

What the Seed Actually Encodes

A BIP39 seed deterministically generates a master key, and standardized derivation paths then branch it into accounts and addresses — different standards for legacy, wrapped-SegWit, native SegWit, and Taproot script types, each yielding an entirely separate address universe. Add an optional passphrase and the same words open a different wallet again. Most single-signature wallets follow common conventions closely enough that recovery usually works, but "usually" is doing heavy lifting: nonstandard paths, forgotten passphrases, and script-type mismatches are the classic recovery failure modes.

What a Descriptor Adds

An output descriptor closes that gap. It is a compact text string that explicitly records the script type, the key-origin fingerprints, the derivation paths, and — for multisig — every cosigner's public key, finished with a checksum that catches transcription errors. Restoring from a seed plus its descriptor removes the guesswork: the recovering software knows exactly which addresses to derive and watch, so it cannot pick the wrong script type or, thanks to correct chain information, silently miss funds beyond the gap limit. For multisig setups the descriptor is not optional. The seed alone recovers only your key; without the other cosigners' public keys, recorded in the descriptor, you cannot even reconstruct the addresses, let alone spend from them. Modern descriptor wallets make this explicit by using descriptors as their native accounting language.

A Complete Backup Strategy

Treat the seed and the descriptor as two layers of one backup with very different secrecy requirements. Seed words are the secret: store them on durable media — steel outlasts paper and house fires — kept private and geographically distributed, and never photographed or typed into an internet-connected device. The descriptor contains only public keys, so while it does reveal your wallet structure and harm privacy if leaked, it cannot spend your coins; it can therefore be copied more freely — alongside your recovery instructions, with your estate documents, or loaded into a watch-only wallet that monitors balances without any spending power. Optionally export your UTXO labels via the BIP329 format so your bookkeeping context survives a restore too. Test the whole stack: a backup you have never restored from is a hypothesis, not a backup.

The principle is simple, and worth engraving next to the seed itself: a seed recovers your coins, a descriptor recovers your wallet, and labels recover your understanding of both. Self-custody is only as strong as the recovery path you have actually verified — build all three layers before you need any of them.

A concrete workflow makes the theory stick. When you create a wallet, export the descriptor immediately — most modern software exposes it in settings or via a command — and file it with your recovery instructions before the first deposit lands. When you change anything structural (a new account, an added cosigner, a migrated script type), re-export, because a stale descriptor quietly stops describing your wallet. And once a year, restore the whole stack — seed, descriptor, labels — onto a spare device and confirm the addresses and balance match. Ten minutes of drill converts your backup from an assumption into a fact, which is the only kind of backup worth having.