Chainlist provides EVM network details that can help with wallets beyond MetaMask, but automatic setup requires a wallet that accepts website requests to add or switch networks. If no prompt appears, use Chainlist to find the fields, then follow your wallet’s own network settings. Wallet edition, platform, and supported chains determine which route works.
Chainlist fields are readable without connecting a wallet
The directory’s network details remain visible even if you have not connected a wallet. An entry typically gives a network name, chain ID, RPC URL, currency symbol and block explorer URL. The RPC URL is the address your wallet uses to retrieve chain data and submit transactions. Your wallet’s documentation tells you which of these fields its network form accepts and where they belong.
Start with the particular network you need, including whether it is a mainnet or testnet. Similar names can refer to different chains, so compare the chain ID and RPC details from a Chainlist network search with the network’s official documentation before entering them. That comparison matters most when you are about to give a wallet an RPC URL: the endpoint will handle its requests for balances, transaction data and broadcasts.
Wallet support determines which setup route works
An EVM-compatible wallet can support a chain without accepting a website’s request to add it. These are separate capabilities. When a wallet does accept such a request, it can display the proposed network settings for your approval and save them after you confirm. Adding the settings and switching to that network may involve separate prompts. The website cannot make your wallet support a blockchain it does not already support.
Consider two browser wallets that both support Polygon and are used on the same platform. One accepts requests from websites to add networks, so its user sees a prompt with the proposed details. The other does not accept those requests, so its user sees no prompt, even though Polygon is supported. In the second wallet, the route might be a built-in network selector or a custom-network form. The missing prompt alone tells you about that website interaction, not whether the chain is available.
There is a further boundary: some wallets support an EVM chain but do not allow arbitrary custom RPC URLs. If the intended chain is built in, select it through the wallet’s own controls. If it is absent and the wallet offers neither a supported addition prompt nor custom network settings, directory fields cannot add that chain to that wallet. Features can differ between a wallet’s browser extension and mobile edition, so use the documentation for the edition you have.
A successful setup loads data from the intended chain
The practical route begins in your wallet’s documentation: establish that it supports the intended chain, then find out whether it offers a network selector, website prompts or manual custom-network settings. After comparing the directory entry with official network documentation, approve a supported prompt or enter the verified fields in the wallet’s form. Use the chain ID to distinguish the intended chain from another network with a similar name.
When the settings are saved, select the network if the wallet has not switched to it already. The setup is complete when the wallet displays the intended chain and retrieves public network data. A delayed or empty display can reflect an unresponsive RPC endpoint; it does not by itself prove the chain is unsupported. If the wallet permits another RPC URL, use one verified against the network’s official documentation and try loading the data again.
Network setup is free, while transactions have separate costs
Saving or selecting network settings uses no gas because it does not send a transaction. The time it takes depends on the wallet’s prompt or manual form and on how quickly the RPC endpoint responds. A later on-chain transaction has its own network fee, paid in the currency that chain requires. Connecting to a network also does not move funds there or give an app access to assets on that chain.
A listing is useful network information, not a guarantee that every endpoint is trustworthy or that every app works with the chain. The Chainlist RPC list may offer more than one endpoint, but an endpoint’s presence does not replace checking its operator or the network’s official details. Once your wallet shows the correct chain and loads its data, any remaining app or balance issue calls for a separate check of that app’s network support and where your funds actually reside.