OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Infrastructure

Chains

An MIT-licensed public repository of structured metadata for EVM-based blockchain networks. Its records use CAIP-2 identifiers in filenames and are intended for consumption by applications or self-hosted workflows.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Chains — OpenViST project profile in Infrastructure.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Chains when an EVM-compatible application needs a structured, reusable source of network metadata or when contributors are preparing chain records for repository validation.

Who it is for

  • Developers building wallets and blockchain applications
  • Teams maintaining EVM network configuration services
  • Users of chain metadata lookup or validation tools

Documented uses

  • Find chain identifiers and network IDs
  • Retrieve RPC endpoints, native currencies and faucet information
  • Read supported EVM features and explorer details
  • Create or validate network configuration data
Before you choose

Requirements & limits

It uses the MIT license. No account, pricing or service-availability terms are documented.

  • Records are organized as one CAIP-2-named JSON file per chain.
  • Aggregated chains.json and a smaller chains_mini.json are published through chainid.network.
  • The schema can include RPC endpoints, faucets, currencies, features, icons, explorers and parent-chain relationships.
  • The repository enforces unique chain IDs and documents replay-attack concerns around collisions.
  • The project is intended as metadata infrastructure; it does not provide the blockchain networks or operate the listed endpoints.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Validate chain metadata before submitting a pull request

Run the documented project checks and format chain JSON files before submission.

Before you start

  • A local checkout of the repository
  • Gradle and npm available for the documented commands

Steps

  1. Run ./gradlew run and confirm the checks complete successfully.

  2. Run the command below to format the JSON files.

    Documented command
    npx prettier --write _data/*/*.json

  3. Submit the pull request and monitor CI; re-request review after correcting CI issues.

Expected outcome

The proposed chain metadata has been checked with the documented Gradle task and formatted before review.

Guide limitations

  • The documented process does not establish that CI will pass for every change.
  • The guide covers preparation and submission, not approval or merging.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
1 October 2026
Original website title
ethereum-lists/chains · Official homepage title · retained in its source language
How we review sourcesSuggest a correction