Introduction
Every Bitcoin wallet rests on a simple promise: a human-readable phrase can reliably regenerate every private key the wallet will ever use. Achieving that promise at scale required a carefully designed standard. BIP32, the Bitcoin Improvement Proposal that introduced hierarchical deterministic (HD) wallets, made it possible to derive an entire tree of keys from a single seed. When paired with BIP39 mnemonic phrases and the derivation paths defined in BIP44, these ideas form the backbone of most modern wallets. MultiBit, one of the earliest desktop Bitcoin clients, offers a useful lens for understanding how these components fit together in practice.
From Mnemonic to Master Seed
A BIP39 mnemonic is a sequence of words, typically 12, 15, 18, 21, or 24, drawn from a fixed wordlist of 2048 entries. Each word encodes 11 bits, and the final word includes a checksum derived from the entropy. The mnemonic is not itself a private key. Instead, it is stretched through PBKDF2 with HMAC-SHA512, using 2048 iterations and the salt string "mnemonic" followed by an optional passphrase. The output is a 512-bit seed.
This seed is the root of everything that follows. Anyone holding the seed can derive every key in the tree, which is why the mnemonic must be stored with the same care as a private key. The optional passphrase acts as an additional secret: a different passphrase yields a completely different seed, and therefore a completely different wallet, even when the words are identical.
The BIP32 Master Key
BIP32 takes the 512-bit seed and runs it through HMAC-SHA512 keyed with the string "Bitcoin Seed". The left 256 bits become the master private key, and the right 256 bits become the master chain code. The chain code is what allows child keys to be derived without revealing the parent. Together, the key and chain code form an extended private key, or xprv.
From this master node, child keys are generated by combining the parent's key material with an index number. BIP32 defines two child derivation types. Normal derivation uses a public index below 2^31, allowing the parent public key to derive child public keys without the private key. Hardened derivation uses an index at or above 2^31, which requires the parent private key and prevents a leaked child key from exposing the parent chain.
Understanding Derivation Paths
A derivation path describes how to walk the tree from the master node to a specific key. It is written as a sequence of indices separated by slashes, beginning with the letter m for the master node. An apostrophe, or the letter h, marks a hardened index.
BIP44 standardized a five-level structure:
- m / purpose' / coin_type' / account' / change / address_index
- purpose is 44 for BIP44 wallets
- coin_type is 0 for Bitcoin mainnet and 1 for testnet
- account separates logical sub-wallets
- change is 0 for receiving addresses and 1 for change addresses
- address_index increments for each new address
A typical first receiving address on Bitcoin mainnet therefore follows m/44'/0'/0'/0/0. Later BIPs introduced alternatives, such as BIP49 for nested SegWit (m/49') and BIP84 for native SegWit (m/84'). Choosing the correct purpose field matters, because a wallet that expects one path will not discover funds held under another.
MultiBit and Path Compatibility
MultiBit Classic and MultiBit HD approached wallet recovery with the same underlying principles, but their historical behavior illustrates a common pitfall. Recovering a wallet requires not only the correct mnemonic but also the correct derivation path and script type. If a seed was generated by a wallet using m/44' and the recovery tool scans only m/84', the balances will appear empty even though the keys are valid. Users who migrate between wallets should confirm which path their original software used before concluding that funds are lost.
The same caution applies to passphrases. A mnemonic restored without its passphrase produces an unrelated wallet with no visible funds. Verifying the first receiving address against a known value is a reliable way to confirm that the phrase, passphrase, and path all match.
Practical Recovery Checklist
- Confirm the mnemonic length and spelling against the original backup
- Record whether a passphrase was used, since it cannot be recovered from the words alone
- Identify the purpose field, typically 44, 49, or 84, used by the original wallet
- Verify the coin type, which is 0 for Bitcoin mainnet
- Derive the first receiving address and compare it with a previously used address
- Scan several accounts and address indices before assuming the wallet is empty
Security Considerations
Mnemonic phrases should never be typed into websites, shared with support staff, or photographed and stored in cloud services. Offline storage on durable material is preferable to digital copies. Because hardened derivation protects parent keys, wallets that export extended public keys for watch-only use reduce exposure, but xpub holders can still see every address and transaction in the account, so these should be treated as sensitive.
Conclusion
BIP32 derivation paths and BIP39 mnemonics work together to turn a handful of words into an entire hierarchy of keys. Understanding the seed, the master node, and the path structure makes wallet recovery far less mysterious. For MultiBit users and anyone working with HD wallets, the most important habits are precise record keeping, careful path selection, and verification before assuming funds are gone.