On-chain wallets

Sure can track wallets you hold the keys to — Bitcoin, six EVM networks, and Solana — from their public addresses only. Nothing is signed, no key or seed phrase is ever entered, and no API key is required for any chain.

​

What gets tracked

One Sure account is created per asset, per address, per network. A wallet holding ETH and USDC on Ethereum becomes two accounts, both Crypto accounts with the “wallet” subtype. For each asset Sure records:

• The quantity held, read from the chain
• A holding valued at the current price, or at zero when no price is available
• The transfers in and out, as investment trades when the price for that day is known, so cost basis and the value chart reconstruct back to acquisition. When that day’s price is not known, the transfer still appears as an excluded, zero-amount entry — and it is upgraded to a trade on the first sync after the price becomes available

Balances are read-only and always derived from the chain. Editing them by hand is pointless: the next sync overwrites them.

​

Prices need two settings, not one

On-chain data sources report quantities, not values. Prices come from Sure’s market data providers, and the only provider that can quote bare crypto symbols is Binance public (keyless). If no crypto-capable market data provider is enabled, every on-chain wallet is tracked by quantity and valued at zero. This is the most common support report for this feature, and it is a settings issue rather than a sync failure. The settings panel and the linking modal both warn you before you link anything. On a self-hosted instance an admin can fix it from the warning itself with Enable crypto prices — that adds binance_public to the enabled providers and leaves the others alone. Otherwise, enable it under Settings → Self hosting → Market data providers, or set SECURITIES_PROVIDERS to a comma-separated list including binance_public.

​

Exchange rates for non-USD families

The crypto provider quotes in USD, so valuing a wallet in any other family currency needs an exchange rate. Sure’s default exchange rate provider (twelve_data) requires an API key. With no key and a non-USD family, every on-chain wallet is valued at zero for this second, separate reason. Set EXCHANGE_RATE_PROVIDER (or Settings → Self hosting) to a provider you can use; frankfurter needs no API key. The linking UI warns about this gap specifically, naming your currency. A USD family never sees this warning. When an asset ends up valued at zero for either reason, it is recorded in Settings → Debug logs under the onchain_wallet provider with the reasons listed.

​

Data sources

Every override expects the base URL of a compatible instance, without a trailing slash — useful if you run your own indexer or node, or if a public endpoint rate limits you.

​

Optional Etherscan key

Ethereum, and only Ethereum, can be read through Etherscan instead of Blockscout. A key buys nothing except a higher rate limit. Add it under Settings → Providers → On-chain wallets → Advanced; it is stored encrypted, per family. A key only moves transfer history onto Etherscan. Balances and network detection always come from the keyless indexer. Leave the field empty unless you are being rate limited.

​

Rate limits and request cost

All the default endpoints are free and shared, so they throttle. Per sync, per address, the cost is roughly: History is capped by default at 10 pages per source and at 25 transactions for Solana. Wallets with more history keep their current balance correct — balances come from an address summary, never from history — but their oldest transfers are not imported. Raise both caps with ONCHAIN_HISTORY_MAX_PAGES (default 10, maximum 200); the Solana budget scales proportionally. History is best effort; balances are not. If a source refuses or times out on paginated history, the balances are still recorded and the history is marked incomplete. When a cap is hit, the affected address says so in Manage wallets, and the event is recorded in Settings → Debug logs under the onchain_wallet provider.

​

Token limits per address

Real addresses are airdrop dumping grounds. One read surfaces at most 200 tokens per address, settable with ONCHAIN_MAX_TOKENS_PER_ADDRESS (maximum 5,000). The native coin is never affected, and anything already tracked keeps syncing regardless. On EVM networks the tokens kept are ranked by market cap, so real assets survive the cap and airdrops fall off the end. On Solana the order is by mint address — arbitrary, but identical between syncs, which stops the cap from reshuffling a wallet every night.

​

Linking a wallet

Go to Settings → Providers → On-chain wallets → Add wallet. Nothing is imported that you did not tick.

​

Managing a wallet

Go to Settings → Providers → On-chain wallets → Manage wallets.

• Review tokens — reopens the asset selection with the address unchanged. Use this to start tracking a token that arrived later, or stop tracking one you no longer want.
• Stop tracking (per asset) — drops one asset.
• Change address — corrects the address while keeping the accounts, holdings, and balance history attached to it.
• Disconnect wallet — drops every asset at one address.

Disconnecting never deletes an account. The provider link is removed, holdings are detached, and what you can see stays as a manual account that no longer updates. Delete the account itself if you want it gone. An address can only be tracked once per network. To change which assets are tracked, use Review tokens rather than adding the address again.

​

Limitations

Only tokens the crypto price provider quotes get a value, and it quotes by symbol. Valuation goes through a CRYPTO:<SYMBOL> ticker, and a symbol is not a token’s identity — its contract is. In practice the provider covers major assets and little else: measured on a real Ethereum address, of its ten largest token positions it quoted two. The other eight — including holdings worth roughly $406,000,$141,000 and $74,000 — showed a value of zero while their quantities were tracked correctly. A zero next to a token you know is worth something almost always means the provider does not list that token, not that the balance is wrong. Check the quantity, which is read straight from the chain. Native coins (BTC, ETH, SOL, POL, XDAI) and large-cap tokens are the well-covered case. DeFi positions are not seen at all. Staked ETH, liquidity-pool tokens, lending positions, and Solana stake accounts are invisible. A wallet holding most of its value in a staking or lending protocol will report a fraction of it. Bitcoin is one address at a time. Extended keys (xpub, ypub, zpub) are not supported and are rejected as addresses. Most Bitcoin wallets are HD wallets, where one extended key derives thousands of addresses and change is sent to derived ones. Tracking a single address of such a wallet reports only that address’s balance. Solana token names depend on a token list. RPC returns mints, not names, so names come from Jupiter’s token search — and only for mints it reports as verified. An unverified or unknown mint keeps a label built from its mint address and is tracked by quantity only. Names are cached for 24 hours per mint. Fees are not itemised. Network fees are included in the net effect of each transfer rather than recorded separately. On Solana, native balance changes below 0.0001 SOL are treated as fees and ignored. Bridged assets are normalised. USDC.e, USDbC, USDT0, WETH, and similar 1:1-redeemable forms are tracked as their canonical asset, so the same asset held on two networks is one Security rather than two. Prices are daily and USD-quoted. Values are converted into your family currency using Sure’s exchange rates. A transfer whose day has no price becomes a zero-amount excluded entry rather than a trade. NFTs are not tracked. They are filtered out by token standard, so an NFT is never mistaken for a balance of one fungible token.

​

Troubleshooting