Methodology
How Main.net checks chain fields.
Each chain page is built from checked public docs, visible source snapshot provenance, source links, and a correction path if something looks wrong.
What the pages include
Chain rows include network name, chain type, chain ID, gas token, public RPC endpoint, explorer, source links, verification status, and a safety note. Launch rows list source type, source date, source links, and boundary text. They are not launch stage labels, rankings, recommendations, or operational readiness claims.
How reviews stay traceable
Each chain page shows the automated source snapshot date, ISO timestamp, run ID, source set, and latest EVM eth_chainId probe evidence when available. The snapshot issource-monitoring-2026-07-04, generated with source-monitoring-refresh at.
Source hash snapshots, source change snapshots, and RPC chain ID probes are generated by explicit operator scripts. The snapshot timestamp is not a manual review date or deadline. These artifacts do not automatically change chain metadata and they are not uptime, latency, or reliability claims. See /monitoring/ for the current human-readable snapshot.
API v1 and legacy exports still include lastVerified,verifiedAt, updated, reviewCadence, andneedsReviewAfter as deprecated compatibility aliases for automated source-snapshot evidence and scheduling; they do not prove a manual field review or promise a manual review deadline. New integrations should use thesourceSnapshot* fields.
What Main.net does not do
Main.net does not publish live uptime, latency, block lag, price, TVL, volume, airdrop eligibility, rankings, or investment recommendations. The public service is limited to checked chain fields, monitoring evidence, and correction paths.
Download the data
The current static datasets are available at /chains.json and/launches.json. Category and glossary datasets are available at /network-categories.json and/glossary.json. These endpoints are generated at build time from the same data used by the HTML pages.
The versioned API is documented at /api/ and described by/api/v1/openapi.json. Source and freshness data are available at /sources/ and /review/. Derived gas token and explorer directories are available at/gas-tokens/ and /explorers/.