Crypto Balance Showing Zero After Restoring Your Wallet? The Derivation Path Fix
September 5, 2026
7 min read
Disclosure: This article is information and opinion, not financial advice. See our full disclaimer.
The seed phrase was accepted. The wallet restored. And the balance says zero.
This one frightens people more than an “invalid phrase” error, because it feels like confirmation: the wallet checked, and the money’s gone. Except that’s not what happened, in the overwhelming majority of cases. What happened is this: your seed phrase is a master key to millions of addresses, different wallet apps open different ones by default, and this wallet is showing you an empty room in a building where your coins are sitting two doors down.
The coins didn’t move. The wallet is looking in the wrong place. And there’s a two-minute test that proves which situation you’re in before you touch anything.
2. Paste it into a block explorer. Balance still there? Then nothing is lost; this is purely a looking-in-the-wrong-room problem, solvable below.
3. Now compare: does the freshly restored wallet show that same address? Different address = the wallet opened the wrong room (derivation path, passphrase, or a different seed; fixes below). Same address but zero = check the explorer’s transaction history to see where and when the coins went.
Why one phrase opens millions of doors
A seed phrase doesn’t contain one address; it deterministically generates a practically infinite tree of them, organized along “derivation paths,” which are just standardized routes through that tree. Every wallet app picks a default route: which address format, which account index, which branch. Same key, same building, different floor plans.
Restore a phrase in the same app that created it and you land in the same rooms automatically. Restore it in a different app, or a new version, or a different mode, and you can land on a perfectly valid, perfectly empty branch of your own tree. Nothing about the balance changed; only the tour route did.
The five causes, in order of likelihood
1. Different address type (Bitcoin’s specialty). Bitcoin has three address families, per the address guide: legacy (starts with 1), nested (starts with 3), and native segwit (bc1). A wallet defaulting to bc1 won’t show coins sitting at your old 1-address. Fix: look for an address-type or account-type option during restore (hardware wallet apps typically list all three as separate accounts; pick each and check), or restore in a wallet that lets you choose the path explicitly.
2. A missing passphrase, the “25th word.” Some setups add an optional extra word or phrase on top of the seed, and here’s the trap: the same seed with and without a passphrase produces two completely different wallets, both valid, both restorable, no error anywhere. If you ever enabled a passphrase (hardware wallets call it a hidden wallet), restoring without it lands you in the empty twin. Fix: restore again and enter the passphrase, exactly, since it’s case-sensitive and space-sensitive.
3. It’s the right phrase for a different wallet. People who’ve been around a few years own several seeds. A phrase that restores cleanly but shows unfamiliar addresses may simply be the key to another, emptier building of yours. The address-comparison test catches this instantly: if the restored addresses match nothing in your records, hunt for your other backups.
4. The coins are on accounts or networks the wallet hasn’t shown yet. Multi-account wallets restore account #1 and wait; if your coins lived on account #3, add accounts until they reappear (in MetaMask: create additional accounts, they’re deterministic, the same ones come back in order). Same logic for networks: a restored EVM wallet shows Ethereum by default, and balances on other chains appear only after you re-add those networks.
5. The scan just hasn’t finished, or hit its limit. Wallets discover your history by scanning; on a slow connection or a long history that takes time, and Bitcoin wallets stop looking after a “gap” of consecutive unused addresses. Fix: let it finish, restart, or trigger a full rescan in settings before concluding anything.
The tools and the trap
Two honest helpers for stubborn cases: the community resource walletsrecovery.org documents which derivation paths each wallet brand uses (find your old wallet’s name, get its path, use a wallet that accepts custom paths), and hardware-wallet apps make trying all address types safe and easy since the seed stays on the device.
And the trap, stated as always in absolutes: this exact panic is farmed by fake “wallet recovery” websites and helpful strangers who materialize when you post about it. The phrase goes into wallet software or a hardware device, never into a website, never to a person, never to “support,” per the entire red flags doctrine. Anyone asking for it is the loss you were worried about.
If the explorer shows the coins actually left
The rare, serious branch: the correct address, a zero balance, and an outgoing transaction you didn’t make. That means the seed was compromised somewhere along the way, and the response isn’t recovery of that wallet but retirement of it: new wallet, new seed, generated on a clean device (ideally a hardware wallet), and nothing valuable ever touches the old phrase again. The transaction’s timestamp at least tells you when, which sometimes tells you how, and the lesson gets expensive exactly once if the new setup is done right.
Common questions
Why does my wallet show zero after restoring my seed phrase?
Almost always because the wallet is deriving different addresses than your coins sit at: a different address type, a missing passphrase, another account index, an unadded network, or an unfinished scan. The blockchain balance is unchanged, verifiable by checking your old address on an explorer.
Are my coins gone if the restored balance is zero?
Only if the explorer shows an outgoing transaction you didn’t make; otherwise the coins sit exactly where they were, and the zero is a display of the wrong branch of your own key. Check the old address first and let the answer set your pace.
What is a derivation path?
The standardized route a wallet takes through the tree of addresses your seed generates: which format, account, and branch to open. Different wallets default to different paths, so the same phrase can display different (equally valid) addresses in different apps.
How can one seed phrase produce different addresses in different wallets?
Because the seed is a master key generating millions of addresses deterministically, and each app chooses which ones to show. Same key, different tour route. Matching your old wallet’s path, address type, or account index brings the familiar addresses back.
What is the 25th word or passphrase?
An optional extra secret on top of the seed that creates an entirely separate hidden wallet: same phrase plus passphrase equals different addresses, with no error shown when restoring without it. If you ever set one, restoring with it, typed exactly, is the fix.
How do I find out which wallet brand I originally used?
Clues: old app-store history, emails from wallet setup, the address format itself (a 1, 3, or bc1 start narrows Bitcoin wallets), and screenshots. Once identified, restoring in that brand’s current app, or matching its documented derivation path elsewhere, recreates the original view.
Is it safe to keep trying restores?
Completely: restoring is read-only key derivation, and no number of attempts, apps, or wrong paths can move funds. The only unsafe act is typing the phrase anywhere other than wallet software or a hardware device, which is theft’s front door regardless of the occasion.
How do I prevent this next time?
Record three things with your backup: the wallet brand and version, whether a passphrase exists (without writing the passphrase alongside the seed), and one receiving address for future comparison. Those three lines turn any future restore from an investigation into a formality.
