Skip to the article
Web3 Hub

Markets, protocols and policy, reported

What mistakes happen when adding an EVM network to a wallet?

Common mistakes when adding a network to a crypto wallet include a wrong Chain ID or RPC, a testnet mix-up and missing tokens; verify each before sending.

By Web3 Hub Newsroom3 min read

What mistakes happen when adding an EVM network to a wallet?

You can add an EVM network and see the right assets by checking its settings before approval and verifying your address afterward. Common mistakes are entering the wrong Chain ID or an untrusted RPC endpoint, choosing a testnet, and expecting tokens to appear without importing them.

  • Match the Chain ID and RPC endpoint to the network’s official details.
  • Confirm you selected the main network, not its testnet.
  • Import token contracts, then compare your wallet balance with the block explorer.

Which details should you verify before adding?

Use the network project’s own documentation for its Chain ID and a trusted RPC endpoint. Chainlist is an EVM network directory with Chain IDs and RPC endpoints; chainlist.cc covers the same task of adding a network, where checking these settings matters. MetaMask’s network-addition instructions also advise checking network details before adding a custom connection.

  • Check the Chain ID. It identifies the network to the wallet. A value copied from an old forum post or random social post can be wrong, even when the network name looks right.
  • Check the RPC endpoint. This is the service your wallet contacts to read blockchain data and send requests. A malicious RPC can return false balances and see your IP address and wallet addresses. Prefer an endpoint published by the project or a provider it names.
  • Check mainnet versus testnet. Testnets are for trying transactions. Their tokens come from a faucet and have no value. If you mean to use the live network, confirm the wallet’s network name before sending funds.
  • Check Native currency and Block explorer. The Native currency is the network’s built-in transaction-fee token; the Block explorer lets you look up an address and its on-chain activity. Confirm both match the network you intend to use.

How do you confirm the wallet shows the right assets?

With your wallet unlocked, look up the network in its official docs or Chainlist, approve the add request in MetaMask, switch to that network, and import any needed tokens. Importing uses the token contract address from the network’s Block explorer; a token may not show in the wallet until you add that address.

Adding or removing a network changes the wallet’s connection settings, not the blockchain. Your assets stay on-chain. The same EVM address works across EVM networks, so if you sent tokens on the wrong one, add that network to the wallet and use the same address to view them there. Recovery depends on the tokens existing at that address on that network.

Finish by opening your address on the network’s Block explorer and comparing its token balance with the wallet. When they match, the wallet is reading the intended network and showing the assets held at that address.