Type declaration: This article is a Type B "pre-education" piece. The main purpose of the title is to answer a common question about whether delegation status syncs across chains. It explains the cross-chain mechanics of EIP-7702.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
You authorize EIP-7702 on one chain, then use the same wallet address on another chain. The wallet gives no warning, so you think "it should be fine."
The answer is: it does not sync automatically. But if you signed with chainId set to 0, it may also take effect on other chains.
Core concept: 7702 delegation works per chain
The EIP-7702 authorization tuple contains a key field called chain_id. It decides which chains the delegation applies to.
When you delegate your wallet to a contract, the signed content includes four pieces of information: chain_id, address (the contract address you are delegating to), nonce (the account nonce), and your signature.
When chain_id is set to a specific chain number (for example, Ethereum mainnet is 1, Arbitrum is 42161), the delegation is only valid on that one chain. If you delegate on Arbitrum and then go to Optimism, your wallet's code field is still empty, just as if you had never delegated.
The chain_id = 0 case: the key cross-chain risk
There is a special case: if the chain_id in the authorization signature is set to 0, the delegation will "apply to all chains."
The official Ethereum documentation clearly warns: When using chain_id = 0, the delegation applies to all chain IDs. Only delegate to immutable contracts (never delegate to proxies), and only delegate to contracts deployed using CREATE2 (with standard initcode). Otherwise, your delegation puts your account at risk on all other EVM chains.
Scammers exploit this. They create a malicious authorization with chain_id set to 0 and trick you into signing it. Once signed, your wallet on all EVM-compatible chains may be controlled by that malicious contract.
In practice: how to check delegation status
Case A: Check delegation on a specific chain
Open Etherscan (or another chain's block explorer), enter your wallet address, and find the "Authorizations (EIP-7702)" section under "More Info." The contract address shown there is your delegation status on that chain. If it is empty or shows the zero address, there is no delegation.
You need to repeat this on every chain: Etherscan for Ethereum, Polygonscan for Polygon, Arbiscan for Arbitrum. Delegation status does not sync across chains.
Case B: You are not sure what chain_id you signed with before
If you cannot confirm the chain_id used when signing, treat it as the worst case: check delegation status one by one on every EVM chain you have used, and confirm there is no suspicious delegation contract.
Completion standard: You can confirm on each chain's block explorer that the "Authorizations" field is empty or shows a trusted official contract address.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
What to do if you suspect cross-chain delegation
Risk warning: If a scammer tricked you into signing a delegation with chain_id = 0, your wallet may be controlled on all EVM chains. Checking just one chain and thinking you are safe may miss risks on other chains.
[What to do]: Remove any possible malicious delegation on all chains.
[How to do it]: On every EVM chain you have used, perform a delegation removal operation: send a new EIP-7702 transaction (Type-4) pointing the delegation address to 0x0000000000000000000000000000000000000000 (the zero address). You need to do this separately on each chain, and each chain requires its native token for gas.
[Completion standard]: Confirm on each chain's block explorer that the delegation address has been cleared.
