Key points
- Token-approval revocation does not clear an EIP-7702 delegation; inspect the account’s code separately.
- A delegation marker is 0xef0100 plus a 20-byte implementation address. Empty code reads 0x.
- A later execution failure does not roll back processed delegation changes. Re-read state after inclusion.
- Clearing delegation on one chain does not clear another chain or repair a leaked private key.
The approvals page is clean. The wallet address has not changed. Neither observation answers the question that matters after a suspicious smart-account authorization: whose code can this account execute?
To remove EIP-7702 delegation, use your wallet’s supported reset or smart-account controls, then read the account’s code on the same network. Clearing delegation should leave empty code, represented as 0x. An empty approvals list is a different check.
This guide covers externally owned accounts using EIP-7702 on compatible EVM networks. It is not a reset procedure for every smart-contract wallet, and it does not establish whether a particular address was attacked.
What EIP-7702 changes at your address
Ethereum’s EIP-7702 guidelines describe a pointer from an ordinary key-controlled account to deployed contract code. Your address can stay the same while gaining smart-account behavior. The original private key retains control; delegating to sophisticated code does not, by itself, turn that single key into a multisignature security model.
The functionality has legitimate uses. Batching can combine actions, and sponsorship can let another account pay transaction fees. A delegation is therefore a capability to identify and understand, not automatic evidence of theft.
The EIP-7702 specification defines the onchain marker as 0xef0100 followed by a 20-byte implementation address. The setting persists until replaced or cleared. Changing token allowances does not clear that account-code marker.
First identify the permission you are removing
Keep a short record of the account, network, suspicious request and transaction hash, if one exists. Then separate the jobs:
| Check | Question it answers |
|---|---|
| Website connection | Can this site request actions through my wallet interface? |
| Token allowance | Can a specific spender move this token through its allowance? |
| Permit2 signature | Can a signed authorization still be used under its nonce and expiry rules? |
| EIP-7702 delegation | Which implementation code is assigned to this account? |
Panther’s token-approval guide and Permit2 cancellation guide handle the middle rows. A clean result in one row should not be used as the answer to another.
Revoke.cash documents a separate delegations tab for inspecting EIP-7702 settings. Its current guide says it cannot revoke those settings there; removal belongs inside the wallet because most wallets do not expose it to external apps. Do not mistake an inspection page for a completed revocation.
Read the account code without signing anything
Use the full account address and a trusted RPC for the intended chain. Ethereum’s execution API reference defines eth_getCode as a read of code at an address and block. This JSON-RPC request template performs that read; replace the address placeholder before using it:
{
"jsonrpc": "2.0",
"method": "eth_getCode",
"params": ["YOUR_FULL_ACCOUNT_ADDRESS", "latest"],
"id": 1
}
No wallet connection, signature, seed phrase or private key is needed for that public-state query. The RPC endpoint determines which chain you are reading. Save the network and observation time; for a reproducible record, use an explicit block number rather than a moving latest result.
Interpret the returned code narrowly:
0x: empty code at that address in the queried state. It does not prove the key is secret or token permissions are clean.- Exactly 23 bytes beginning
0xef0100: an EIP-7702 delegation marker. The remaining 20 bytes identify its implementation. - Other nonempty code: do not classify it as a standard EIP-7702 marker. Confirm the account type before attempting a reset.
Security Alliance’s verification guide recommends comparing the implementation with your wallet provider’s documented contract. A familiar name or explorer label is not a substitute for the full address. If the delegation is unexpected, investigate before using the account again.
Remove EIP-7702 delegation through your wallet
For MetaMask, its current instructions describe the Extension route as account selector → three dots beside the account → Account details → Smart account. Disable the toggle for the relevant network, review the request and confirm. On Mobile, open the account selector and three-dot menu, then Smart account and the network toggle. Network gas is required.
Menu names follow MetaMask’s current documentation. Other wallets have different menus and support. If your account points to an unfamiliar implementation and the reset option is missing, use the provider’s independently verified support documentation rather than a search-ad “recovery” page.
At protocol level, removal requires a valid authorization to the zero address, included in a type 0x04 transaction. Sending tokens or ordinary ETH to the zero address does not perform that operation. Do not improvise a transfer to reproduce it.
Verify state even when the transaction says failed
Foundry’s delegation documentation highlights a crucial rule: authorization processing is not undone when the transaction’s later execution reverts. Conversely, the EIP allows an invalid authorization tuple to be skipped. A transaction receipt alone is therefore insufficient evidence of the intended delegation change.
After inclusion, read the account code again on the same chain. For a completed clearing operation on a previously delegated EOA, expect 0x. Record the hash, implementation before removal and resulting code. If the marker remains, the intended clearing has not been established; inspect the authorization and network before signing another attempt.
Here is a hypothetical verification record, not a live wallet test:
| Observation | Chain A | Chain B |
|---|---|---|
| Before removal | Delegation marker present | Delegation marker present |
| After reset submitted only on A | Code reads 0x |
Marker still present |
| Supported conclusion | Delegation cleared on A at the observed block | B still needs its own investigation |
The same key and address can have different state across networks. Ethereum’s guidelines also distinguish authorizations bound to a chain from those signed with chain ID zero. A zero-chain authorization can be reusable on compatible chains if its other validity conditions hold; clearing one network does not establish the state of another.
A leaked key needs a new security boundary
Security Alliance warns that clearing delegation cannot repair a stolen private key: its holder can authorize another delegation. If a sweeper is taking incoming funds, do not casually top up that address with ETH for gas. Its guide describes a separate broadcaster paying for a clearing transaction, but an active compromise calls for a coordinated recovery plan, not repeated public experiments.
If backup words or keys were exposed, follow the separate recovery-phrase compromise guide. Preserve evidence and secure remaining assets under fresh keys. Removing one delegation cannot return stolen funds or establish that all other permissions have disappeared.
Reviewed November 17, 2026. Technical basis: the Ethereum specification and guidance, wallet-provider instructions, Foundry and Security Alliance; inspection-tool behavior checked against Revoke.cash.
Sources
- 01EIP-7702: Set Code for EOAs · Ethereum Improvement Proposalseips.ethereum.org/EIPS/eip-7702
- 02Pectra EIP-7702 guidelines · ethereum.orgethereum.org/roadmap/pectra/7702
- 03Switch to or revert from a smart account · MetaMasksupport.metamask.io/configure/accounts/switch-to-or-revert-from-a-smart-account
- 04Verifying EIP-7702 Transactions · Security Allianceframeworks.securityalliance.org/wallet-security/signing-and-verification/verifying-7702/
- 05EIP-7702 account delegation · Foundrywww.getfoundry.sh/cast/eip-7702-delegation
- 06What Is EIP7702? · Revoke.cashrevoke.cash/learn/wallets/what-is-eip7702
- 07eth_getCode execution API reference · Ethereum Execution APIsethereum.github.io/execution-apis/next/api/methods/eth_getCode/
Responses
No responses yet. Start the conversation.
Panther Journal — The intelligence brief
Stay ahead of the story.
Free. New investigations delivered when published. Unsubscribe anytime.






