What Is the Gap Limit in a Bitcoin Wallet? (And Missing Funds)

The gap limit is one of those quiet HD wallet rules that nobody notices until a restored wallet shows the wrong balance. Once you understand why it exists and how to work around it, a scary looking case of missing bitcoin becomes a solvable one.

What is the gap limit in a Bitcoin wallet?

The gap limit is a cap on how many empty addresses a wallet tolerates in a row before it stops deriving new ones. Modern wallets are hierarchical deterministic, meaning a single seed generates an effectively unlimited sequence of addresses through an extended public key. Because that sequence is infinite, a restoring wallet needs a stopping rule, otherwise it would scan forever. The gap limit is that rule. As it walks the derivation path, it keeps a running count of consecutive addresses with zero transaction history. The moment that count hits the limit, usually 20, it decides the remaining addresses are all unused and ends the scan.

Why is the gap limit 20?

The gap limit is 20 because BIP 44, the standard that defines HD account structure, specifies 20 as the default, and most wallets simply follow it. The number is a compromise. Set it too low and a wallet might stop before finding legitimately used addresses that happen to sit after a run of skipped ones. Set it too high and every restore becomes slow, since the wallet has to query the history of far more addresses than it will ever need. Twenty consecutive unused addresses was judged large enough that normal wallet use almost never leaves that big a gap, while staying small enough that scanning stays fast.

How does the gap limit cause missing funds?

The gap limit causes apparent missing funds when a payment lands on an address that sits beyond a run of 20 unused ones. Picture a wallet that has used address index 5, then you manually generate address 40 and receive coins there, skipping everything in between. On restore, the wallet derives index 6, 7, 8 and so on, finds nothing, and by index 25 it has seen 20 empty addresses in a row. It stops. Index 40, where your coins actually are, is never checked, so the balance looks short. The bitcoin is not lost. The wallet simply never scanned far enough to see it.

How do I recover funds beyond the gap limit?

To recover funds past the gap limit, you need to make the wallet scan further than 20 empty addresses. The most common fixes are to raise the gap limit setting in a wallet that exposes it, such as Electrum, then rescan; or to import the specific derivation path or address where you know the coins landed. Some wallets let you set the gap limit to a few hundred temporarily, which forces a deeper scan across the whole account. Because the addresses are all deterministic, nothing is at risk in doing this: you are only asking the software to look at more of the same sequence it already knows how to generate.

Can I check an address past the gap without my wallet?

Yes, you can check any address for history independently of your wallet by querying the chain directly, which is often the fastest way to confirm coins are really there before you fiddle with wallet settings. If you have the extended public key, you can derive the addresses and check each one over an API. BitcoinDatabase indexes every address on the chain, so you can look up a balance and full history for any derived address, or watch a whole wallet through an xpub balance API that walks the derivation path for you. That confirms the funds exist and tells you exactly which index to import, all without exposing a private key.

Does raising the gap limit put my coins at risk?

No, raising the gap limit does not put your coins at risk, because it only changes how far the wallet scans, not anything about your keys or the coins themselves. The gap limit is a search setting, not a security control. A higher limit means the wallet queries the history of more addresses during a restore, which takes longer and uses more bandwidth, but every address it checks is one your seed already deterministically controls. The only real trade-off is speed. Once your funds are found, you can leave the limit high or return it to the default without affecting the balance.

Query the derivation path directly

The gap limit is really a symptom of how HD wallets work: one key, an endless sequence of addresses, and a stopping rule that occasionally stops too soon. When you can query the chain yourself, that stopping rule stops being a mystery, because you can check any index directly and see exactly where the money is. BitcoinDatabase lets you resolve balances and history for any address or extended public key over a clean API, SQL or dashboards, so a confusing restore becomes a lookup. Try it from the console above, and this is informational on-chain data only, not financial advice.