Level 3 · How it worksThe village#230

EVM-compatible chains explained: one key, many villages, separate notebooks

An EVM-compatible chain runs the same contract code and uses the same address format as Ethereum. Your address is therefore the same on all of them, but each chain keeps its own balances. A number called the chain ID, added by EIP-155 in 2016, tells them apart and stops a signed transaction from being replayed on another chain.

The village's notebook worked so well that other villages copied it. Same paper, same columns, same rules for writing contracts on its pages. Your house key even fits the gate in every one of them, because the gates were all built to the same pattern.

Grandma Rosa notices something odd. Her house has the same number in every village. "So my flour is everywhere?" No. Her flour is in the one village where she put it. In the others, her house is there, with the same number, and empty.

That is an EVM-compatible chain: a separate village that copied Ethereum's notebook format. Same address, same kind of contracts, completely separate balances.

What it is

An EVM-compatible chain is a blockchain that runs the Ethereum Virtual Machine, or a close copy of it. Contracts written for Ethereum can run on it with little or no change, and wallets built for Ethereum can sign for it.

The address is the part people notice first. On Ethereum, an account address is made by "taking the last 20 bytes of the Keccak-256 hash of the public key and adding 0x to the beginning" (ethereum.org). There is no chain in that recipe. One private key gives one address, and that address looks the same on every chain that uses the recipe.

How it works

So how does a chain know a transaction was meant for it, and not for the village next door?

Since 2016, by a number. EIP-155, written by Vitalik Buterin and dated 14 October 2016, added a chain ID to every signed transaction (EIP-155). It went live with the Spurious Dragon upgrade at block 2,675,000, on 22 November 2016, which ethereum.org lists as "adding replay attack protection" (ethereum.org).

Some chain IDs, as examples, not recommendations (read on 19 November 2026):

  • Ethereum: 1 (EIP-155).
  • Ethereum Classic: 61 (ECIP-1066).
  • Polygon: 137, Base: 8453 and Arbitrum One: 42161, as listed by Etherscan (Etherscan).

The sum inside every signature

EIP-155 puts the chain ID into the data you sign. In the original transaction format it also goes into a value called v that comes out of the signature. The rule: v is 35 or 36 plus twice the chain ID. Newer transaction types, such as the one EIP-1559 introduced, carry the chain ID as a field of its own (EIP-1559).

  1. Ethereum, chain ID 1: 1 times 2 plus 35 or 36 gives v = 37 or 38.
  2. Ethereum Classic, chain ID 61: 61 times 2 plus 35 or 36 gives v = 157 or 158.
  3. Polygon, chain ID 137: v = 309 or 310.
  4. Base, chain ID 8453: v = 16,941 or 16,942.
  5. Arbitrum One, chain ID 42161: v = 84,357 or 84,358.

Each chain checks the number. A transaction signed for chain 1 doesn't add up on chain 137, and is rejected.

Why did this matter in 2016? The DAO fork had just split Ethereum and Ethereum Classic into two chains with the same history and the same addresses. Without a chain ID, a payment signed on one could be copied and sent on the other. The Foundation's post on the day of the fork already warned users of the old chain to "beware of transaction replay attacks" (Ethereum Foundation). Ben loves that trick: carry Anna's signed slip to the next village and cash it a second time. Since EIP-155, the village's number is stamped on every slip, and the next village just laughs. Good luck, Ben.

Why it matters

  • One wallet, many chains. The same seed phrase and address work everywhere, which is convenient and easy to misread.
  • Same address, different balances. What you hold on one chain says nothing about another.
  • Same contract address, different contract. A contract's address comes from its creator's address and nonce (ethereum.org). The same address on another chain can be empty, or hold something else entirely.
  • Who pays. People who send tokens on the wrong chain, or trust a contract address copied from a different chain. "Sent to the wrong network" covers the recovery side.

Where people get it wrong

  • "My address shows zero, my coins are gone." Check which chain your wallet is looking at first.
  • "Same address, same token." A token address on one chain may be a fake, or nothing, on another.
  • "EVM-compatible means as secure as Ethereum." It means the same code runs. Who validates the blocks, and how many of them, is a separate question for each chain.
  • "The chain ID is just a setting." It is part of what you sign. Pick the wrong one and the transaction goes to a different village.

Check the village before you sign

Before you confirm any transaction, look at the network name in your wallet, and if it shows one, the chain ID. Make sure it matches the chain the receiver or the contract is on. If you add a network to your wallet by hand, check its chain ID against the chain's own documentation, not a link from a message.

The stranger at the gate loves EVM chains. He can show you your own address, with a balance on it, on a chain you've never heard of. The house number is real. The flour isn't.

Frequently asked questions

What does EVM-compatible mean?

An EVM-compatible blockchain runs the Ethereum Virtual Machine or a close copy, so Ethereum smart contracts and wallets work on it with little or no change. It is still a separate chain, with its own blocks, validators and balances.

Why is my address the same on different chains?

An Ethereum address is derived from your public key alone, with no chain in the recipe. So the same private key gives the same address on every EVM-compatible chain. The balances on each chain are separate.

What is a chain ID?

A chain ID is a number that identifies an EVM chain, such as 1 for Ethereum or 61 for Ethereum Classic. Since EIP-155 went live on 22 November 2016, it is included in the data you sign, so a transaction for one chain is rejected on another.

What happens if I send tokens on the wrong chain?

They arrive at the same address, but on the other chain. If you control that address's private key, you can often reach them by switching networks; if the address belongs to an exchange or a contract, recovery depends on them, and may be impossible.

Is an EVM-compatible chain as secure as Ethereum?

Not automatically. Running the same contract code says nothing about who produces and validates the blocks. Each chain's security has to be judged on its own.

Sources

  1. ethereum.org, Ethereum accounts
  2. Ethereum Improvement Proposals, EIP-155: Simple replay attack protection
  3. ethereum.org, The history of Ethereum (Spurious Dragon)
  4. Etherscan API documentation, Chainlist endpoint
  5. Ethereum Improvement Proposals, EIP-1559: Fee market change for ETH 1.0 chain
  6. Ethereum Foundation Blog, Vitalik Buterin, Hard fork completed (20 July 2016)
  7. Ethereum Classic, ECIP-1066: Ethereum Classic Network Description

Read next.