Same EVM address on different networks
An ordinary EOA derived from the same key has the same address across EVM networks. Its balances, activity and supported assets remain network-specific; contract deployments need separate checks.
Worked example
| Context | Same text? | What remains separate |
|---|---|---|
| Same ordinary EOA key on two EVM chains | Yes | Balances, transactions, chain state |
| Smart contract on two networks | Not guaranteed | Deployment, code and state |
| Custodial deposit instructions | May reuse text | Supported network and crediting rules |
Do not infer deposit support
A service may display an identical 0x address for multiple networks but support only certain assets or deposits. The ability of a key to derive an EOA is different from a service agreeing to monitor and credit that network.
Contract scope matters
A contract at an address on one chain may be absent, different or independently configured on another. CREATE and CREATE2 deployment rules do not remove the need to verify the project’s published chain-specific mapping.
Common pitfalls
- A correct address on an unsupported network can still cause a failed deposit.
- Smart accounts and delegated account behavior add complexity beyond the ordinary EOA case.
Related references
Primary sources
Examples explain identifiers. They are not investment recommendations.