01

Same address, different networks

One Ethereum wallet address works not only on Ethereum mainnet but on many layer 2s and Ethereum-compatible chains. With the same private key, the same address, and similar transaction formats, a question arises: what happens if someone takes a transaction signed for one network and submits it to another?

Below, we look at how the chain ID prevents that risk, known as transaction replay. It covers the danger of older transaction formats without a chain ID, how the same address differs across networks, and what to check before signing.

02

What a replay attack is

A transaction signature proves that the account owner approved its contents. If two networks share the same signing rules and nothing in the signed data distinguishes the network, a transaction signed for one can be valid on the other. Copying a public transaction and submitting it to another chain is called a replay attack.

The risk was most acute when one chain split into two. Both chains started with the same balances and rules, so a transfer sent on one could execute on the other too.

Consider a hypothetical case: suppose that just after a split a user sends 10 coins to a friend on chain A. Without a chain ID in the format, anyone could copy that signed transaction and submit it on chain B, and the user would have sent 10 coins there too without meaning to.

03

What the chain ID does

EIP-155 solved this by including the chain ID in the data being signed. A signature for Ethereum mainnet, chain ID 1, is not valid on a network with a different chain ID. Transactions in the later EIP-1559 format carry chain_id explicitly as a field.

Chain IDs and replay by network (examples)
NetworkChain IDSame address usableSignature reusable on another chain
Ethereum mainnet1YesNo (chain ID mismatch)
OP Mainnet10YesNo
Arbitrum One42161YesNo
Sepolia testnet11155111YesNo
Legacy transaction without chain IDNoneYesMay be replayed on chains with the same rules

The chain ID binds a signed transaction to one network. Legacy transactions without one risk reuse on other chains with the same signing rules.

04

Replay protection with the nonce

As Ethereum.org's page on transactions explains, within one network the account nonce prevents the same transaction from being processed twice. The chain ID prevents replay across networks, and the nonce prevents replay within one. Together they ensure a signed transaction executes exactly once on exactly one network.

Nonces are counted separately on each network. Having sent your hundredth transaction on mainnet does not mean your nonce on a layer 2 is 100. Matching nonces on two chains is precisely what made replay possible before chain IDs.

05

Same address, different things

An ordinary account address derived from a private key is the same on every Ethereum-compatible network. Smart contract addresses are different. There is no guarantee that a contract at an address on mainnet exists at the same address elsewhere, and a completely different contract may sit there.

When using a smart contract wallet or handling token contract addresses, check addresses network by network. Tokens with the same name often have different contract addresses on each network, and assets sent to the wrong network can be hard to recover.

Some projects deploy their contracts at the same address on many networks on purpose, which helps, but it is a choice each project makes rather than a rule. The official documentation for each network is the place to confirm it.

06

Checks before signing

Before approving a transaction or signature request, work through these items.

  1. Confirm the network name and chain ID shown in your wallet match the network you intend.
  2. If a website asks you to switch networks, compare its chain ID and RPC address with official sources.
  3. Check token and contract addresses separately for each network using official sources.
  4. For typed-data signatures, check that the domain's chainId matches the current network.
  5. If a wallet asks for a legacy signature without a chain ID, do not sign until you understand why.
07

What the chain ID does not prevent

The chain ID stops signed transactions from being replayed on other networks, but not users from signing on the wrong network themselves. Phishing sites may switch users to a fake network, or users may transact on another network believing it is mainnet.

Some off-chain signed messages are designed without chain information and may be valid across networks. Even messages that look harmless, such as login signatures, are worth checking for whether they name the network and app.

08

What was simplified

The chain IDs here are widely known examples, and new networks keep appearing. Transaction formats and how wallets display them can change with upgrades.

When checking, use EIP-155, Ethereum.org, and each network's and wallet's current official material along with the date of each. This guide does not recommend buying or selling anything.