Data methodology

What is included

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 are source records with record type, source date, source links, and boundary text. They are not launch stage labels, rankings, recommendations, or operational readiness claims.

Verification metadata

Chain pages expose the source-review date, ISO timestamp, run ID, source set, review cadence, and latest EVM eth_chainId probe evidence when available. The current chain metadata run is source-monitoring-2026-06-10, checked with source-monitoring-refresh at June 10, 2026.

Source hash snapshots, source change snapshots, and RPC chain ID probes are generated by explicit operator scripts. They are evidence inputs only; they do not automatically change chain metadata and they are not uptime, latency, or reliability claims. See /monitoring/ for the current human-readable snapshot.

Scope limits

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 source-cited reference metadata, monitoring evidence, and correction workflows.

Machine-readable files

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/.