Chainlist helps you find EVM network settings and ask a compatible wallet to add them, but a listing does not establish that the network or its RPC endpoint is safe. The directory supplies configuration data; your wallet handles approval, an RPC server handles requests, and the blockchain has its own security. Verify each part for the network you intend to use.
Directory Entries Supply the Settings an EVM Wallet Needs
A directory entry gives your wallet the details it needs to identify a network and contact an endpoint. Chainlist's EVM network entries cover Ethereum, Polygon, Arbitrum, and Optimism, among others. Testnet entries describe separate testing environments; choosing one does not put your wallet on that network's mainnet or move assets between them.
- Network name: The label your wallet displays. It helps you recognize a saved network, but anyone can copy a familiar name.
- Chain ID: The number used to distinguish one EVM chain from another when transactions are signed. A mainnet and its testnet have different IDs.
- RPC URL: The address of a server your wallet contacts to read network data and broadcast signed transactions. It is a service endpoint, not the blockchain itself.
- Native currency: The name and symbol your wallet may display for the asset used to pay transaction fees on that network.
- Block explorer: An optional address your wallet may use to open transaction and account records in a browser.
These fields describe how to configure a connection. They do not show who operates the network, whether its rules protect users, or whether the listed server will answer accurately. Treat a complete entry as enough information to begin checking, rather than evidence that those checks have been done for you.
Official Network Documentation Provides the Identity to Match
The intended network's official documentation is the reference for its chain ID and connection details. Compare the documented ID with the directory entry and with the value your wallet asks you to approve. A Chainlist entry can carry recognizable branding, but a name or logo does not establish chain identity. If you meant to add a testnet, make the comparison against that testnet's documentation, not the mainnet's.
Consider two entries offered to the same wallet for the same claimed network. Both use its familiar name, and both RPC URLs respond. In the first case, the chain ID matches the ID in the network's official documentation; in the second, it differs. The first has a plausible configuration to assess further. The second has an identity mismatch to resolve before use. Responsiveness and branding are shared between the cases, so neither explains that difference. Even the matching ID does not prove that the RPC server reports data honestly or that the chain is secure.
Also compare the network's stated requirements with your purpose. A wallet may support EVM network settings yet lack a feature you expected to use on that chain. Confirming the identity tells you which network you are configuring; it does not establish that every wallet feature or application will work there.
Wallet Approval Saves the Network Settings You Select
A supported wallet request presents proposed settings for you to review before the wallet saves them. Look at the network name, chain ID, and RPC URL in the approval prompt. Approval authorizes a configuration change in your wallet; it does not transfer funds or certify the operator of the network or endpoint.
The comparison with official documentation gives you a reason to try the settings, while the endpoint still needs its own assessment. With that identity check done, use Chainlist to request the network in a compatible wallet. A Chainlist wallet request is useful because it passes the fields to the wallet together, but the values shown in the wallet prompt are the ones you are agreeing to save.
If your wallet does not support the request, enter the documented fields manually if it supports custom EVM networks. After either path, inspect the saved settings and confirm that the wallet has selected the network you intended. A successful “add network” message only means the configuration was stored; it does not show that the endpoint is responding or that you are viewing the chain you meant to use.
RPC Endpoints Affect Wallet Data and Availability
An RPC server supplies much of the network data your wallet displays, while the blockchain determines which transactions become part of its history. Wallets communicate with these servers using JSON-RPC, a message format for requests such as reading a balance or broadcasting a signed transaction. A listed URL can fail, rate-limit requests, or return misleading data. An endpoint that responds today may also become unavailable later.
The operator of an RPC endpoint may see the IP address, wallet addresses, and requests sent to it. A dishonest server could misstate a balance or transaction status in its replies, so an RPC listing guarantees neither honest responses nor privacy. It also says nothing about the security of the underlying chain. Endpoint behavior and blockchain security require separate judgments, even when the chain ID in your wallet matches the documented value.
An RPC server does not acquire your signing keys merely because your wallet connects to it. Your wallet still asks you to approve a transaction before signing. That distinction matters when diagnosing a problem: a wrong or unresponsive balance display may come from the endpoint, whereas a signed transaction is a separate wallet action.
Adding Network Settings Costs No Gas
Saving an EVM network configuration does not send an onchain transaction, so adding it incurs no gas fee. The time it takes depends on reviewing the identity and endpoint, whether your wallet supports automatic requests or needs manual entry, and how quickly the endpoint responds. A wallet can save the settings even when the endpoint is too slow or unavailable to show useful account data.
Using the network afterward is different. Sending a transaction generally requires the network's native asset for gas, according to that network's rules. If a wallet prompts for a signature or payment while you are only trying to add settings, inspect what that separate request would authorize before proceeding.
Network Setup Does Not Move Assets or Supply Gas
Chainlist does not hold your funds, bridge assets, or provide gas. Adding a network changes which chain your wallet can view and use; it does not move tokens that already exist on another chain. A balance visible on one network therefore should not be expected to appear on another merely because you switched the wallet's selected network.
If using the new network requires assets there, that is a separate task with its own network and transaction details to verify. Keep the setup decision narrow: confirm the intended chain ID, review the saved RPC URL, and establish that the wallet can reach it. Any request to sign a transaction, transfer assets, or pay for access calls for its own explanation and review.