$ show ethereum-lists/chains
This repository is a community-maintained, curated registry of EVM-compatible blockchain networks. It contains thousands of JSON files under `_data/chains/`, each defining a chain's metadata: RPC endpoints, native currency, explorers, icons (IPFS CIDs), status (active/deprecated/incubating), parent L2 relationships, and feature flags. The dataset is the primary asset, designed for consumption by wallets, dApps, block explorers, and infrastructure tooling that needs up-to-date chain information. Beyond the data, the repository includes a Kotlin-based processor that validates all chain definitions (schema compliance, icon size/format, IPFS retrievability, ENS address checks) and produces aggregated `chains.json` and `chains_mini.json` outputs. A published Kotlin model library (`model/`) and an HTTP loader (`httpsloader/`) enable programmatic access. CI pipelines enforce formatting, schema validation, and per-PR checks. The project is hybrid: its core value is the dataset, but it also delivers a well-engineered application layer for validation, aggregation, and distribution. The registry answers questions like 'What RPC endpoints are available for chain X?', 'What is the native currency of chain Y?', 'Which chains are L2s of Ethereum?', and 'What explorers support EIP3091?'. It serves as a single source of truth for EVM chain metadata, reducing fragmentation across the ecosystem.
The LLM identified 3 files worth highlighting for reuse:
Defines the core `Chain` data class with Moshi JSON adapters, along with `Explorer`, `NativeCurrency`, and other supporting types. Published as a standalone Maven artifact, this model can be reused by any Kotlin project that needs to parse or generate chain metadata. It demonstrates clean separation of concerns and idiomatic Kotlin data modeling.
A JSON Schema document that formally defines the structure of chain definition files. It specifies required fields (`name`, `chain`, `chainId`, `rpc`, etc.), optional fields (`icon`, `explorers`, `parent`, `status`), and constraints. This schema is reusable for validating any EVM chain metadata collection and can be integrated into other projects' CI pipelines.
A lightweight HTTP client library that fetches the aggregated chain list from `chainid.network` and deserializes it into the model classes. It handles HTTPS, caching headers, and error responses. This component can be extracted and reused by any application that needs to consume the chain registry at runtime, providing a clean API for dynamic chain discovery.