Restored From the Seed, and the Balance Is Zero
You typed your 12 or 24 word seed phrase into a new wallet and it shows a zero balance. The coins are almost always still there. The words restore keys, and the wallet guesses which addresses to look at. Address type and derivation path, account number, passphrase, gap limit, non-BIP-39 seed formats and rescans, in the order to check them when a restored Bitcoin wallet shows nothing.
You entered your seed phrase into a new phone or a new hardware wallet. Every word was right and the wallet opened without complaint. The balance is zero. Most people's first thought is that the coins were stolen. Far more often, the wallet is simply looking in the wrong place.
What a seed phrase brings back is a single root of private keys. Which branch you followed from that root and what kind of address you made is not written anywhere in the words. A new wallet walks the few paths it knows, finds nothing, and shows zero. No error appears.
Do not put the seed just anywhere
Settle one thing before you start. Enter the seed only into the wallet you originally used or a widely used open source wallet. Websites offering "balance recovery", tools that show up as search ads, and support accounts that message you first are almost all after the seed. The moment a balance shows zero is the moment people are most desperate, and scams aim at exactly that moment.
There are pages, such as Ian Coleman's BIP39 tool, that list the addresses on many paths at once. If you use one, download it as a file and open it on a computer disconnected from the internet. If the screen you typed the seed into was online, treat that seed as one somebody else may already know.
Find one address first
The fastest route is to find one address you received coins on before. An exchange's withdrawal history keeps the destination address. So do receipt screens in the old wallet, payment emails, and addresses pasted into notes. Look that address up in a block explorer and two cases separate immediately.
- The coins are still at the address. They are safe, and the new wallet just is not producing that address.
- The coins have already left the address. If you do not remember that withdrawal, skip to the last section below.
When you type an address into an explorer, the site sees your IP and the address together. An explorer backed by your own node is best. If that is not possible, at least do not go on to paste every other address of the wallet in after it.
Once you have the address, look at its first characters. They tell you the address format the wallet used, and the format maps almost one to one onto the path in the next section.
Cause 1. A different address type and derivation path
For one seed, each format has one standard path.
| Address starts with | Format | Standard path (BIP) |
|---|---|---|
1 | Legacy P2PKH | m/44'/0'/0' (BIP-44) |
3 | Wrapped SegWit P2SH-P2WPKH | m/49'/0'/0' (BIP-49) |
bc1q | Native SegWit P2WPKH | m/84'/0'/0' (BIP-84) |
bc1p | Taproot P2TR | m/86'/0'/0' (BIP-86) |
From the same twelve words, these four paths make addresses that never overlap. Most wallets today create only bc1q or bc1p at first. If coins from a wallet made around 2017 sit on addresses starting with 1 or 3, the new wallet never even considers those addresses. This is the most common cause. Most wallets let you choose the address format on the restore screen or when adding an account. Pick the one that matches the first characters of the address you found.
Non-standard paths are more common than you might expect. When Electrum restores a BIP-39 seed it looks for accounts already in use, and the discovery list in its source (bip39_wallet_formats.json) shows the situation. Beyond the three standard formats, it has three non-standard ones that use the path m/0' with different formats, and four mismatched combinations such as legacy addresses on the BIP-84 path. Copay made native SegWit addresses on the BIP-44 path m/44'/0'/0', and CoolWallet S used wrapped SegWit on the same BIP-44 path. Match only the path or only the format and those coins stay invisible. Both have to match.
Cause 2. The account number is not 0
The third position in the path, 0', is the account number. If you ever tapped "add account" in a wallet app, those coins are in account 1' or 2'. BIP-44 sets out account discovery like this: scan the receiving addresses starting from account 0, stop if no transactions are found, and move to the next account if there are some.
By that rule, if you left account 0 empty and used only account 1, discovery ends at account 0. An account emptied later still has transaction history, so discovery moves past it, but how faithfully wallets follow the procedure varies. If you remember creating several accounts, add them one by one in the restored wallet.
Cause 3. There was a passphrase
BIP-39 lets you add an optional passphrase on top of the words. The passphrase goes into the salt of the key stretching function: the string "mnemonic" followed by the passphrase, run through 2048 rounds of HMAC-SHA512. The BIP-39 text states the design choice outright: every passphrase generates a valid seed.
So a wrong passphrase is not rejected. The wallet happily opens a different wallet, and that wallet is empty. A forgotten passphrase and a passphrase off by one character look identical on screen. If you ever turned on a "hidden wallet" or "use passphrase" option on a hardware wallet, suspect this first.
The passphrase has to match to the character and the space. A different case is a different wallet. Leading or trailing spaces make a different wallet too. Phone keyboards often capitalize the first letter or add a space after a word. BIP-39 requires words and passphrase to be normalized to Unicode NFKD, so wallets that follow the standard treat the same characters the same way, but normalization does not help when the characters a person typed are different.
Cause 4. The coins are beyond the gap limit
A wallet does not scan receiving addresses on a path forever. When a certain number of unused addresses appear in a row, it assumes there are no more and stops. That number is the gap limit. BIP-44 sets it at 20, and the same document says wallet software should warn when the user is trying to exceed the gap limit by generating a new address.
The trouble is that the limit gets exceeded without the user noticing. If a payment page or shop server issued a new address for every order and most orders were never paid, the address that actually received coins may sit behind more than twenty empty ones. Pressing "new address" many times and receiving only on a later one does the same.
Electrum's source sets the default gap limit to 20 for receiving addresses and 10 for change. In the console (View, Show Console) you can raise the receiving limit with something like wallet.change_gap_limit(100). The "change" in the name means altering the limit, not change addresses. Other wallets often keep the same value in an advanced setting. Raising it means more addresses to scan, so syncing gets slower.
Cause 5. The seed is not BIP-39
Some seeds look like the same word list but turn words into keys differently.
Seeds that Electrum creates itself are not BIP-39. Electrum's documentation says it does not generate BIP-39 seeds, citing the lack of a version number in BIP-39. Instead it puts a version in the leading part of a hash of the seed phrase: 01 for legacy and P2SH multisig, 100 for SegWit, 101 for two-factor wallets. Put such a seed into a BIP-39 wallet and you usually get a checksum error. If the checksum happens to pass, a completely different empty wallet opens. Restore Electrum seeds with Electrum. Electrum goes the other way too: choose BIP39 seed in the options on its restore screen and it finds the accounts in use with the discovery list described above.
The aezeed format used by LND's Lightning wallet is different again. It is written as 24 words from the BIP-39 English list, but inside it carries an encrypted version byte, the wallet's birthday (counted in days from the genesis block) and a salt. If you set no passphrase, the string "aezeed" is used. Put it into a BIP-39 wallet and the same thing happens. Trezor's Shamir backup (SLIP-39) consists of several shares of 20 or 33 words, and even its word list is different. If your word count is not 12 or 24, suspect this first.
Bitcoin Core has no screen for entering words at all. Descriptor wallets import descriptors containing extended keys, and seed words have to be converted to an extended key with another tool first. A pull request to accept mnemonics (#35857) was opened as recently as July 2026 and was closed without being merged.
Cause 6. A wallet one seed cannot open
One seed of a multisig wallet is only one key. Put one seed from a 2-of-3 wallet into an ordinary wallet and it opens the single signature addresses that key makes on its own, and there is nothing there. To make the multisig addresses you need the other keys' extended public keys, the quorum and the order, and the one line that records all of that is the output descriptor. If you have neither the descriptor nor the wallet configuration file, get it from a co-signer.
Wallets that do CoinJoin also use special accounts. The Samourai paths in Electrum's discovery list put Whirlpool's premix and postmix coins in accounts 2147483645' and 2147483646' on the BIP-84 path. A normal wallet scanning accounts in order from 0 will never reach those numbers. Restore with the same family of wallet, or one that lets you enter the path directly.
Cause 7. The wallet never reread the past
Even with every path right, the balance is zero if the wallet never scanned past blocks. Light wallets that ask a server about addresses rarely hit this. Wallets connected directly to your own full node do. When you import descriptors into Bitcoin Core with importdescriptors, a timestamp of "now" skips the past. Give it a date around when the wallet was first created, or run rescanblockchain after importing. A pruned node cannot scan blocks it has deleted, so that range has to be downloaded again.
If the coins really moved
If the address you found shows the coins leaving and you do not remember that withdrawal, this is not a path problem. That transaction carries a signature, and only whoever holds the key can make one. Assume the seed leaked somewhere. If any path on the same seed still holds coins, create a new seed on a new device and move them right away. Move any passphrase wallets on the compromised seed as well, since you cannot know whether the passphrase leaked too.
You can follow where the coins went in an explorer, but there is no way to reverse it. If the trail ends at an exchange deposit address, asking the exchange to freeze it through law enforcement is the path that remains.
The order to check
When a balance shows zero, go in this order.
- Find one address you received on before and check in an explorer that the coins are still there.
- Restore again with the address format that matches that address's first characters.
- If you used several accounts, add them one at a time.
- Recall whether you ever used a passphrase, and enter it exactly, case and spaces included.
- If many addresses were issued, raise the gap limit.
- From the word count and the original wallet, check whether it is an Electrum seed, aezeed or SLIP-39.
- For a multisig or CoinJoin wallet, you need the descriptor or the specific path.
- For a wallet connected to your own node, make it rescan.
The list is long for one reason. The seed remembers the keys and not the map. Write the wallet's name and version, the address format, whether a passphrase is used and one first receiving address next to the seed when you create the wallet, and most of this list stops being necessary. All the more so for an inheritance plan where the person restoring is family. The surest preparation is to restore once on another device while you have time, and check that the first address matches.