Chainlist can help you add an EVM network to a compatible wallet when you confirm the intended chain ID and choose an RPC endpoint the wallet can reach. The network setting tells the wallet where to send requests; it does not move assets or approve a transaction. If an application asks you to switch to a network you do not have, identify that network before accepting suggested settings.
A Directory Shows Network Identity and RPC Access
An EVM network directory pairs a network’s identity with connection details a wallet can use. When an application names a network absent from your wallet, Chainlist can surface a proposed chain ID and RPC URL; Chainlist network search helps narrow entries with similar names. A similarly named directory or service may have a different operator or data, so treat its entries as separate until you verify them.
Ethereum, Polygon, Arbitrum, and Optimism are recognizable EVM mainnets, but an application may ask for a testnet instead. Mainnets carry production activity and assets with real value; testnets are for testing and have separate chain IDs and balances. A familiar network name alone does not settle which environment the application expects. Read the network name and chain ID in the application’s instructions, then compare the chain ID with that network’s official documentation before accepting settings.
The chain ID identifies the chain for the wallet and transaction signing. An RPC URL identifies a server that relays the wallet’s requests to that chain; several endpoints can serve the same chain ID. The native currency symbol and block explorer URL help the wallet label balances and show transactions, but neither substitutes for a matching chain ID. I would reject an entry with a conflicting chain ID even if its name looks right.
Wallet Setup Adds and Selects the Verified Network
Adding a network changes the wallet’s saved configuration; selecting it changes which chain the wallet queries and uses for transactions. A typical compatible wallet flow is:
- Find the network. Search for the exact mainnet or testnet the application requests, and compare near matches by chain ID.
- Verify the details. Compare the chain ID and RPC guidance with the network’s official documentation. Chainlist network entries may offer several RPC URLs for one chain, so note which endpoint you choose.
- Connect the wallet. Use a wallet that supports the EVM chain and network addition, then approve the connection request if you want the application to see your address.
- Review the network request. The wallet may show the name, chain ID, RPC URL, currency symbol, and explorer URL. Resolve any mismatch before approving.
- Add and select it. Confirm the settings in the wallet, then switch to that network. If it already exists, inspect the saved settings and select it instead of creating a duplicate.
Chainlist can populate the request, but your wallet’s confirmation screen controls whether the entry is saved. Suppose, illustratively, your wallet starts on Ethereum and an application requires Polygon. Before the change, the wallet queries Ethereum; after adding and selecting Polygon, it queries Polygon through the chosen RPC. Your account’s keys remain in the wallet and Ethereum funds stay on Ethereum. You can use the same EVM address on Polygon, but moving assets between chains requires a separate bridge or transfer route.
Network Setup Has No Gas Fee but Later Actions May
Saving network settings costs no on-chain gas because the wallet is recording configuration, not sending a transaction. Connecting a wallet and switching the selected network also do not incur network gas. A later transfer, contract interaction, or bridge action may require fees paid in that network’s native asset; the wallet should display the transaction for separate approval.
Most setup time goes into confirming the right chain and responding to wallet prompts. With matching details and a responsive public RPC, this may take only a few minutes; an unreachable endpoint or a wallet that needs manual entry extends it. Some RPC providers offer endpoints that require an API key, account, or paid plan. Those are separate service terms, so read them before choosing the endpoint.
Failed Setup Usually Points to a Mismatch or RPC Access
An incorrect chain ID, an unsupported wallet flow, or an unavailable RPC endpoint explains most failed additions. If the wallet rejects a duplicate chain ID, inspect its existing entry and select it when its settings match the official network details. If the wallet cannot accept an application’s configuration request, use its manual network entry screen with those verified fields.
If the chain saves but the application cannot load, the RPC may be down, rate limited, or restricted to users with an API key. Try another endpoint for the same verified chain ID; changing the RPC server can restore access without changing the chain. If the wallet opens but shows no expected balance, compare mainnet with testnet, then identify the chain where the assets actually reside. Adding a network does not create funds there.
Top comments (0)