What is HD wallet (hierarchical deterministic)?

A wallet that derives every address it will ever use from a single seed, so one backup restores the whole set.

Not yet verifiedHow we verify

3 min read

In this entry

A wallet that derives every address it will ever use from a single seed, so one backup restores the whole set.

This is why modern wallets hand you a recovery phrase rather than a file of separate keys, and why they can generate a fresh receiving address each time you are paid. Essentially every wallet you will encounter today works this way, whether it is a phone app, a browser extension, or a hardware device.

The point people miss is what this means for backup discipline. Because every key descends from one seed, that seed is the entire wallet, forever, across every account and every chain the software supports. There is nothing else to back up and nothing else worth stealing.

How it works

The design comes from BIP-32, which specifies hierarchical deterministic wallets, paired with BIP-39, which specifies the human-readable mnemonic, and BIP-44, which specifies the path layout most wallets follow.

  1. A random number becomes the seed, and BIP-39 encodes it as a word list with a checksum in the final word.
  2. The seed produces a master key, and a one-way derivation function turns that master key plus an index into a child key. Repeat, and you have a tree.
  3. BIP-44 gives the tree a convention: purpose, coin type, account, change, and address index. A path like m/44'/0'/0'/0/5 means the sixth receiving address of the first Bitcoin account.
  4. Because derivation is deterministic, restoring the seed in any compatible wallet regenerates the same tree in the same order.

A useful property is that a public branch can be shared without the spending keys. An extended public key, usually called an xpub, lets software generate every receiving address for an account and watch them, while signing remains impossible. Exchanges and merchant systems use this to issue fresh deposit addresses without holding keys on a web server. The privacy cost is real: anyone holding your xpub sees your whole balance and history for that branch.

Example

Illustrative walkthrough. You set up a wallet, write down twelve words, and receive three payments to three different addresses. Your phone is destroyed. You buy a different brand of hardware wallet, enter the same twelve words, and the software rederives the same tree, scans the chain for those addresses, and shows the same balance. No file was copied. Nothing was exported. The twelve words were the wallet all along.

Why it matters when you buy

When you withdraw from an exchange to your own wallet, the address you paste is one leaf of this tree, and using a fresh one each time is normal rather than a sign of anything going wrong. Budget the withdrawal cost, which sits outside trading fees and varies by venue on the fee comparison. The first crypto wallet guide and seed phrase backup methods cover the setup and the backup properly.

  • seed phrase: the words that encode the seed
  • bip 39: the mnemonic standard behind them
  • xpub: a public branch used for watch-only access
  • watch only wallet: tracking balances without spending keys
  • private key: the individual key each leaf holds
  • passphrase: an optional extra word protecting the seed

Questions

Why does my wallet keep giving me a new address?

Reusing one address links all your activity publicly. A hierarchical wallet can produce a fresh address for each payment and still restore them all from the same phrase.

Can I restore my wallet in different software?

Usually yes, provided both follow the same standards and derivation path. If a balance is missing after restoring, the most common cause is the new wallet defaulting to a different path.

Is one phrase enough to back up multiple coins?

For wallets that support several chains from one seed, yes. Each chain occupies a different branch of the same tree, so the single phrase restores all of them.