How Do EVM Network Directories Choose Which Chains to List?
How EVM network directories decide which networks to list: teams submit chain data to GitHub, automated checks validate it, and directories display the result.
The Blockchain Brief Desk4 min read
EVM network directories usually list chains after teams submit structured metadata to a shared GitHub registry; the directory displays entries that pass data checks. The ethereum-lists/chains repository supplies chain data used by Chainlist and Chain ID Network. Its checks enforce format and unique identifiers, so a listing records a submission that passed data checks, not a quality endorsement.
How does a chain get into an EVM network directory?
A chain team proposes a network by opening a pull request against the registry. The submission is a JSON file describing the network, rather than a request for a directory operator to assess the chain’s commercial prospects or technical quality.
- Network name and shortName
- Chain ID and network ID
- RPC endpoints
- Native currency details
- Explorer links and other metadata
These fields give wallets and Web3 tools the parameters they need to identify a network and connect to it. The Chain ID identifies the network for EVM transactions; the RPC endpoint is the service a wallet contacts to read network data and submit transactions. Currency and explorer fields help apps display information alongside that connection.
The repository stores entries as individual JSON files. A proposed entry therefore becomes a reviewable change: maintainers can inspect the metadata, automated workflows can check its structure, and the repository records whether the change was merged.
What do the registry checks actually validate?
Automated checks validate whether the submitted entry follows the registry’s schema and uses identifiers that do not conflict with existing entries. The schema defines expected fields and their types; uniqueness checks prevent a second entry from reusing a Chain ID or shortName already in the registry.
A file with a missing required field, an invalid value or a duplicate identifier can fail before maintainers merge it. Passing those checks means the metadata is structurally acceptable and the identifiers are available in that registry. It does not establish that the chain is active, secure, widely used or supported by a particular wallet.
Maintainers still merge the pull request, so the workflow has a human review step. But the central gate is data validity, not a ranking of chains. That is why test networks and abandoned networks can remain discoverable: the registry’s job is to publish network metadata, not to certify that every entry is a good choice for current use.
Why can Chainlist show RPCs that differ from a chain’s entry?
Chainlist combines registry chain metadata with RPC information it maintains separately. Its repository accepts pull requests for additional chain entries and for RPC endpoints added to chains that already appear on the site. That separate data path means the RPCs shown by the directory can differ from the endpoints in the chain’s official registry entry.
Say a team submits a new network with its name, Chain ID, native currency, explorer and one RPC endpoint. The registry checks the JSON and identifiers. After maintainers merge the pull request, directories that use the registry can display the network. Later, someone can submit an additional RPC to Chainlist’s own repository; that endpoint can appear there without changing the original registry file.
At this point, Chainlist, available at chainlist.cc, is one place where the distinction matters: a directory’s network metadata and its displayed RPC collection can come from different maintained records. The network’s presence tells you how its entry entered the directory. It does not tell you that every endpoint has the same operator or status as the chain team’s own endpoint.
What does a network listing tell a wallet user?
A listing tells a wallet or Web3 tool that metadata for the network was submitted, passed the registry’s format and uniqueness checks, and became available for directories to display. The directory turns those records into a searchable interface, so users can find a Chain ID and connection details without manually assembling each field.
For an everyday wallet connection, the distinction is practical. A network name and Chain ID identify the configuration; the selected RPC determines which endpoint handles the wallet’s requests. Because test chains and abandoned chains can also be listed, users should check the chain’s official site before relying on an entry or connecting an application to one of its RPCs.
EVM network directories generally reflect submitted data rather than a central verdict on which chains deserve to exist. The registry decides whether an entry is well-formed and uniquely identified; that is what makes a listing useful for discovery, and what limits what it says about the network’s quality.