Core Concepts
Wallet Sync
How Ledger connects to public blockchain RPCs to pull a complete transaction history and maintain a live balance for every address you add to a portfolio.
Wallet Sync
A portfolio is only as accurate as the transaction data behind it. Ledger keeps that data current by connecting directly to public blockchain RPCs for every address you add, pulling the complete on-chain history once and then refreshing it on a schedule that matches your VIP level. The address you provide is your public address only — Ledger never asks for and cannot use a private key, a seed phrase, or any signing material. Read access to the chain is enough to reconstruct every transaction the address has ever participated in.
Supported networks#
Ledger reads from every major EVM chain Atlas Labs has shipped support for, plus Solana and Bitcoin. Addresses on EVM-family networks (Ethereum, Base, Arbitrum, and the rest) share the same 0x… format, so an address is portable across them and Ledger picks up activity on whichever network you've selected.
Network | Address format | Notes |
|---|---|---|
Ethereum |
| ERC-20 tokens included |
Base |
| Same address as Ethereum |
Arbitrum |
| Same address as Ethereum |
Solana | Base58 | SPL tokens included |
Bitcoin |
| UTXO model |
Adding a wallet#
The flow is short. From the portfolio page, open the Connections panel, choose Add wallet, paste your public address, and pick the network. Ledger fetches the full transaction history on the first sync; subsequent syncs only pull what's new. The first sync for a long-lived address can take a few minutes — for a freshly-created one it returns in seconds.
How sync works#
Behind the scenes Ledger uses viem to talk to the RPC. For each address it pulls every incoming and outgoing transaction, every token-transfer event the address appears in (the standard ERC-20 Transfer log), and every internal transaction triggered by smart-contract calls that moved value through the address. The raw transactions are then normalised into double-entry journal entries — one for each side of every value flow — so the data feeds straight into the cost-basis engine without further transformation.
Swaps are a special case worth calling out. A swap is logically two transactions in one: a disposal of the asset you sold and an acquisition of the asset you received. Ledger detects the swap pattern at sync time and creates both legs automatically, with matching cost-basis records and the protocol fee broken out as a separate expense entry.
Sync frequency#
How often Ledger refreshes a wallet's data depends on the portfolio owner's VIP level. Free portfolios refresh on demand; VIP tiers add scheduled and real-time refreshes so positions stay current without manual intervention.
Plan | Sync interval |
|---|---|
Free | Manual only |
VIP 1+ | Every 6 hours |
VIP 2+ | Real-time (webhook) |
Excluding transactions#
Not every transaction belongs in your reported profit-and-loss. Test transactions from a deployment session, gas costs you'd rather track in a dedicated expense view, or one-off transfers between your own wallets all contribute noise to the P&L if they're left in. Ledger lets you mark any transaction as excluded; the entry stays in the audit trail so the balance still reconciles, but the realised-gain calculation skips it.