After enabling EIP-7702 delegation, you may find that NFTs sent to you by others never arrive. The sender shows a successful transfer, and the on-chain transaction status is marked as success, but the NFT does not appear in your wallet balance.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
Most likely, your delegation contract does not implement the callback functions required for NFT transfers. This is not a wallet malfunction; it is a contract compatibility issue.
First, understand: Why 7702 affects NFT reception
When someone transfers an ERC-721 or ERC-1155 standard NFT to you, the receiving contract needs to implement specific callback functions like onERC721Received or onERC1155Received. If the receiver is a regular EOA (externally owned account), the protocol usually allows direct transfers without requiring these callbacks.
But when you enable EIP-7702 delegation, your address has code deployed on-chain, so the system treats it as a contract. If the delegation contract does not implement the corresponding receiving functions, the transfer transaction will behave abnormally. Although block explorers may show the transaction status as "Success," the NFT is actually locked in an intermediate contract.
Official documentation clearly states that when the receiver is an EOA with 7702 delegation enabled, if the delegation contract lacks the corresponding receiving callback functions, not only can NFTs get stuck, but ETH may also be locked on the target chain due to a missing receive() function.
Minimal viable steps
Goal: Get NFTs to arrive normally and restore your address's ability to receive NFTs. Follow these steps in order:
Step 1: Verify the actual transaction status using a block explorer
Open Etherscan, enter your wallet address, find the relevant NFT transfer record, and check the "Internal Transactions" tab on the detail page for any anomalies. If the transaction status shows "Success" but "Internal Transactions" contains warnings like "ERC721 transfer failed," it means the NFT is stuck in an intermediate step and you need to follow the corresponding bridge recovery process.
Completion standard: Confirm the on-chain status of the NFT transfer to determine whether the asset is locked on-chain or the transfer was never initiated.
Step 2: Check if the delegation contract lacks receiving functions
Find your delegation contract address on Etherscan and check whether the contract code includes receive() and onERC721Received() functions.
- Case A: The contract has these functions, but the NFT still has not arrived. The implementation of these functions may be faulty, such as excessive gas consumption causing a revert. In this case, you need to clear the delegation first, restore EOA status before receiving NFTs, or contact wallet support to confirm the delegation contract's compatibility list.
- Case B: The contract does not have these functions. You need to clear the EIP-7702 delegation so that your address returns to a normal EOA state before it can receive NFTs normally. To clear the delegation, send a type 0x04 transaction pointing to the zero address. If you are using MetaMask, you can use its built-in "revoke delegation" feature. For other wallets, you can use tools like eip7702reset.
Completion standard: After clearing the delegation, initiate the NFT transfer again. The transaction succeeds and the NFT appears in your wallet balance.
Troubleshooting
- Case A: After clearing the delegation, the NFT still has not arrived. This means the NFT may already be locked in a bridge contract. In this case, you need to follow the bridge protocol's recovery process. The general solution is to clear the delegation on the source chain, then go to the L1/L2 cross-chain message contract page and resend the relayMessage transaction.
- Case B: The wallet shows "This type of asset is not supported for receiving." Your delegation contract may come from a third party rather than the wallet's official whitelist. The official Ethereum guide clearly states that DApps should not directly request EIP-7702 authorization signatures. They must rely on standard wallet interfaces such as ERC-5792 and ERC-6900. If your wallet does not support that interface, it may fail to handle NFTs correctly when receiving them.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
Verification and wrap-up
After clearing the delegation, open Etherscan and enter your wallet address. Confirm that the delegation address in the "More Info" section shows as the zero address or has disappeared. Then ask the sender to resend the NFT transfer and confirm that it arrives normally.
How to verify completion: The NFT appears in your wallet balance, and Etherscan shows the transfer status as "Success" with no error events. If using a cross-chain bridge, you can also find the corresponding incoming record on the target chain's block explorer.
