A derivation path identifies a location in a deterministic wallet’s key tree. One initial configuration can generate many addresses. Restoring the seed in software that searches a different branch can therefore show an empty account even though no coins have moved.
Reading an example
In m/84’/0’/0’/0/5, the levels identify the convention, coin, account, branch and index. Apostrophes mark hardened derivation. In this BIP84 Bitcoin example, account zero is used and index five is the sixth address on that branch. It is not a path to impose on every wallet.
Scripts and accounts matter
BIP44, BIP49, BIP84 and BIP86 describe different conventions. A bc1q prefix suggests a version-zero witness address, but does not prove that the wallet uses BIP84; other scripts and setups exist. Reproducing a known address with the documented configuration is a stronger check.
Further reading: related technical explainer.
Seed, passphrase and app password
Changing a BIP39 passphrase changes the resulting wallet. That passphrase is not necessarily the password used to open the app. The recovery-phrase format must also be supported. Do not experiment with secrets in online services or treat one zero-balance display as proof that no funds exist.
Further reading: connected operating guide.
A sensible diagnostic order
Find the original wallet software, network, account information and a previously used address. Verify these before changing scan ranges or checking change branches. Increasing the gap limit on the wrong branch will not help. Use the software documentation and appropriate offline or watch-only methods.
Further reading: security checklist.
Public data still affects privacy
An extended public key can support checks without signing, but may expose the history of its branch. Do not post it in public support requests. Once the configuration is identified, retain the recovery-relevant details separately from secrets. Moving funds comes after establishing control, not before.
The path is not the transaction history
A path reproduces keys and addresses; it is not a record of payments. Finding a plausible path without reproducing a known address is weak evidence. A correct address, on the other hand, lets you inspect its history even if the application has not finished scanning every branch.
Accounts and change branches
Accounts can use different indices within the same convention. Change from a payment can also go to a branch separate from receiving addresses. Checking only the first address of the first account may therefore be insufficient. Follow the original wallet’s behaviour rather than a path example copied from a forum.
Describe recovery without exposing it
Operational notes can identify the software, account type and derivation convention without including the seed. Keep additional secrets separate and ensure an authorised future user understands which components are needed. A useful backup must be understandable, not merely a photograph of recovery words with no context.
Practical checks
- assuming twelve words imply one universal path.
- confusing a BIP39 passphrase with a wallet password.
- scanning only account zero.
- entering a seed into a web-based path finder.
- moving funds before checking a known address.
