chainslist helps you find an EVM network’s chain ID and RPC endpoint before adding that network to a compatible wallet. If you already have verified network details, you can enter them manually; if you need a chain list to find those details and connect the network in one click, use chainslist.
An entry identifies an EVM network and gives you the settings a wallet needs to reach it. EVM stands for Ethereum Virtual Machine: an EVM network works with Ethereum-style wallets and apps. Each network still has its own record of accounts and transactions, so choosing the right one matters.
The chain ID is the network’s numerical identifier. For example, Ethereum Mainnet uses chain ID 1, while Optimism uses chain ID 10. The network name is a readable label; it is less useful for checking that you have the right chain because names can be entered differently. A chain ID is neither your wallet address nor a token’s contract address.
The RPC endpoint is the address of a node your wallet talks to. Through that node, the wallet can ask for a balance, read information from an app and submit a transaction you have signed. A network may have several RPC endpoints with the same chain ID: they reach the same chain through different providers. An entry may also give a currency symbol and a block explorer address, which helps you look up transactions.
A one-click connection sends the chosen network’s settings to a compatible wallet for your approval. In a typical EVM wallet flow, the request includes the chain ID and an RPC URL. Your wallet presents the proposed network, and you decide whether to add it. If the network is already saved, the wallet may offer to switch to it instead.
Once added, the wallet saves those settings. When you select the network, it asks that network’s RPC endpoint for account data; when you approve a transaction, the wallet signs it with your account and sends it through the endpoint. The connection request does not give the directory your recovery phrase or authorize a transaction. You should never need to type a recovery phrase into a network directory.
“One click” describes how the request starts, not the whole approval process. The wallet still needs to be available, and you still need to inspect and approve what it shows. If no wallet prompt appears, check that your wallet is unlocked and able to respond to websites in the browser you are using. You can enter the same network details manually if the connection request does not work with your setup.
Manual setup puts the directory’s details into your wallet’s add-network form. Wallet menus differ, but the fields serve the same purpose whether you use MetaMask or another EVM wallet. Keep the network entry open while you fill them in so you can compare each value.
Use the number format the wallet requests. Optimism’s chain ID is usually written as decimal 10 in a wallet form; technical requests may show the same value as hexadecimal 0xa. Those are two ways to write one number, not two networks. If the wallet reports that the chain ID and RPC endpoint do not match, recheck both fields before saving.
Adding the network is a settings change in your wallet. It does not create an account on that chain, move funds or send a blockchain transaction, so the act of adding it does not incur a gas fee. You will need the network’s native gas asset when you later make a transaction there.
Check the chain ID against the network’s official documentation, then check that the RPC URL is intended for that chain. A directory such as chainslist helps you locate and connect the settings, but the chain operator’s published details are a useful independent check before you use a network for funds. This matters most when a network name looks familiar or several similar entries appear.
The chain ID tells your wallet which chain a transaction is for; it does not tell you who runs an RPC endpoint. An endpoint can fail, lag behind the chain or return unreliable information. If a wallet shows stale balances or cannot submit transactions, another verified RPC for the same chain ID may solve the connection problem. Do not change the chain ID merely to make an endpoint respond.