How to Add a Custom Network and Token to Your Wallet (and Verify the Contract Address)

The WATS Hot Wallet comes with its supported chains already configured — EVM networks including Ethereum and its L2s, plus Solana and TON — so there is no RPC endpoint to paste in for those. Adding a custom EVM network by hand takes five fields: network name, chain ID, RPC URL, native currency symbol and block explorer URL. Adding a token takes one verified contract address for that exact chain, confirmed on a block explorer first. Importing a token is local — no gas, no transaction, no approval.

Why Wallets Don't Show Every Network and Token by Default

A wallet does not carry a master list of everything on-chain. It ships with a few preloaded networks and a curated token list, and anything outside that has to be pointed at by hand. The reason is partly technical — a wallet can only read balances from a network if it knows where to send its queries, and there is no universal registry of chains — and partly safety. Anyone can deploy a token named after a well-known asset, so a wallet that displayed everything landing in your address would double as a phishing channel.

So when you bridge to a newer rollup, or hold a token that never made the built-in list, the wallet is simply not looking for your balance. Adding the network and contract tells it where to look.

What You Need First: Chain ID, RPC URL and Block Explorer

Adding an EVM network manually takes five fields, each with a job. Network name is a label for you. Chain ID is not cosmetic: it is a unique integer bound into the transactions your wallet signs, which is what stops a transaction signed for one chain from being replayed on another. RPC URL is the endpoint the wallet queries to read balances and broadcast transactions — if you are unsure what that node does, read what an RPC node is and why your wallet needs one before pasting one in. Native currency symbol is the ticker shown beside gas balances; its decimals are not a field you type, being fixed at 18. Block explorer URL is nominally optional; fill it in anyway, because it turns a transaction hash into something you can inspect.

Source all five from the chain's own documentation. As of 2026 community registries mirror them, but official docs are what to trust.

Step 1: Add a Custom Network to Your Wallet Manually

Open your wallet's network settings, choose to add a network manually, paste the five fields in, save, and switch to it. Prefer this to a site's one-click add-network button, which picks the RPC URL for you.

Most wallets query the endpoint on save and compare the chain ID it reports against the one you typed; if they disagree, they refuse to save. That check is a feature — do not work around it. Once the network is active, your native balance should appear within seconds.

Step 2: Find and Verify the Real Token Contract Address

This is where people lose money, so slow down. A token is identified by its contract address on a specific chain — not by its ticker, not by its logo. The same project has a different address on every chain it deploys to, and impostor contracts with identical names are cheap to create.

Take the address from a source the issuer controls — their documentation, official site or verified social account — then confirm it on the chain's explorer. A legitimate contract normally shows verified source code, a substantial holder count and transfer history going back to deployment; a copycat deployed last week shows a few holders and almost no activity. If you are unsure which signals matter, learning to read a block explorer pays for itself the first time it stops you. Compare the full string character by character: attackers generate vanity addresses matching at the first and last four precisely because that is the part people check.

Step 3: Add the Token and Confirm the Balance Appears

With the correct network selected, open the import-token option and paste the contract address. The wallet reads the symbol and decimals straight from the contract. Do not overwrite those auto-filled values unless the contract is non-standard — the decimals field controls how your balance is displayed, and a manual mistake there makes your holdings look wildly wrong.

Save, and the balance should render immediately. Importing a token is purely local: it writes an entry to your wallet's display list, costs no gas, sends no transaction and grants no approval to anyone.

Red Flags: Fake Tokens, Spoofed RPCs and Copycat Contracts

Three patterns recur. Airdropped dust: an unfamiliar token appears unprompted, often mimicking a real name, with a website baked into its metadata. Do not interact with it: trying to sell or approve it is usually the trap. Spoofed RPC endpoints: a malicious node can show fabricated balances and prices. It cannot sign for you, but it can mislead you into signing, so use endpoints from official docs or a provider you chose yourself. Copycat contracts: matching ticker, matching logo, different address. The explorer is the tiebreaker every time.

Troubleshooting: Wrong Chain ID, Zero Balance, Missing Decimals

If the wallet rejects your network, the chain ID almost certainly does not match what the RPC reports; check for a decimal-versus-hexadecimal mix-up, the most common cause. If the network saves but nothing loads, the endpoint is unreachable or rate-limited — swap in a second endpoint for the same chain ID and see whether the problem follows.

If the token imports but shows zero, confirm you are on the chain where you actually hold it. Assets bridged to one network are not present on another, and identical-looking addresses across EVM chains make this easy to misread. If the funds went over the wrong network entirely, importing a token will not surface them — recovering crypto sent to the wrong network covers what is and is not retrievable. If the balance is off by orders of magnitude, the decimals are wrong: remove the token and re-import it.

Adding Networks and Tokens in WATS Wallet

The WATS Hot Wallet works across a maintained set of supported chains: EVM networks including Ethereum and its L2s, plus Solana and TON. The verification habits above still apply to any token you hold there.

One thing differs on those supported networks. Every action — transfers, swaps, staking — is charged in a single token, ATS, instead of the chain's native gas: on EVM through an ERC-4337 paymaster, and on Solana and TON through an equivalent fee-payer and relayer. Because ATS is a LayerZero OFT, one balance covers all of them. That changes which token pays the fee, not what the network charges — the ATS amount tracks the live cost. Collected ATS is burned, from 100 million toward a 30 million floor. It stays non-custodial throughout: you hold your keys and WATS never holds a key. WATS is the first and only wallet to combine ERC-4337 and OFT single-token fees, charged instead of native gas, with that burn.