Balance Sync
The wallet detail page shows a Balance Sync panel that lists every pool address the wallet has ever derived, together with its current on-chain balance. Sync runs on demand — TxNod fetches fresh data from the chain provider for each address. This page covers the two signals operators most often ask about.
Staleness
The Balance Sync panel keeps a per-wallet fresh-TTL of five minutes. Inside that window, the Sync balances button is disabled and the meta line shows Just checked — wait Xm Ys so you don’t fan out provider quota by clicking it repeatedly. After the window elapses, the button re-enables and a click triggers a fresh sync.
Once a sync completes (or while none has run yet), the meta line shows one of:
Last synced: <relative time>— the most recent successful sync, with a relative-time label that ages fromjust nowthrougha minute ago,5 minutes ago, etc.Last successful sync: <relative time> · showing cached balances— the most recent sync failed; the table is showing the previous successful snapshot.Never synced— the wallet has never been synced; the table is empty until you click Sync.
The five-minute TTL is per-wallet, not per-address; one sync covers every used address in one batch.
Ledger Live gap limit
Ledger Live derives addresses lazily — by default it only watches index 0 on most chains, even though TxNod’s pool model allocates from index 1 onward. That mismatch produces three different surprise modes depending on the chain family:
EVM (Ethereum, Polygon PoS, BNB Smart Chain)
Ledger Live by default shows only index 0 on EVM chains. Your derived addresses (indexes 1, 2, 3, and onward) are on-chain and spendable, but invisible in Ledger Live unless you Add Account per index. TxNod’s Balance Sync is the ground truth.
TRON
Ledger Live TRON typically shows only index 0. TxNod’s Balance Sync is the ground truth.
Cardano
Ledger Live Cardano groups addresses under your stake key but may not display every derived payment address. Balance Sync covers every address this wallet has used.
If a Ledger Live balance disagrees with Balance Sync, trust Balance Sync — it queries the chain provider directly for every index the pool has ever allocated, with no client-side gap-limit assumption.