Who runs the RPC endpoints you add to your wallet?
Does Chainlist host its own RPC endpoints? No. It lists URLs run by node providers, network teams and public operators; your wallet contacts the saved endpoint directly.
Web3 News Editorial2 min read

Chainlist does not run the RPC endpoints your wallet connects to; it is an EVM network directory that passes a selected URL and network details to your wallet. The directory at chainlist.cc is a useful next stop when you need to identify a network entry before checking which URL your wallet saved. Each endpoint is run separately, by a node provider, a network team or a public operator.
The assumption is easy to make: you find a network and choose “add” in one place, so it can seem like that same service handles the connection. In practice, adding a network gives your wallet the endpoint address to contact.
Chainlist lists RPC endpoints; separate operators run them
Chainlist is a directory, while each RPC URL points to an operator’s server. The project’s extra RPC entries are maintained in the open-source DefiLlama/chainlist GitHub repository; that does not make the repository’s maintainers the operators of every endpoint listed there.
These are the separate roles:
- Directory: Provides network details, including a chain ID, native currency and RPC URL.
- RPC operator: Runs the endpoint that receives and answers your wallet’s JSON-RPC requests. It may be a node provider, a network’s own team or a public operator.
- Wallet: Stores the network configuration and sends requests to the saved URL. MetaMask and Rabby Wallet are examples of wallets that can use network RPC endpoints.
When you approve adding a network, the wallet receives the network details and an RPC URL. After that, the wallet sends JSON-RPC requests directly to that address; the directory is not relaying them.
Your wallet keeps the RPC URL after setup
Your wallet saves the chosen endpoint, so the connection can keep working while the directory is offline. You also do not need to return to the directory just to change the saved URL: open the network’s settings in your wallet and switch to another endpoint you trust.
That distinction helps when a network connection is slow or failing. The issue may be with the selected endpoint or its operator, rather than the directory that supplied the address. If another suitable endpoint is available, replacing the saved URL in MetaMask, Rabby Wallet or another compatible wallet changes where requests go.
For a connection problem, check the RPC URL saved in your wallet and try a different endpoint if needed. The wallet’s network settings are where the active connection is configured.