Restored wallet, missing balance

Seed phrase accepted but the wallet is empty? Diagnose before assuming the funds are lost

A wallet can accept valid recovery words and still display unrelated addresses or a zero balance. The cause may be an optional passphrase, derivation path, account index, script type, network, or the wrong wallet standard.

Acceptance does not prove identity

A checksum-valid mnemonic proves that the words form a valid phrase. It does not prove that it is the phrase used for the address you remember, nor that the same wallet settings were selected.

Compare public identifiers

Use known public addresses, transaction IDs, exchange withdrawal records, or a watch-only record to identify the expected wallet. Public data can support diagnosis without exposing the seed or private keys.

Common sources of a different wallet

An omitted BIP39 passphrase, different derivation path, wrong account index, legacy versus SegWit address type, different network, or wallet-specific seed format can all lead to valid but unexpected addresses.

Preserve the original setup context

Keep the old device, screenshots, labels, wallet name, model, firmware era, and software version. Do not repeatedly reset or initialize the only hardware device before documenting it.

When recovery may not be possible

If there is no link between the remembered address and the surviving recovery material, the diagnosis may remain inconclusive. A public address alone cannot reveal the required seed, passphrase, or private key.

Frequently asked questions

Why does the wallet accept the seed but show zero?

Valid words can still derive a different wallet because of passphrase, path, account, script type, network, or seed-format differences.

Is the balance stored inside the wallet file?

No. The blockchain records transactions; the wallet holds or derives keys used to control addresses.

Can I share the seed to identify the right path?

Do not share it publicly or in an initial assessment. Start with public addresses and configuration details.