You restored your wallet with a seed phrase or private key. You are sure you used your own backup, but Etherscan still shows a delegation contract address. This does not mean your account was hacked—it may just mean the old delegation record is still on-chain. The private key is restored, but the on-chain state needs to be cleared by you.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
First, understand: private key recovery and delegation state are two different things
Restoring with a seed phrase or private key only lets you regain control of the signing rights for that address. It does not automatically clear any existing code delegation on-chain.
EIP-7702 delegation is stored in on-chain state. When you restore your wallet, you are only rebuilding the local wallet configuration file. The field on the Ethereum chain that records "this address has been delegated to whom" will not automatically reset to zero just because you re-imported the private key. The EIP-7702 specification explicitly supports "clearing delegation on the source chain via a Relayer," which means it is completely normal for delegation to still exist after restoration.
Minimum viable steps
To clear the on-chain EIP-7702 delegation record and restore your account to a normal EOA, follow these steps in order:
Step 1: Check the delegation status
Open Etherscan or another block explorer and enter your wallet address. In the "More Info" area, find the "Authorizations (EIP-7702)" or "Delegate Information" field. If it shows a non-zero address, the delegation is still active and needs to be cleared.
Completion standard: You have confirmed which contract address currently holds the delegation. If it is a trusted official contract, the risk is manageable. If it is an address you do not recognize, you should clear it as soon as possible.
Step 2: Use the wallet's clearing function
Case A: Use Alchemy Wallet API (recommended, has gas sponsorship)
Alchemy's undelegateAccount interface can sponsor gas through the BSO (Bundler Sponsorship) policy. The account does not need to hold native tokens to clear the delegation.
Operation path: Call wallet_prepareCalls and pass in the eip7702Auth capability, pointing the delegation target to the zero address 0x0000000000000000000000000000000000000000. Then use wallet_sendPreparedCalls to submit the signature.
Case B: Use the eip7702reset tool (command line)
After installing Rust, run:
cargo install eip7702reset eip7702reset clear --rpc-url --gas-limit 50000
This tool will interactively prompt you to enter your private key and use a Relayer to pay for gas. If the account has no ETH to pay for gas, you can use the eip7702-clean-delegation tool, which supports sponsored transaction mode—using another account that has ETH as the Sponsor to pay for gas.
Case C: Use Ethers.js to clear manually
Use the authorize method to create an authorization pointing to ethers.ZeroAddress, then send a type 4 transaction:
const revokeAuth = await signer.authorize({
address: ethers.ZeroAddress,
nonce: currentNonce + 1
});
const tx = await signer.sendTransaction({
type: 4,
to: signer.address,
authorizationList: [revokeAuth]
});Completion standard: The transaction is successfully included on-chain, and the "Authorizations" field on Etherscan becomes empty or shows the zero address.
Step 3: Verify the clearing result
Query your wallet address again on Etherscan and confirm that the "Authorizations" field has disappeared or shows 0x0000000000000000000000000000000000000000. If the account's code field has returned to empty, it means you have successfully recovered a normal EOA.
Completion standard: Etherscan shows the delegation address has been cleared, and the account has been restored to a normal EOA.
Troubleshooting
Case A: The wallet interface says "cleared," but Etherscan still shows delegation
The transaction execution part of EIP-7702 is independent of the delegation setting. Even if the outer transaction reverts, the delegation setting will not roll back. So do not only look at the wallet popup's "success/failure" message. Use Etherscan's eth_getCode result as the source of truth.
Case B: The old delegation reappears after clearing
There may be several reasons: First, you cleared it on a different chain, but the old delegation still exists on another chain. Second, your private key has indeed been leaked, and an attacker is re-setting the delegation. If you confirm it is the latter, prioritize moving assets to a new address rather than repeatedly clearing the same address.
Case C: Cannot pay gas or a malicious contract blocks clearing the delegation
EIP-7702 natively supports sponsored transactions, but the recovery support depends on the specific implementation of the wallet and Relayer. Do not accept any third-party Relayer that asks for your private key or requires you to transfer funds. Always follow the wallet's official documentation.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
Final verification
After clearing the delegation, confirm the following two items on Etherscan:
The "Authorizations" field is empty or shows the zero address
The address's code field has returned to empty (normal EOA state)
If both conditions are met, your account has been restored to a normal EOA and can use all functions normally.
Verification method for completion: Confirm on Etherscan that the delegation address has been cleared and the account's code field is empty. If the wallet interface still shows cached prompts, clear your browser cache and check again.
