# EVM Chain List: Chain IDs, Native Tokens and RPC Support

> An EVM chain ID list: each covered network's chain ID, native gas token, type, stack and settlement layer, plus the RPC methods its public endpoints answer.

Markdown copy of https://voltfincrypto.com/apps/evm-chain-list

**Question:** What is the chain ID and native token of each EVM chain, and which RPC methods do its public endpoints support?

- Kind: Table in Voltfin Strata
- Topic: [Layer 2s](https://voltfincrypto.com/topics/layer-2)
- Chains: Multi-chain, Ethereum, Base, Arbitrum, OP Mainnet, BNB Chain, Polygon, Avalanche, HyperEVM, Monad, Plasma, Berachain, Sonic, Unichain, Linea, Scroll, ZKsync, Mantle, Blast, Celo, Gnosis, World Chain, Ink, Katana
- Status: Planned. The data is not published yet, so this page states no figure; each figure will open its receipt when it is.

Every EVM chain has a chain ID, a number that wallets and contracts use to tell networks apart and that is signed into every transaction so it cannot be replayed on another chain. This table lists each covered EVM chain with its chain ID, its native gas token, whether it is a layer 1 or a rollup, the stack it runs and where it settles.

It also records what developers usually find out the hard way: which JSON-RPC methods the chain's public endpoints answer, from the standard eth namespace to debug and trace methods, whether they serve old state for archive reads and whether websocket subscriptions work. Each value is checked by calling the chain rather than copied from another list, and that check is the row's receipt.

## Blueprint

One row: One row per EVM chain, from the latest daily probe

- **Chain** (`chain`): The network's name, as its own team publishes it.
- **Chain ID** (`chain_id`): The chain's EIP-155 ID, read with eth_chainId on its public endpoints.
- **Native token** (`native_token`): The token that pays for gas on the chain.
- **Type** (`chain_type`): Layer 1, optimistic rollup, ZK rollup, validium or other layer 2.
- **Stack** (`stack`): The software the chain runs, such as the OP Stack, Arbitrum Nitro, the ZK Stack or its own client.
- **Settles on** (`settlement`): The chain a rollup posts data and proofs to, or none for a layer 1.
- **RPC methods** (`rpc_methods`): Which method families the public endpoints answer: eth, debug and trace.
- **Archive reads** (`archive`): Whether public endpoints answer state reads at early blocks.
- **Websocket** (`websocket`): Whether eth_subscribe works on a public websocket endpoint.
- **Block time** (`block_time`, seconds): The median gap between recent blocks, as measured.
- **Checked** (`checked_at`): When the probes behind the row last ran.
- **Receipt** (`receipt`): The calls made, the endpoints that answered and their responses.

## How it will be measured

- The chain ID is read with eth_chainId on each chain's public endpoints and must agree on every endpoint checked; net_version is recorded beside it.
- RPC support is probed method by method: eth_getLogs over a range, debug_traceTransaction, trace_block and eth_subscribe, each recorded as answered, refused or missing.
- Archive support means a balance read at an early block returns a value rather than an error; block time is the median gap between recent blocks.
- Type, stack and settlement layer come from each chain's documentation and contracts, such as a rollup's bridge and proof contracts on Ethereum.

## Data it needs

- `chain_activity_daily` (to build): Transactions, active sending addresses, new addresses, contracts created and gas used on each chain per day, counted from blocks and transactions.
- `gas_blocks` (to build): Base fee, priority fee percentiles, gas used and gas limit for each block on fee-market chains, for a near-live gas tracker.
- `l2_activity_daily` (to build): Per layer 2 per day: transactions, active addresses, fees users paid on the L2, and what the L2 paid Ethereum to settle and post data.
- Source: eth_chainId and net_version on each chain's public endpoints
- Source: Method probes: eth_getLogs, debug_traceTransaction, trace_block and eth_subscribe
- Source: eth_getBalance at an early block, for archive support
- Source: Recent block headers, for the median block time
- Source: Rollup bridge and proof contracts on the settlement layer

## Questions

### What is a chain ID?

A number that identifies an EVM network. It is defined by EIP-155 and included in every signed transaction, so a transaction signed for one chain cannot be replayed on another. Wallets also use it to know which network they are connected to.

### Where can I find a chain's ID?

In this table, or from the chain itself: any RPC endpoint answers eth_chainId with it. The table makes that call on each chain's public endpoints and shows an ID only when every endpoint checked agrees.

### What is the difference between chain ID and network ID?

The chain ID, from eth_chainId, is the one signed into transactions. The network ID, from net_version, identifies the peer-to-peer network and usually matches it, but not on every chain. Wallets and signing code should use the chain ID.

### Why do some RPC endpoints refuse debug or trace calls?

Tracing replays transactions and costs far more than an ordinary read, so many public endpoints disable debug and trace methods or limit them. The table shows which public endpoints answer them, which tells a developer when a private node or a paid endpoint is needed.

### What is an archive node?

A node that keeps the state of every past block, so it can answer balance or contract reads at any height. Full nodes prune old state, so a read far in the past fails on them. The archive column shows whether a chain's public endpoints serve such reads.

## Glossary

- **EIP-155**: The Ethereum standard that adds the chain ID to transaction signatures, so a transaction is valid on one chain only.
- **JSON-RPC**: The request format EVM nodes answer, with methods grouped in namespaces such as eth, net, debug and trace.
- **Settlement layer**: The chain a rollup posts its data and proofs to, and whose bridge holds its deposits.

## Related apps

- [Ethereum Layer 2 List Ranked by Activity, Fees and Value](https://voltfincrypto.com/apps/ethereum-layer-2-list)
- [Layer 1 Blockchain List: Activity, Fees and Staking](https://voltfincrypto.com/apps/layer-1-blockchain-list)
- [Multicall3, Permit2 and EntryPoint Addresses by Chain](https://voltfincrypto.com/apps/multicall3-permit2-entrypoint-addresses)
- [WETH and Wrapped BTC Token Addresses by Chain](https://voltfincrypto.com/apps/wrapped-btc-eth-token-addresses)
- [Stablecoin Contract Addresses: USDT, USDC and More by Chain](https://voltfincrypto.com/apps/stablecoin-contract-addresses)
- [Ethereum TPS: Mainnet and Layer 2 Transactions per Second](https://voltfincrypto.com/apps/ethereum-tps)

Build it in Voltfin Studio: https://app.voltfincrypto.com/signup?next=%2F