Skip to main content
BitCurrent

Crypto markets, protocols and policy

EVM Address Reuse and Chain-Specific State

The same wallet address can work on different EVM chains because key-based address derivation omits chain ID, while each chain keeps separate balances and allowances.

BitCurrent Newsroom2 min read

EVM Address Reuse and Chain-Specific State

Yes: the same externally owned account (EOA) can use the same address on Ethereum and Arbitrum because both chains derive the address from the same key, while keeping separate ledgers. Say you send tokens from Ethereum through a lifi bridge to Arbitrum: the destination can credit your familiar address, but the balance there belongs to Arbitrum.

That transfer depends on a route between chains, not on a shared balance. For route context, our look at lifi bridge vs Bungee route choice explains how the two services can find different cross-chain paths.

For an EOA, the private key determines a public key. The address is the final 20 bytes of the Keccak-256 hash of that public key. Chain ID is not part of this address derivation. It enters separately when a transaction is signed, so the same key can sign transactions for different EVM chains without changing its address.

One address, separate chain state

Compatible EVM chains follow the same address rules, but they do not share account state. Ethereum and Arbitrum each track balances, transaction nonces and contract data on their own ledger. A token balance on one chain does not automatically appear on another.

ERC-20 allowances are separate too: each token contract stores its allowance on its own chain. If you approve a spender for an ERC-20 token on Ethereum, that approval changes the Ethereum token contract’s state. It leaves the corresponding Arbitrum allowance unchanged. To spend tokens held on Arbitrum, the relevant Arbitrum token contract needs its own allowance.

This distinction matters when checking a bridge transfer. The address may match across the source and destination, but confirm the destination chain and token balance there; the source-chain balance and approvals tell you nothing about the destination’s state.

Contract wallets need an extra check because their deployment and configuration can vary by chain. For key-controlled EOAs, address reuse follows from shared derivation rules; assets and permissions still live on each chain’s ledger.