Step-by-step
- Open the explorer for the network you selected. Ethereum → etherscan, Base → basescan, TRON → tronscan, Solana → solscan. Navigate yourself; do not trust a popup.
- Copy the contract/mint from that explorer. USDT on Ethereum is not the Tether contract on TRON. SPL mints are base58, not 0x.
- Fetch token info in Settings on that same network. Settings → Tokens → network dropdown → paste → Fetch. Duplicate tokens error separately (<code>settings.tokens.error.duplicateToken</code>).
Fetch is not a price oracle
The wallet reads the contract’s metadata on that RPC. A scam token with a USDT name can still “fetch” if the contract exists. Verify the address against a source you typed, then keep amounts small.
| Symptom | Cause | Fix |
|---|---|---|
| This error immediately | No contract at that address on this chain | Change network or paste the right contract |
| EVM 0x on Solana selected | Wrong ecosystem | Switch to an EVM net |
| Empty address field | settings.tokens.error.missingAddress | Paste a contract |
| Already listed | duplicateToken | Use the curated row |
Telegram “token importers” that ask for a seed are theft. Custom tokens are contract addresses only.
Curated lists vs custom
Nine EVM nets ship with curated ERC-20/BEP-20 catalogs. Everything else is add-by-address. Solana includes SPL and Token-2022 in the adapter. After a successful fetch, the token appears on Dashboard for that network only.
settings.tokens.fetchFailed → “Couldn't read this contract. Check the address and network.”
Fetch token info → chain-specific RPC read, not a CoinGecko search
If Exchange already quoted a token, add that same contract so Receive/Send match the route. Bridged USDC ≠ native USDC.
FAQ
Why does the address look right on Etherscan but fail on Base? Different chain ids. The bytecode is not automatically on Base. Bridge or use the Base contract.
Can I add a token by ticker? No. Tickers collide. Always paste a contract/mint.
Does fetch spend gas? The read is an RPC call, not a signed transaction. Adding a token does not approve spenders.