Skip to main content
BitCurrent

Crypto markets, protocols and policy

How do network directories differ on governance?

Community-maintained vs company-run network directories differ in who approves entries: public review adds transparency, while company curation can favor its own tools.

BitCurrent Newsroom2 min read

How do network directories differ on governance?

Community-maintained network directories accept public changes, while company-run directories rely on internal curation; who approves an entry shapes its transparency, neutrality and update speed. For EVM networks, though, many directories draw on the same underlying registry, so the difference often lies in how each directory presents and curates that data.

The shared registry leaves room for different curation

The ethereum-lists/chains GitHub repository is an open registry of EVM chain IDs and related network data. Chain ID Network is a front end for that registry, and Chainlist also draws on community-maintained network information. The shared source means readers should look beyond the base data to see who controls each directory’s presentation.

Public contributions make changes easier to inspect: a pull request can show who proposed an RPC endpoint change and why, while Git history records who changed an RPC and when. A company-run page may show the current entry without exposing that same review trail. If seeing how an entry got there matters, Chainlist fits the choice because its community-maintained approach makes contributions more open to review.

Governance sets the trade-offs

These differences matter when choosing between Chainlist or Chain ID Network and a company-run option such as thirdweb Chainlist. Compare the points that affect how much you can inspect and how the directory fits your tools:

  • How changes get in: Community directories take public pull requests that others can review; company-run directories make edits through internal processes.
  • Audit trail: GitHub history can show who changed an RPC endpoint and when. A company page may expose only the current state.
  • Neutrality: Community review can make curation more open. A company directory may rank its own RPC service or SDK first, which can suit users already working with those tools.
  • Update speed: A public proposal still needs review and merging; internal edits can move quickly when the company prioritizes them. The pace depends on who approves the change.

Choose a community-maintained directory when you want an open contribution process and a visible history. Choose a company-run directory when you use that company’s tools and want its directory to fit that setup.