/evm-atlas

Target Chains & Chainscout

Blockscout and Chainscout index many EVM networks, but this skill only uses them for chains in references/generated/target-mainnets.json. Do not use Chainscout to expand scope. If a requested chain is not in that JSON file, ask the user to file a feature request in https://github.com/PaulRBerg/agent-skills.

Chainscout API

No API key required. Live UI: https://chains.blockscout.com/

Single-chain response shape:

{
  "name": "Gnosis",
  "native_currency": "XDAI",
  "isTestnet": false,
  "layer": 1,
  "rollupType": null,
  "ecosystem": "Ethereum",
  "explorers": [{ "url": "https://gnosis.blockscout.com/", "hostedBy": "blockscout" }]
}

explorers[].hostedBy:

• blockscout - Blockscout-operated; candidate for the unified PRO host (api.blockscout.com/{chain_id}/...). Still confirm with a live call; not every hosted target chain is fronted by the PRO host.
• anything else - community-operated. Per-instance only; use explorers[].url directly (no key).

Use scripts/resolve-chain.sh <chain_id> to extract these fields as key=value lines. The helper refuses non-target chain IDs and rejects Chainscout responses whose name does not match the target chain. For name -> chain_id, use references/generated/target-mainnets.json and references/generated/chain-aliases.json first.

Target Chains Observed in Chainscout

Observed on 2026-07-08. Presence here does not override the canonical explorer/RPC metadata in references/generated/target-mainnets.json.

Target Chains Absent or Unsafe in Chainscout

Use Etherscan, a documented exceptional-history route, or the public RPC/explorer in references/generated/target-mainnets.json for these.

Contributing

Missing or wrong Blockscout registry data is fixed via PR to https://github.com/blockscout/chainscout. Requests to add non-target chains to this skill belong in https://github.com/PaulRBerg/agent-skills.