BIP-32, BIP-39 and BIP-44: The Layers Behind a Seed Phrase

Write down twelve or twenty-four words, keep them safe, and any compatible wallet can restore your funds. That is the promise, and it mostly holds. When it does not, the cause is nearly always a mismatch between the layers the phrase actually depends on — because the words alone do not fully determine which addresses a wallet will look at.

BIP-39: words to a seed

BIP-39 defines how a mnemonic phrase encodes entropy and converts to a binary seed. The wordlist is fixed at 2048 words chosen so the first four letters are unambiguous, which is why some wallets accept truncated input.

The phrase includes a checksum, which is why a single mistyped word is usually caught rather than silently producing a valid-but-different wallet. It is a safety net rather than a guarantee: a small fraction of wrong phrases pass the checksum, and those restore a real, empty wallet with no error.

The conversion from words to seed also takes an optional passphrase. With no passphrase, an empty string is used. Any passphrase produces a completely different seed — that is the mechanism behind so-called hidden wallets, and the reason a forgotten passphrase is unrecoverable.

BIP-32: one seed, unlimited keys

BIP-32 turns that single seed into a tree of keys. From one master key, any number of child keys can be derived deterministically, so a wallet can generate a fresh address for every transaction while only ever backing up one secret.

Two properties are worth knowing. Extended public keys allow a watch-only wallet to derive all your receiving addresses without any ability to spend — the basis of monitoring a cold wallet from a phone.

And hardened derivation exists because non-hardened child keys have an unfortunate property: an extended public key combined with any one child private key reveals the parent private key. Hardened derivation blocks that, which is why account-level paths use it.

BIP-44: where in the tree to look

A tree with unlimited branches is only useful if wallets agree where to look. BIP-44 defines a standard path structure — purpose, coin type, account, change, index — so that any conforming wallet derives the same addresses from the same seed.

This is the layer where compatibility actually breaks, because BIP-44 was followed by further standards for newer address types, each with its own purpose value. A wallet that derives one type from your seed will not show balances held under another, even though the seed is identical and everything is working correctly.

That is the mechanism behind the most common self-custody scare: a correct phrase, a correct wallet, and an empty balance. Nothing is lost. The wallet is looking in a different part of the tree, and pointing it at the right derivation path restores the view.

Where compatibility actually breaks

• Different derivation path — the wallet defaults to a different address type from the one your funds sit under. Most common, entirely recoverable.
• A passphrase you forgot you set, including one entered by accident. Produces a valid but different wallet with no error message.
• A non-standard wordlist or a wallet that never used BIP-39 at all. Older and bespoke wallets exist that do not.
• Account gaps — funds on an account index beyond where the wallet stops scanning, so the balance is real and invisible.
• Address gap limits, where a long run of unused addresses causes the wallet to stop looking before it reaches funds.

What to record alongside the words

The practical conclusion is that a seed phrase alone is an incomplete backup. Recording a few extra facts costs nothing and removes almost every recovery failure that is not simple loss.

Note the wallet software and device the phrase was created on, the derivation path if the wallet displays it, whether a passphrase is in use and where it is stored separately, and the first receiving address. That last item is the cheapest verification available: if a restore produces a different first address, you know immediately that something is wrong, before you conclude the funds are gone.

Testing a restore on a spare device before funding a wallet is the other habit worth building, and it is the one that converts all of this from theory into something you have actually done.