Recovery methodsTechnical

Wallet Seeds, Derivation Paths and Account Reconstruction

A recovered seed phrase and a recovered wallet are not the same thing — the software still has to walk the same branch of the same key tree the original wallet used.

A seed is the root of a tree, not an address

Modern wallets are usually hierarchical deterministic (HD) wallets, defined by BIP32: a single master seed can generate an entire tree of child keys, addressed by a derivation path such as m / purpose’ / coin_type’ / account’ / change / address_index. Knowing the seed identifies the root of that tree; it does not by itself say which branch the original wallet actually used, and a different branch produces completely different, equally valid addresses with no error at any point.

BIP39 mnemonics and the passphrase that is not a password

BIP39 turns a mnemonic sentence — commonly 12 or 24 words from a fixed 2048-word list — into a seed through a one-way derivation that also accepts an optional passphrase. That passphrase is not a password wrapped around an already-fixed seed; it participates in creating the seed itself, so a different passphrase produces a different wallet, and an empty passphrase is used whenever none is supplied. A wallet password, by contrast, usually just encrypts a locally stored copy of key material and does not change the underlying deterministic wallet at all — recovering one is not a substitute for the other.

Password vs. passphrase

A wallet password usually decrypts stored data. A BIP39 passphrase changes the deterministic wallet derived from the seed. A wrong passphrase commonly produces a valid but empty-looking wallet instead of an error.

Electrum and SLIP39 are not BIP39

A phrase built from familiar English words is not automatically a BIP39 mnemonic. Electrum uses its own seed-versioning scheme to tell its software which derivation logic to apply, and a phrase it rejects as invalid BIP39 may still be a perfectly valid Electrum seed. SLIP39 (Shamir) backups split a master secret into multiple mnemonic shares with a configured threshold, and are generally not compatible with BIP39 at all — “I still have two seed cards” means nothing until the threshold and the share set are known.

Derivation paths decide which addresses appear

For Bitcoin specifically, BIP44 (legacy), BIP49 (nested SegWit), BIP84 (native SegWit) and BIP86 (Taproot) each define a different account-tree convention, and wallet software that does not support a given standard will not automatically discover accounts built on it. Altcoins can use different coin types or wallet-specific conventions again. The account index, the change branch and the address-index gap all matter too — restoring correctly to the wrong account looks identical to restoring an empty wallet.

Imported accounts are not backed up by the seed

Many wallet applications mix deterministic accounts derived from the main seed with individually imported private keys, accounts from a separate seed, hardware-wallet accounts and watch-only addresses. A seed backup only restores the first category. Before concluding a seed recovery failed, ask specifically whether any account was imported from a private key, a JSON file, another phrase or a hardware wallet — MetaMask’s own support documentation is a clear, well-documented example of exactly this distinction.

Diagnosing an empty wallet

When a correct-looking seed restores to nothing, check in order: the derivation path and account convention the original wallet used, the account index and address type, whether a passphrase was involved, and whether any of the expected accounts were actually imported rather than derived. Confirm success against a known address, xpub or transaction — not against the absence of an error message.