The address gap limit refers to the standard number of public addresses that are checked for transactions in the blockchain in order to calculate an account's balance. Transactions received on an address beyond the address gap limit are not detected. This can only happen when using an external wallet to derive addresses.
How it works
A blockchain contains a record of public addresses and their balances. To display your account balance, Ledger Live checks your transaction history in the blockchain. As accounts for Bitcoin and Bitcoin-based coins use multiple public addresses, Ledger Live needs to look up only the public addresses that are used.
Public addresses are derived from an account's extended public key (xpub) by incrementing the address index in the derivation path. Ledger Live follows the BIP44 standard which prescribes that wallets look ahead 20 addresses from the last used address.
Address gap limit example
If you receive a transaction on the first address, address 1, Ledger Live will scan addresses 2 to 21 for any additional transaction history. If nothing is found, it will stop looking. If address 22 has been received, Ledger Live will not see it because it stopped at address 21.
Custom address gap limit (Advanced users)
Ledger Live lets you set a custom address gap limit in case you have received a transaction beyond the address gap limit. This feature should only be used temporarily for wallet recovery purposes.
- Go to the Settings.
- Click on the Experimental features tab.
- Enable the Custom gap limit option and set a custom number.
Caution: Setting a high gap limit will negatively affect synchronization performance.
- Click on the Help tab.
- Click on the Clear button to clear the cache.
- Click on Confirm.