The relationship between a recovery phrase and the addresses it controls follows a specified process, and understanding it resolves most recovery confusion.
Entropy to phrase
Random data is encoded as words from a defined list, with a checksum.
Which makes the secret human-transcribable and catches transcription errors.
The word list is standardised, so a valid phrase can be checked without knowing the wallet it came from.
Phrase to seed
The phrase is stretched into a seed through a key derivation function, optionally with a passphrase.
Which means the passphrase produces an entirely different seed rather than acting as a password.
There is no way to detect a wrong passphrase — it simply produces different, empty accounts.
Hierarchical derivation
The seed generates a master key, from which a tree of child keys derives deterministically.
Which means one backup covers unlimited addresses across multiple assets.
Each child is derived by an index, so the same seed always produces the same sequence.
Derivation paths
A path specifies which branch of the tree an address comes from.
Which is why importing a phrase into a different wallet sometimes shows an empty balance — it is looking at a different branch.
Standard paths exist per asset, and historical variation between wallets is the usual cause of the problem.
Most wallets allow specifying a custom path, which resolves it.
Hardened derivation
Certain derivations prevent deriving a parent key from a child and a public key.
Which matters for security when extended public keys are shared.
Sharing an extended public key reveals all addresses in that branch, which is a privacy consideration rather than a theft risk.
Account discovery
Wallets scan a number of addresses ahead looking for activity.
Which means funds sent to an address far beyond the used range may not appear.
Increasing the gap limit in wallet settings resolves this when it occurs.
Practical consequences
The phrase is everything, the passphrase is separate and unrecoverable, and derivation path mismatches are the usual cause of apparently missing funds.
Testing recovery in advance is what turns this knowledge into actual safety.
Multiple accounts from one phrase
The standard structure includes an account level, allowing separate accounts under one backup.
Which is useful for separating activity without managing multiple backups.
Wallets differ in whether they expose this, and the accounts exist whether or not they are displayed.
Cross-wallet compatibility
A phrase generated in one wallet generally works in another, subject to path and standard compatibility.
Which is by design and is what makes the standard valuable.
Non-standard implementations exist and produce phrases that only work in their originating software, which is worth checking before relying on portability.
Word list languages
Standard word lists exist in several languages.
Which means a phrase in one language may not import into software expecting another.
The underlying entropy is the same, and the encoding differs.
Checksum
The final word encodes a check over the preceding ones.
Which means most transcription errors are detected on import.
An invalid phrase error generally indicates a wrong or misordered word rather than lost funds.
Verifying a backup
Import into a second wallet and confirm the first address matches before funding.
Which takes minutes and removes the most common catastrophic assumption.
Watch-only wallets
Importing an extended public key allows monitoring balances without any ability to spend.
Which is genuinely useful for checking holdings on an everyday device.
It exposes all addresses in that branch to whoever holds the key, which is a privacy consideration.
Air-gapped signing
Keeping the signing device permanently offline, transferring transactions by camera or removable media.
Which eliminates network-based attack paths entirely.
It is more cumbersome and is standard practice for large holdings.
Entropy quality
The randomness generating the original phrase determines its security.
Which is why generating phrases with dice or with a hardware random source is preferred over software of unknown quality.
Phrases generated by websites should never be used, since the site knows them.
Brain wallets
Deriving keys from a memorised phrase chosen by a person.
Which has been comprehensively broken, since human-chosen phrases have far less entropy than assumed.
Automated systems sweep such addresses continuously and have for years.
Summary
The phrase, the passphrase and the derivation path are the three things that determine access.
Migration between wallets
Moving to different software generally means importing the phrase and confirming addresses match.
Which is safer than transferring funds if the destination supports the same standards.
Where addresses do not match, the derivation path is the first thing to check.
Closing
The phrase generates everything deterministically, which is why protecting it is the whole of the task.
Common recovery problems
Wrong derivation path, forgotten passphrase, transposed words and insufficient address scanning.
Which between them account for most cases where funds appear missing but are not.
Working through these systematically resolves the majority before any assumption of loss is warranted.
Prevention
Record the wallet software, the derivation path and whether a passphrase was used alongside the phrase itself.