Funds Not Showing? Derivation Paths, Accounts, and What to Check

In one paragraph. A wallet that restores correctly from your seed but shows a balance of zero has, in the large majority of cases, not been robbed — it is simply looking in the wrong place. The same seed phrase can generate several completely different sets of addresses depending on a setting called the derivation path, and a second setting called the account index. Restore your seed into a wallet that uses a different default path from your original, and your real, untouched funds sit on addresses the new wallet never checks. The reassuring part: much of the diagnosis is safe to do yourself, for free, and you can often confirm the money is fine before you involve anyone. This guide explains how, and where the genuinely awkward cases begin.

1. First, the calming fact: zero balance ≠ lost funds

If you have just restored a seed and seen 0.00, your stomach has probably dropped. Before anything else: a zero balance after a restore is most often a display problem, not a theft.

Your coins live on the blockchain, at specific addresses, permanently. A wallet app does not "hold" them — it re-derives a list of addresses from your seed and then asks the blockchain what those particular addresses contain. If the app derives a different list of addresses from the one your funds are actually on, it will faithfully report zero, while the coins sit safe and visible on a block explorer the whole time. Nothing has moved. The wallet is just asking about the wrong addresses.

The job, then, is not "recover lost funds" — it is "point a wallet at the right addresses". Often that is a free, five-minute fix you can do yourself. Sometimes it is genuinely harder. The rest of this guide is about telling the two apart.

2. What a derivation path actually is

Modern wallets are hierarchical deterministic (HD) wallets, defined by a standard called BIP-32. From your single seed, an HD wallet can generate a near-endless tree of private keys and addresses. A derivation path is the set of directions that picks one branch of that tree — written like m/84'/0'/0'/0/0.

You do not need to read the path like a programmer, but the shape matters:

• The first number after m/ is the purpose, and it is what selects the address type — 44' for Legacy, 49' for nested SegWit, 84' for Native SegWit, 86' for Taproot.
• The next number is the coin (0' = Bitcoin, 60' = Ethereum, and so on).
• The next is the account index (0', 1', 2' …) — see §4.
• The last numbers walk along the individual addresses.

Crucially, the same seed under two different purposes produces two entirely unrelated sets of addresses. Your Legacy 1... addresses and your Native SegWit bc1q... addresses share a seed but are different wallets in every practical sense. Put your seed in a wallet that defaults to the wrong purpose and your balance vanishes from view — not from existence.

3. Why wallets disagree — the standard paths, and who uses them

The reason this happens so often is that the ecosystem standardised at different times, and different wallets chose different defaults. This table covers the great majority of Bitcoin cases:

A classic example: you created a wallet years ago in software that used Legacy (1...) addresses, then in 2026 you restore the seed into a shiny modern wallet that defaults to Native SegWit (bc1q...). The modern wallet derives a fresh set of bc1q... addresses, finds them empty (because you never used them), and shows zero — while your real coins sit on the 1... addresses, exactly where you left them.

Ethereum and most EVM chains use a single standard path (m/44'/60'/0'/0/0), so this address-type problem is largely a Bitcoin-family phenomenon — though the account index issue in §4 can still bite on Ethereum.

4. Account indices and the "gap limit" — the second place funds hide

Even on the right derivation path, there is a second way funds disappear from view.

Account indices. Many wallets let you create multiple "accounts" from one seed — Account 0, Account 1, Account 2 — each a separate branch. If you received funds into Account 1 but your restored wallet only shows Account 0, the balance reads zero. Checking each account index is part of a thorough look.

The gap limit. Wallets do not scan infinitely far along a branch. By convention they stop after finding a run of about 20 consecutive unused addresses (the "gap limit") and assume there is nothing beyond. Usually fine — but if you once skipped ahead (some wallets, or manual use, can leave a gap larger than 20), the wallet stops scanning before it reaches your funds and reports zero. Raising the gap limit, where the wallet allows it, makes those funds reappear.

Both of these are common, both look identical to "my money is gone", and both are usually fixable.

5. What you can safely check yourself — for free

A great deal of this you can do without involving anyone, and without ever exposing your seed to the internet. If one of these solves it, you are done at no cost.

1. Find a known address and check it directly on a block explorer. If you have any old receiving address — from an email, a screenshot, a label — paste the address (never the seed) into a public block explorer. If the funds show there, your money is provably safe and this is purely a derivation-path display issue.
2. Restore into a wallet that lets you choose the path. Some wallets (for example, Electrum and Sparrow on desktop) let you set the derivation path or scan several. Restoring offline into one of these and trying m/44', m/49', m/84', and m/86' in turn will surface Legacy, nested-SegWit, Native-SegWit, and Taproot funds respectively.
3. Check multiple account indices (Account 0, 1, 2…) in your wallet's settings.
4. Raise the gap limit if your wallet exposes the setting and you suspect a skipped range.
5. Match the address type to your memory — if you remember your old addresses started with 1, you need a Legacy (44') path; 3 is nested SegWit (49'); bc1q is Native SegWit (84'); bc1p is Taproot (86').

The safety line, again. Checking an address on an explorer is completely safe — addresses are public. Restoring a seed must be done in trustworthy wallet software, offline where possible, and never typed into a website or "balance checker" page. The address is public; the seed is the keys to everything.

6. When it is genuinely harder — and a scan earns its keep

Self-checking handles the common cases. Some cases are legitimately past it, and this is where a systematic scan helps:

• A non-standard or custom derivation path. Some older or unusual wallets used paths that are not in the BIP-44/49/84/86 set at all. Finding these means searching methodically across known non-standard paths rather than the four defaults.
• You no longer remember which wallet software you used, so you cannot guess the right default to try.
• Funds spread across several account indices and/or beyond a large gap.
• A multi-coin seed where different assets sit on different paths.
• Old wallets (pre-2017) that predate the modern standards and occasionally used idiosyncratic schemes.

A professional scan works through the standard paths, a library of known non-standard paths, multiple account indices, and a sensible address range under proper gap-limit logic, deriving the candidate addresses and querying the chain for activity — until it either locates your funds or establishes, methodically, that they are not on any path the seed produces. We keep the exact tooling internal, but the principle is just breadth done carefully, not magic.

There is one genuinely reassuring technical point here: locating funds across derivation paths is fundamentally about deriving and checking public addresses, which can largely be done from the wallet's extended public key (xpub) — the public half. A great deal of derivation-path diagnosis therefore does not require your private keys at all, which makes it one of the safer pieces of work we do.

This kind of case is usually light Tier 1–2 work, and a fair number of enquiries end with us telling people the fix is free and showing them how — which is the right outcome.

7. What NOT to do

• Do not assume the funds are stolen because the balance shows zero. Check the addresses on an explorer first; theft is far rarer than a path mismatch.
• Do not enter your seed into online "balance checkers", derivation-path websites, or any web page. Use offline wallet software you trust. A page that asks for your seed to "find your funds" is a trap.
• Do not give up after one wallet. A single modern wallet checking a single default path is exactly the setup that hides Legacy-era funds. Try the other paths and account indices before concluding anything.
• Do not pay for a "scan" before checking the free options in §5, and do not pay anyone who needs your seed (rather than an xpub or known address) merely to diagnose a path problem.
• Do not pay in cryptocurrency or engage anyone who insists on it. Reputable UK firms invoice in GBP and issue proper invoices.
• Do not respond to unsolicited "I can find your funds" messages. Legitimate help does not arrive uninvited in your inbox.

8. Frequently asked questions

My restored wallet shows zero. Are my coins gone? Almost certainly not. The usual cause is that the new wallet derives a different set of addresses (a different derivation path) from your original, so it is checking the wrong addresses. Find an old receiving address and look it up on a block explorer — if the funds show there, they are safe and this is a display issue, not a theft.

How do I know which derivation path I need? Match it to your old address type: 1... = Legacy (BIP-44), 3... = nested SegWit (BIP-49), bc1q... = Native SegWit (BIP-84), bc1p... = Taproot (BIP-86). If you do not remember, try them in turn in a wallet that lets you choose the path, such as Electrum or Sparrow, offline.

Can I fix this myself for free? Often, yes. Restoring into a wallet that lets you select the path and account index, and checking your known address on an explorer, resolves a large share of these cases at no cost. We are glad when it does.

What is the gap limit and why does it matter? Wallets stop scanning a branch after about 20 unused addresses in a row. If your funds sit beyond a larger gap, the wallet never reaches them and shows zero. Raising the gap limit (where the wallet allows) makes them reappear.

Do you need my seed phrase to help with this? Frequently not. Because finding funds across paths is about deriving public addresses, a great deal of derivation-path diagnosis can be done from your extended public key (xpub) or even just known addresses — no private keys required. We will always ask for the least sensitive thing that does the job.

The funds aren't on any path I try. What now? Then it is worth a systematic scan across non-standard paths and account indices, or the problem may not be a path issue at all — it could be a seed-transcription fault (see Seed Phrase Typos or Wrong Order) or a missing word (Seed Phrase Missing 1 Word). A free assessment will help pin down which.

Which jurisdictions do you serve? The UK, the EU, and most jurisdictions where we can complete sanctions and money-laundering checks. We do not currently engage clients resident in the United States or Canada.

9. Working with us

Step one — a written first contact: an email to legal@arcana-crypto.com with your coin type, any known addresses, and which wallets and paths you have already tried. You do not need to send your seed.

Step two — a free, confidential assessment. Often we can tell you the fix is something you can do yourself, and how. If a systematic scan is warranted, we explain what it involves and what it would cost, and we will favour working from an xpub or addresses over anything more sensitive.

Step three — if a scan is needed, a written engagement sets the scope and price, and the work is handled non-custodially and offline.

A closing note. The zero balance after a restore is one of the most frightening sights in self-custody and one of the most over-diagnosed as theft. Far more often, the coins are exactly where you left them and a wallet is simply checking the wrong addresses. Look up your old address on a block explorer, try the other derivation paths offline, and check your account indices — and if the money still will not appear, write to us at legal@arcana-crypto.com. A fair number of these conversations end with us telling you it is free and showing you where to click.

Arcana Crypto LTD — registered in England and Wales (no. 16371124). Recovery and forensics for cryptoasset wallet-loss cases. UK + EU engagements. Sole Director: R. Macri.

Guide version 1.0 · Published 14 June 2026 · Last reviewed 14 June 2026 · Reviewed by counsel. This guide is general information, not legal or financial advice. The engagement letter is the operative contract for any recovery engagement, and its specific terms — not this guide — govern the relationship.