How Do I Check and Revoke an EIP-7702 Delegation on My Wallet?
⚠ After Oct 29 breaches: check your wallet free — read-only, 30 seconds →A wallet with a malicious EIP-7702 delegation can be emptied by a sweeper bot minutes after you top it up — without you signing anything. Checking takes two minutes, costs nothing, and works for any EVM address. Here is the complete procedure: read the delegation status, interpret what you see, and revoke safely if something is wrong.
How do I look up my EIP-7702 delegation on a block explorer?
Open Etherscan (or the equivalent explorer for your chain) and paste your address into the search bar. On the address page, find the “Delegated Address” field — Etherscan surfaces it in the account summary for any address carrying EIP-7702 state. If you don’t see the field at all, the address has no delegation and you’re clean on this axis.
What do the three EIP-7702 check results mean?
The explorer shows one of three states: Null (never delegated, nothing to do), a labeled contract you knowingly upgraded to (expected — verify the label), or an unknown contract address (danger — revoke before using the address again).
“Null” — no active delegation. The address has never delegated or the delegation was cleared. Nothing to do.
A labeled contract from a wallet you knowingly upgraded. If you (or your wallet app) upgraded to a smart-account implementation — Passkey wallets, some embedded wallets — you’ll see a recognized implementation name. This is expected. Verify the label matches what you actually opted into.
An unknown contract address. This is the danger state. An attacker who phished a 7702 authorization out of you delegated your account to a sweeper contract, and anything you send there can be swept. An unknown label with a transaction history you don’t recognize means: stop using this address until you’ve revoked.
How do I revoke an EIP-7702 delegation safely?
Revoking a delegation means sending a type-0x04 transaction carrying a
signed authorization whose address field is the zero address
(0x0000000000000000000000000000000000000000). Per the
EIP-7702 specification: when the
authorization’s address is the zero address, the protocol does not write a
new delegation indicator — it clears the account’s code entirely,
returning the wallet to a normal EOA (the “Null” state on explorers).
Practical routes:
- Wallet-native: recent MetaMask, Rainbow and most major wallets expose “remove delegation” or “reset smart account” actions that build the 0x04 transaction for you.
- Manual: construct a type-0x04 transaction with the authorization tuple pointing at the zero address. The signature in the tuple must come from the delegated account itself (it signs the authorization), but the transaction broadcast can come from any account — which is exactly how the sponsorship route below works. Tools like our delegation checker show the current state so you can verify the revoke landed.
The sponsorship route (the safest path for compromised addresses): because the authorization is a signature and the transaction is a broadcast, a different wallet can submit your revoke — paying the gas itself. If your address is compromised, this beats funding it directly: sign the revoke authorization (with the compromised key, one signature), then have a clean wallet broadcast the type-0x04 transaction paying gas from its own balance. The compromised address never receives funds for sweepers to take. If you must fund it directly instead, fund with only the gas needed for the revoke — nothing more.
Critical ordering detail: if a sweeper is watching the account, it may race you — the sponsorship route removes that race entirely. After the revoke, verify the “Delegated Address” reads Null (or that the address’s code is empty — the CLI check eip7702-check exits clean). If your seed phrase itself was phished, revoking the delegation is not enough: the attacker holds the key. Move everything to a fresh wallet with a new seed — see the first 24 hours after a drain.
How do I verify the revoke worked and re-check my habits?
After the revoke, re-read the Delegated Address field — it must show Null. Then check what let the attacker in:
- Did you sign an authorization request you didn’t initiate? That’s the classic one-signature drainer pattern.
- Do you have unlimited token approvals still active? Those outlive delegation cleanup — audit them separately.
- Use a hardware wallet or clear-signing wallet for anything holding real value; blind-signed typed data is how most 7702 phishes land.
FAQ
How do I check if my wallet has an EIP-7702 delegation? Open your address on Etherscan and read the “Delegated Address” field: Null means none, a labeled contract you chose is expected, an unknown contract means revoke.
What does “Delegated Address: Null” mean? Your account is a normal EOA with no active delegation — the safe state.
Can I remove a malicious delegation myself? Yes, with a type-0x04 transaction re-delegating to the null indicator. Wallets increasingly offer this as a one-click action. Fund the address with only the gas needed — sweepers may be watching.
I revoked but my funds were already swept — what now? The delegation was the persistent backdoor; funds swept before the revoke are gone absent recovery action. Never pay unsolicited “recovery agents” — most are second-wave scammers.
Is an unknown delegation dangerous if I never send funds there again? The account stays a liability: any accidental deposit can be swept, and the delegation can interact with approvals you forgot. Revoke or abandon the address entirely.
Educational content, not financial advice. Read-only guidance; never share your seed phrase with any checking tool. Last updated October 2026.