HD Wallet (Hierarchical Deterministic Wallet)

A Hierarchical Deterministic (HD) wallet is the standard Bitcoin wallet design where every key the wallet will ever need is deterministically derived from a single root seed. Back up the seed; you've backed up everything.

The structure, defined in BIP 32:

• A single seed (typically 12 or 24 BIP 39 words) plus optional passphrase produces a 512-bit master seed.
• The master seed splits into a master private key and a master chaincode.
• Children are derived by HMAC-SHA512 keyed with the parent chaincode over the parent key and the index; the left half of the output is added to the parent key to make the child key, and the right half becomes the child's own chaincode. Each child is itself a parent that can derive its own children. This forms the tree.
• Standardized paths (BIP 44 for legacy, BIP 49 for wrapped SegWit, BIP 84 for native SegWit, BIP 86 for Taproot) tell wallets exactly where to look for addresses.

Why HD wallets dominate:

• One backup covers everything. Write down 12 or 24 words, and you've backed up every address your wallet will ever generate, across every account, indefinitely.
• Cross-wallet portability. Import a BIP 39 seed into any standards-compliant wallet (Sparrow, BlueWallet, Electrum, Trezor, anything) and get the same addresses.
• Watch-only support. Hand someone the xpub (extended public key) and they can derive every receive address without ever seeing private keys. Useful for accounting, monitoring, watch-only mobile apps backed by hardware wallets.
• Multi-account separation. The BIP 44/84/86 path structure includes an account level so users can maintain logically separated wallets (account 0 for personal, account 1 for business, etc.) from a single seed.
• Hardware wallet integration. The hardware device holds the seed; software wallets only see the xpub. The standardized derivation paths mean any compatible software pairs with any compatible hardware.

What HD wallets aren't:

• A privacy panacea. An xpub is a parent public key plus its chaincode, and from those two pieces anyone can derive every non-hardened child below it (each child gets its own chaincode, computed from the parent's, so the whole branch unrolls). Leak it and whoever holds it sees every address in the branch, past and future.
• A reason to hand out xpubs freely. BIP 32 adds a sharper warning: "knowledge of a parent extended public key plus any non-hardened private key descending from it is equivalent to knowing the parent extended private key". Leak one child private key next to a leaked xpub and the holder has the branch's spending keys, not just its addresses. Hardened derivation (used for the top levels of the path) stops this from climbing further up the tree. And an xpub is key material in the quantum sense too: BIP-360 notes that xpubs and wallet descriptors "also reveal quantum vulnerable public key information", so handing one to a server is public key exposure for every address under it, used or not.
• A backup replacement. The seed is still a single point of failure. Lose the seed, lose everything. Hardware wallets and multisig setups add resilience layers on top of HD.

HD wallets became universal around 2014-2016 as BIP 32 / 39 / 44 implementations matured. Today, essentially every wallet worth using is an HD wallet, and "the seed" is the universal backup primitive.