Two ways to track crypto
Vault handles crypto in two different ways, and it is worth knowing which applies to you before you start.
Connected wallets. You paste a public address, and Vault reads the transaction history from the blockchain automatically. This works for seven networks, listed below.
Manual accounts. For other coins you create the account yourself and enter transactions by hand. Exchange rates still work, and balances are converted into your workspace currency — but there is no address to connect.
Before you start
Connecting a wallet requires the Pro plan. On Free and Basic you can still create manual crypto accounts and enter transactions yourself.
Networks you can connect
Network | Tokens read |
Ethereum | ETH, USDT, USDC, LINK, UNI, POL |
Polygon | POL, USDC, LINK |
BNB Smart Chain | BNB, LINK |
Arbitrum One | ETH, USDC, LINK |
Base | ETH, USDC, LINK |
TRON | TRX, USDT |
Solana | SOL, USDC, USDT |
Manual accounts only
Bitcoin (BTC), Litecoin (LTC), Dogecoin (DOGE), Cardano (ADA), Polkadot (DOT), TON, XRP and Avalanche (AVAX).
You can hold these in Vault and their value will be converted into your workspace currency at current rates. You just enter the transactions yourself rather than connecting an address.
How to connect a wallet
Open your workspace dashboard and click Add account, then choose Web3.
Pick the network first, then paste the address.
Choose the date to import history from.
Vault reads the address and shows what it holds. Tick the assets you want.
The history loads in the background.
The order matters. The same address exists on every EVM network — Ethereum, Polygon, BNB Smart Chain, Arbitrum, Base — with a different balance on each. Vault needs to know which one you mean.
About the start date. You can import from any date back to 26 December 2023. Earlier than that we have no exchange rates, so transactions could not be converted into your workspace currency. If you pick an earlier date, Vault moves it to the earliest one it can price and tells you.
Each token becomes its own account
If an address holds ETH, USDT and USDC, you get three accounts — one per token — because each has its own currency and its own balance.
They are named so you can tell them apart: USDT · 0x39…a936 (ETH) — the token, the shortened address, the network.
On Solana a single wallet often holds several token accounts for the same token. Vault adds them together and shows one account, not one per token account.
How often wallets update
Connected wallets refresh every few minutes. It is not instant, but a transfer will usually appear within minutes rather than hours.
The first import can take longer. A wallet with years of history has thousands of transfers to read, and they arrive in batches. Solana is the slowest of the seven — it needs a separate request per transfer — so a busy Solana address can take a while to catch up. It continues in the background; you do not need to wait on the screen.
Why USDT is not everywhere
This is the question most people ask when they see the table above.
USDT is available on Ethereum, TRON and Solana only. On Arbitrum, Base and Polygon, Tether does not issue the token itself — what circulates there are bridged versions issued by third parties. We do not read those, because they are not the same asset and treating them as such would put a number in your reports that nobody guarantees.
USDC is available on every network in the list, because Circle issues it natively on each of them.
We read only the tokens listed
Anything else sitting at that address is ignored — including tokens with names designed to look like real ones.
Sending worthless tokens to random addresses is a common trick, and the names are often near-identical to legitimate ones. We have seen addresses holding a fake "ETH" spelled with an accented letter, and several fake USDC variants using invisible characters.
Because Vault reads only a fixed list, matched on the token's contract address rather than its name, a fake token cannot reach your reports at all. Nothing to spot, nothing to clean up.
NFTs are ignored for the same reason. They are not in the list, so they never appear.
Very small transfers are filtered out
Another common trick is sending a fraction of a cent from an address that looks almost identical to one you normally pay — hoping you will later copy the wrong address out of your own history.
Vault drops incoming transfers worth less than about two cents in your workspace currency. They never reach your transaction list.
Transfers between your own wallets
If you move money between two wallets you have connected, the blockchain reports it twice: leaving one address and arriving at the other.
Vault does not pair them automatically. Until you do, reports will count the outgoing side as an expense.
To fix it, select both transactions and merge them into a transfer.
Pausing, converting and deleting
These work the same way as bank accounts.
Pausing stops new transfers appearing while keeping everything already imported. The balance holds where it was. When you resume, everything that arrived in between appears at once. Other assets on the same address are unaffected.
Converting to manual keeps everything imported and stops the address feeding it. From then on you maintain it yourself. This cannot be undone.
Deleting removes the account and its transactions. Also permanent.
We only ever need the public address
Not your private key. Not your seed phrase. Nothing that could move your funds.
A public address is exactly what you would give someone to receive a payment — the blockchain already publishes everything associated with it. Vault reads that public record and nothing more.
If anything ever asks you for a seed phrase in order to connect a wallet, it is not us.
