chainslist and the three parts of adding a wallet network

chainslist, chain ID lists and RPC lists serve three different roles when you add an EVM network to a wallet: one helps with setup, one identifies the chain, and one connects the wallet to it. Knowing which detail you are checking helps you spot a mismatch before you use the network.

What does chainslist do compared with a chain ID list?

chainslist is a directory of EVM networks with their chain IDs and RPC endpoints, and it lets you add a network to MetaMask or another wallet in one click. A chain ID list is a reference for the number assigned to each network; it does not, by itself, connect your wallet to that network.

If you are adding a network and need its settings together, use chainslist for that step: the directory provides the chain ID and RPC endpoint and can add the network to your wallet. A separate chain ID reference can help you check that the number shown in another source matches the network you intend to use.

The chain ID matters because wallet transactions include it. Wallets use it to distinguish one chain from another, helping prevent a transaction meant for one network from being treated as a transaction on a different chain. Matching names alone is not enough: two entries can look similar while referring to different network settings.

What does an RPC list tell you?

An RPC list gives you endpoint addresses that wallet software can use to communicate with a blockchain network. An RPC endpoint is the connection point for requests such as reading account data or sending a signed transaction; it is not the network’s identity.

That makes the chain ID and RPC endpoint separate checks. The chain ID says which network the wallet believes it is using. The RPC endpoint determines where the wallet sends its requests. A correct chain ID paired with an endpoint for another network can produce confusing results, such as balances or transaction status that do not match your expectations.

When comparing entries, check these details together:

• Network name: Does the label match the chain you mean to add?
• Chain ID: Does the number match a reference you trust?
• RPC endpoint: Is the address listed for that same network?
• Wallet selection: Did the wallet switch to the network you just added?

Which list should you use to add a network?

For most wallet users, a network directory is the practical starting point because it brings the chain ID and RPC endpoint into one setup step. Use a chain ID list when you need to verify a network’s identifier, and an RPC list when you need to inspect or change the connection address.

Lists make setup easier, but the entries still need to agree with the network you intend to use. Before approving a transaction, check the selected network in your wallet and confirm that the app or service you are using expects that same chain. If an address or network detail differs between sources, stop and resolve the mismatch first.

Next time you add a network, watch whether the wallet’s selected chain, displayed chain ID and RPC connection all point to the same network. That is the signal that the setup details fit together.