What chainlist changes when one wallet spans EVM chains
Chainlist can add an EVM network to a wallet by submitting its chain ID and RPC details for approval; the wallet still controls the active chain, signing and funds.
The Finality Desk5 min read#e0c28e

Chainlist lets a wallet add an EVM network by asking the wallet to store that chain’s identifier and RPC configuration. The same account can then be used on multiple EVM chains, while the wallet keeps the selected chain and transaction approval under the user’s control. In this setup, chainlist supplies network metadata; it does not move tokens, bridge assets or merge balances.
To add a network, find its entry and request the wallet connection, then approve the network addition in the wallet prompt. The linked chainlist reference belongs in this flow as a place to look up a network’s configuration. Connecting the account lets the page make a request; it does not itself authorize a token transfer. Read the wallet’s confirmation before accepting, especially the chain name, chain ID and RPC endpoint.
What does chainlist change in a wallet?
Chainlist changes the wallet’s network configuration, not the account’s keys or assets. For an EVM network, the configuration commonly includes a chain ID, one or more RPC URLs, a display name, native currency details and block explorer URLs. The wallet uses the RPC endpoint to read chain data and submit signed transactions to that network.
The key field is the chain ID. Wallets use it to identify the active EVM chain and to apply transaction replay protection associated with EIP-155. It is distinct from the older network ID returned by net_version. A familiar chain name is not enough to identify a network: names can be reused, and an incorrect or colliding chain ID can make a wallet show misleading network information or sign for a different chain than intended.
For a standard externally owned account, the same private key generally derives the same address across EVM chains. That does not mean the account has one shared balance. Each chain has its own state: token balances, contract deployments, transaction history and native gas asset. A token shown at the same address on two chains may represent separate contracts and separate assets. Moving value between chains requires a bridge or another transfer mechanism, not a network switch.
How does chainlist add a network?
Chainlist asks the connected wallet to process a network-addition request. The wallet evaluates the submitted configuration and displays its own confirmation. In wallets that support the standard, this request uses wallet_addEthereumChain, specified by EIP-3085. The request suggests a chain for the wallet to add; the wallet can reject it, require more fields or validate the values against its own data.
Adding and switching are separate operations. EIP-3085 does not require a wallet to select the new chain after accepting it. A wallet may switch automatically as part of its own behavior, or leave the active chain unchanged. The standard switch request is wallet_switchEthereumChain, specified by EIP-3326. If the network appears in the wallet but the app still reports the previous chain, check the wallet’s network selector and the app’s displayed chain ID.
The RPC URL is the route the wallet uses to communicate with a node or gateway. Different endpoints for the same chain can vary in availability, rate limits, supported methods and privacy practices. An endpoint can return stale or incorrect read data, fail requests or observe the wallet’s IP address and query patterns. A functioning RPC URL is not proof that the chain is legitimate or that its configuration is trustworthy.
What should you check before using a new EVM chain?
Verify the network’s details against information published by the chain’s own maintainers, then compare them with the wallet prompt. Treat the configuration as a connection route that needs checking, not as a certification of the chain or its assets. The practical checks are:
- Confirm the chain ID against a source maintained by the chain’s operators. Do not rely on the display name alone.
- Check that the RPC URL uses HTTPS and belongs to an endpoint you are willing to trust with your requests.
- Confirm the native currency symbol and decimals. These affect how the wallet labels gas and amounts, but do not establish the value or authenticity of a token.
- After adding the network, check the wallet’s active chain ID before signing. A transaction prompt should match the chain on which you intend to act.
If a wallet rejects the request, do not work around the rejection by pasting unverified details into a manual network form. The cause may be a malformed field, a mismatch between the configured chain ID and the endpoint’s reported eth_chainId, or a wallet-specific validation rule. Check the configuration with the chain’s maintainers and retry only when the mismatch is understood.
For most users, adding only networks they expect to use is the clearer choice. A long wallet network menu creates more chances to select a similarly named or inactive chain, while offering no benefit to account portability. Chainlist reduces manual entry, but the wallet remains the authority over account access, chain selection and transaction signing. A network setup is complete only when the wallet’s selected chain, the RPC response and the intended destination agree.