What to Check After an EIP-7702 Authorization
After an EIP-7702 authorization, the most critical check is whether the delegation target contract address is trustworthy — this determines who controls your wallet's execution. The authorization permanently writes into your account's code field until you actively revoke or overwrite it.
The world's largest cryptocurrency exchange by trading volume,leading in security and liquidity.
New user benefit: Enjoy 20% off trading fees upon registration!
Many people treat EIP-7702 like an ordinary "token approval," but it is far more dangerous than an approve call — a single signature can permanently hand your account's execution rights to a malicious contract, and the attacker can act without further confirmation from you. Below is a checklist of what you must verify item by item.
Prerequisites
You have already signed an EIP-7702 authorization transaction (transaction type 0x04) and can see the record in a block explorer or wallet.
You can log into Etherscan or another block explorer to check the transaction details for that address.
You know whether the authorization was initiated deliberately or came from an unknown link/signature request.
Step 1: Confirm on Etherscan whether an EIP-7702 authorization record exists for the address
Etherscan now supports viewing EIP-7702 authorization records separately — this is the first verification step.
Open Etherscan and enter your wallet address.
Look in the transaction list or the dedicated "Authorizations (EIP-7702)" section.
Check whether there is a transaction record of type
SET_CODE_TX_TYPE(0x04).
Completion criteria: Confirm whether the address has an active EIP-7702 delegation record.
If you don't want to scroll through transactions manually, you can use the quick detection site eip7702.app. Just enter the address to check for authorization records (be careful not to connect your wallet).
Step 2: Verify whether the delegation target contract address is trustworthy
If an authorization record is confirmed, look at the address field — this is the target contract address to which your EOA has been delegated.
Case A: The address is one you recognize — an audited official contract (e.g., a well-known wallet vendor's official delegation contract)
Relatively low security risk. Even so, you should still verify that the contract has no known initialization front-running vulnerabilities or storage collision issues.
Case B: The address comes from an unknown source, you've never seen it, or you simply clicked a link for an "airdrop" or "upgrade"
This is a high-risk signal. Many EIP-7702 authorizations point to malicious contracts — according to Dune data, over 97% of EIP-7702 delegations point to a single malicious contract.
Completion criteria: You can clearly answer the question, "Do I know this target contract address, and what does it do?" If you cannot answer this, treat it as a dangerous authorization.
Step 3: Check whether the chain_id matches the current chain
EIP-7702 authorization records include a chain_id field to prevent cross-chain replay.
Case A: chain_id matches the chain you are operating on — normal. Case B: chain_id is 0 — meaning the authorization can be replayed on all EVM-compatible chains that support EIP-7702 (as long as the nonce matches), significantly raising the risk.
Completion criteria: Confirm that chain_id matches the current chain, or at least understand what a value of 0 implies.
Step 4: Determine whether the authorization is one-time or permanent
An EIP-7702 authorization is not a "temporary code injection" that automatically unloads — once written, your account's code field is set to 0xef0100 || address, and the delegation persists until you actively remove or overwrite it.
If you only need a function temporarily, revoke the delegation immediately after use — set the target address to 0x0000000000000000000000000000000000000000 to clear it.
Completion criteria: You clearly know whether this authorization is meant to be kept long-term or revoked after use.
Step 5: Use tools like Revoke.cash to check and revoke suspicious authorizations
If an authorization appears suspicious or is no longer needed, revoke it as soon as possible.
Open Revoke.cash and connect your wallet.
Look for EIP-7702 authorizations (Revoke currently supports detection, but revocation must be done through your wallet).
If your wallet does not support direct revocation, you can send a new
SET_CODE_TX_TYPE(0x04) transaction, setting the target contract address to0x0000000000000000000000000000000000000000to clear the delegation.
Completion criteria: Successfully clear the delegation, restoring the wallet to a pure EOA state.
Common Reason for Failure
Mistaking the "authorization" for an ordinary ERC-20 approve
This is the most dangerous misunderstanding. A normal token approval only allows a contract to transfer specific tokens; an EIP-7702 authorization can redefine the entire execution logic of your account. Any subsequent transaction targeting your address could be intercepted by the delegation contract and executed maliciously. You are not approving a token allowance — you are handing over the "execution rights" of your account.
Risk Warnings
If not revoked, the account can be permanently controlled: As long as the delegation exists, an attacker can trigger malicious operations at any time — without needing your signature again.
Private key still holds supreme authority: Even with a delegation contract authorized, your private key can still override any account operation, including directly revoking the delegation. This also means that if the private key is compromised, an attacker can use the private key to add a malicious delegation directly.
Official wallets may not trigger EIP-7702: Some wallets currently do not support triggering EIP-7702 authorizations, effectively avoiding this risk.
The world's largest cryptocurrency exchange by trading volume,leading in security and liquidity.
New user benefit: Enjoy 20% off trading fees upon registration!
How to Confirm Completion
After completing the above checks, review your address on Etherscan again to ensure there are no suspicious records under the "Authorizations (EIP-7702)" section, or that the delegation target address has been reset to 0x000...000. Also, it is recommended to check on Revoke.cash that the address no longer has any active EIP-7702 authorization.
