# Chain IDs: why the same address can exist on different networks A chain ID is a number used to distinguish transaction-signing domains on Ethereum-compatible networks. EIP-155 incorporated it into legacy transaction signing to limit cross-chain replay. It does not identify an asset by itself, prove a network is trustworthy or automatically protect every off-chain signature. Evidence: [Simple replay attack protection](https://eips.ethereum.org/EIPS/eip-155); [Typed structured data hashing and signing](https://eips.ethereum.org/EIPS/eip-712) Canonical: https://degreesofsatoshi.com/encyclopedia/ethereum-chain-id/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T18:12:41.505Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Replay scope:** EIP-155 changes the signed legacy transaction payload to include a chain ID. ([Simple replay attack protection](https://eips.ethereum.org/EIPS/eip-155)) - **Address:** Address bytes alone do not specify a network. ([Ethereum accounts](https://ethereum.org/en/developers/docs/accounts/); [Simple replay attack protection](https://eips.ethereum.org/EIPS/eip-155)) - **Typed data:** An EIP-712 domain can include chainId, but applications must implement replay protections. ([Typed structured data hashing and signing](https://eips.ethereum.org/EIPS/eip-712)) ## One address string can refer to several chain states The same key can correspond to the same address bytes on several compatible networks while balances, contracts and transaction histories differ. Choosing a network changes which ledger you query or submit to. A token contract address must therefore be paired with the chain. A familiar symbol and address display are insufficient if the wallet is on a different network. Evidence: [Ethereum accounts](https://ethereum.org/en/developers/docs/accounts/); [Simple replay attack protection](https://eips.ethereum.org/EIPS/eip-155) ## Bind authorization to the intended domain Without appropriate domain separation, a signed transaction valid in one setting might be accepted elsewhere. EIP-155 addresses this for the transaction format it specifies. The protection depends on the actual transaction signing rules and chain configuration. It is not a certification system that makes any network using a particular number safe. Evidence: [Simple replay attack protection](https://eips.ethereum.org/EIPS/eip-155) ## Off-chain signatures need their own checks Typed-data applications can bind a signature to a chain and verifying contract, alongside an application name or version. Nonces and deadlines address additional reuse questions. Review these fields when signing. A chain-aware transaction format does not automatically secure a separate permit or order-signature implementation. Evidence: [Typed structured data hashing and signing](https://eips.ethereum.org/EIPS/eip-712); [Permit Extension for EIP-20 Signed Approvals](https://eips.ethereum.org/EIPS/eip-2612) ## Questions ### Does switching networks in my wallet move the funds? No. It changes the network context the wallet displays or interacts with. Moving assets between networks requires a separate transfer or bridge mechanism. Evidence: [Ethereum accounts](https://ethereum.org/en/developers/docs/accounts/); [Ethereum JSON-RPC](https://ethereum.org/en/developers/docs/apis/json-rpc/) ## Claims and scope ### ethereum-chain-id-quick-answer A chain ID is a number used to distinguish transaction-signing domains on Ethereum-compatible networks. EIP-155 incorporated it into legacy transaction signing to limit cross-chain replay. It does not identify an asset by itself, prove a network is trustworthy or automatically protect every off-chain signature. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-chain-id-fact-replay-scope Replay scope: EIP-155 changes the signed legacy transaction payload to include a chain ID. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-chain-id-fact-address Address: Address bytes alone do not specify a network. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-chain-id-fact-typed-data Typed data: An EIP-712 domain can include chainId, but applications must implement replay protections. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Simple replay attack protection](https://eips.ethereum.org/EIPS/eip-155) — Ethereum Improvement Proposals. Transaction chain ID domain separation; not blanket protection for all signatures. Locator: Specification. Retrieved: 2026-10-02T17:03:42.312Z. - [Typed structured data hashing and signing](https://eips.ethereum.org/EIPS/eip-712) — Ethereum Improvement Proposals. Typed-data encoding and domain fields; replay protection is application-specific. Locator: Specification; Security Considerations. Retrieved: 2026-10-02T17:03:42.239Z. - [Ethereum accounts](https://ethereum.org/en/developers/docs/accounts/) — ethereum.org contributors. Key-controlled and code-controlled accounts, balances, nonces and storage. Locator: Account types; An account examined; Account creation. Retrieved: 2026-10-02T17:03:41.958Z. - [Permit Extension for EIP-20 Signed Approvals](https://eips.ethereum.org/EIPS/eip-2612) — Ethereum Improvement Proposals. Signed token allowances, deadlines, nonces and domain checks. Locator: Specification; Security Considerations. Retrieved: 2026-10-02T17:03:42.295Z. - [Ethereum JSON-RPC](https://ethereum.org/en/developers/docs/apis/json-rpc/) — ethereum.org contributors. RPC response fields, transaction receipts, call simulation and log filtering. Locator: eth_getTransactionByHash; eth_getTransactionReceipt; eth_call; eth_getLogs; eth_getCode; eth_estimateGas; eth_getBalance; eth_getStorageAt; eth_getTransactionCount; default block parameter. Retrieved: 2026-10-02T17:03:42.060Z. ## Revision history - 2026-10-02: First publication after primary-source research and independent automated verification. ## Cite this entry Degrees of Satoshi editorial project. “Chain IDs: why the same address can exist on different networks.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-chain-id/