Nov 17, 2026

Our wallet had an EIP-7702 delegation we did not know about, and our USDC payments stopped working

TL;DR
  • What happened: ChainAnalyzer's own wallets had a "delegation" setting on them that we did not know about. Because of it, every USDC payment we signed was rejected. No funds were lost.
  • The cause: a feature in a wallet app (Phantom) for swaps without network fees. The feature turns the wallet into a smart account. The change stays until you remove it.
  • Who this affects: anyone using a wallet app on Ethereum, Base, Polygon and similar chains. Especially people who pay services with a signature only, such as x402.
  • What to do: check your address on a block explorer (a website that shows on-chain records). If you do not need the delegation, remove it. If you do not recognise it, consider moving your funds to a new wallet.

1. What happened

ChainAnalyzer sells API access through x402. With x402 you pay in USDC (a token kept equal to one US dollar) each time you call the API. The payer does not send a transfer. They only hand over a signature that says "you may take this amount".

On 17 November 2026, ChainAnalyzer tried to pay its own API from a test wallet. It was an ordinary wallet on Base. All 18 API routes (endpoints) rejected the payment.

  • The rejection came from the check run by the facilitator, the service that relays the payment.
  • The reason given was "invalid signature".
  • The balance was enough (about 12 USDC).
  • No payment went through, so no money moved.

The same steps had worked before.

2. What we found

When we looked up the wallet's address, it held "code". An ordinary wallet has none. This was the mark of a delegation under EIP-7702.

A delegation tells a wallet "work the way this program says". The wallet then behaves like a smart account (a wallet run by a program). The address does not change. The owner does not change. EIP-7702 arrived with Ethereum's Pectra upgrade in May 2025[3][4].

Facts we checked

  • The delegate was a smart account program from Alchemy. It is SemiModularAccount7702 (v1.0.0) at 0x69007702764179f14F51cdce752f4f775d74E139. Alchemy lists it in its public list of deployed contracts[2].
  • The same delegation was on other wallets too. The test wallet had it on Base and Polygon. The wallet that receives our x402 payments had it on Base and Ethereum.
  • On Polygon, the test wallet had never made a transaction. The only record was the delegation itself.
  • The receiving wallet also got the delegation while it sat unused. On Ethereum it had not sent a transaction itself since April 2026, yet the delegation was there (as with the test wallet on Polygon). On Base its last own transaction was in July 2026, and three delegation authorizations were recorded after that (its transaction counter had moved three past the number of transactions it sent itself, and each authorization moves the counter by one). So the delegation may have been set again, not just once.
  • The transaction that set the delegation did not appear in the wallet's own history. Another address had sent it and paid the fee.
  • The key had not been replaced. When we asked the delegate program, the registered signer was still the wallet itself.
  • No funds had left.

The cause

The cause was a feature in the Phantom wallet app. Phantom's official help page says[1]:

  • Swaps without network fees work by delegating the wallet to Alchemy's smart contract, using EIP-7702.
  • A notice appears at swap time. "Okay" upgrades the account. "Disable Gasless" opts out.
  • The delegation stays active until you remove it.
  • To remove it, go to "Settings > Security & Privacy > Remove account delegation".
  • A compromise of the smart contract could put your assets at risk.

So there is a notice, and you can say no or remove it later. Even so, the person at ChainAnalyzer who used the wallet did not remember switching. After a delegation, the address and balance stay the same. Nothing obvious changes on the usual screens. That is why owners rarely notice one.

What we do not know yet

  • Why it was also set on Polygon, a chain we never used. EIP-7702 allows an authorization that is not tied to one chain[3]. We have not checked whether that is what happened here.
  • Whether extra modules (parts that add permissions) were installed in the delegate. We did not check this.
  • When, and during which action, the delegation was set. We could not pin it down, including the times it was set again on Base.

3. Why the payment stops working

An analogy first.

Think of a bank counter. When a private customer hands in a form, the bank checks the signature itself, on the spot. If it matches, the form goes through.

Now suppose the customer's record has been changed to "company". The bank no longer checks the signature itself. It phones the company's front desk and asks, "Is this form OK?" The front desk only accepts forms in its own format. A form with just a personal signature gets a "no". So a correct form from the real customer is still refused.

The same thing happens with USDC.

  • Before checking a signature, USDC looks at whether the payer's address has code (a program)[5].
  • If there is no code, USDC treats it as an ordinary wallet. It works out the signer from the signature and checks that it matches the payer.
  • If there is code, USDC treats it as a program wallet. It asks that address, "Is this signature OK?" This way of asking is a standard called ERC-1271[7].
  • A wallet with a delegation counts as an address with code[3]. So the question goes to the delegate program.
  • The delegate program expects signatures in its own format. A plain signature did not pass, which we believe is why the payment was rejected as invalid.
With a delegation, USDC checks the signature a different way (drawn from the USDC public source and the EIP-7702 specification).

After we removed the delegation, the same 18 routes all accepted payment.

This is not a bug in USDC or x402. USDC is built this way so that program wallets can use it too[5]. A delegated wallet is correctly treated as a program wallet, and as a result a plain signature no longer works.

Technical note (for developers)
  • x402's EVM "exact" scheme calls transferWithAuthorization directly on tokens that support EIP-3009[8].
  • In USDC (FiatTokenV2_2), transferWithAuthorization ends in SignatureChecker.isValidSignatureNow, whether the signature is passed as v, r, s or as bytes[6].
  • isValidSignatureNow makes a staticcall to ERC-1271 isValidSignature when extcodesize(signer) > 0, and uses ecrecover otherwise[5].
  • A delegated address holds 0xef0100 plus the 20-byte delegate address, and EXTCODESIZE returns 23[3]. So it takes the ERC-1271 path.
  • The USDC implementation on Base is FiatTokenV2_2, verified on the explorer[9].
  • The facilitator returned invalid_exact_evm_payload_signature (contract call failed: execution reverted). We have not read the delegate's source to confirm exactly which format it expects.

4. Check your own wallet

Anyone can check, for free. A delegation is set per chain, so check each chain you use.

  1. Open the chain's explorer: Etherscan for Ethereum, Basescan for Base, Polygonscan for Polygon.
  2. Paste your address into the search box at the top and open it.
  3. Look at the top of the address page, where the balance is shown. With a delegation, you will see something like "Delegated to" and the delegate's address. The wording differs between explorers.
  4. Look at the tabs too. If your ordinary wallet has a "Contract" or "Code" tab, and the content starts with 0xef0100, it has a delegation.
  5. If a delegate address is shown, click it. Check its name (for example SemiModularAccount7702) and whether its source code (the program itself) is published. If it is, the "Contract" tab usually carries a mark such as a green tick.
For developers

Call eth_getCode through an RPC endpoint (a service that answers questions about the chain). If the result starts with 0xef0100, there is a delegation, and the next 20 bytes are the delegate's address[3]. ChainAnalyzer's wallet scan also shows whether an address is delegated, and to what, on EVM chains.

5. Remove the delegation

ChainAnalyzer removed the delegations in two ways. Both worked.

Option A: remove it in your wallet app (recommended)

We removed the receiving wallet's delegation this way. For Phantom[1]:

  1. Open Phantom and go to "Settings".
  2. Open "Security & Privacy".
  3. Choose "Remove account delegation" and follow the prompts.
  4. When done, use the steps in section 4 to confirm on the explorer that the delegation is gone. Check every chain.

After removal, fee-free swaps stop working and swaps go back to normal network fees[1]. If you do not want the feature, choose "Disable Gasless" when the notice appears. Other wallet apps may have similar features. Check each app's help pages.

Option B: remove it yourself with your key (for developers)

We removed the test wallet's delegation this way. Sign an authorization whose delegate is the zero address (no program) with the same key. Put it in an EIP-7702 transaction (type 4) and send it[3]. It is one transaction, to yourself, for zero value.

One warning. Our first attempt failed because the gas estimate was too low. Some RPC endpoints leave out the cost of the authorization (25,000 gas each) from the estimate. Set the gas limit yourself, with some room.

6. If you do not recognise the delegation

A delegation can only be set with a signature from the wallet's own key[3]. Someone else can pay the fee, but the authorization must be signed by the owner's key. So there are three possible reasons:

  1. A wallet app feature set it. This was ChainAnalyzer's case.
  2. You were tricked into signing it, for example on a fake website.
  3. Your key has leaked, and someone else signed with it.

The second and third are dangerous. If the delegate is a malicious program, your funds can be moved freely. The EIP-7702 specification itself warns that a poorly built delegate can let an attacker take near complete control of the wallet[3]. In the October 2026 exchange drain, an exchange wallet was delegated to the attacker's program, and its assets were swept out three minutes later (our write-up, incident page).

Three things help you tell them apart:

  • Is the delegate a well-known implementation? Compare its address with lists published by your wallet app or its developer. The address in our case is on Alchemy's list[2]. An unnamed program with no published source is a warning sign.
  • Have any funds moved? Look for transfers you do not recognise. Transfers made through a delegated program may not appear in the normal transaction list. Also check the "Internal Transactions" tab and the token transfer tab.
  • Which apps hold your key? Check whether the wallet apps that hold this key have fee-free swaps or similar features. If their help pages name a delegate, compare it.

If you still cannot explain it, consider creating a new wallet and moving your funds. Removing the delegation does not help if your key has leaked: it can simply be set again. If the key has leaked, the only protection is a new key.

7. For services that accept payments

As wallet apps use delegation for more features, we expect more payers to arrive with a delegated wallet. Many will not know it. An "invalid signature" error alone tells them nothing.

ChainAnalyzer made two changes to its x402 API:

  • We added a note to the payment instructions (the 402 response) and the documentation: on an address with a delegation, or a smart contract wallet, the USDC signature check on Base may fail.
  • When a payment is rejected for its signature and the payer's address has a delegation, the response now says so (payer_has_eip7702_delegation). The payer then knows to remove the delegation or pay from another address.

If your service accepts signed payments, we suggest returning the reason for a rejection as specifically as you can.

8. Summary

  • A convenient wallet app feature can put an EIP-7702 delegation on your wallet. Nothing looks different, and it stays until you remove it.
  • With a delegation, USDC sends the signature check to the wallet's program. Payments made by signature alone can then fail.
  • Anyone can check for a delegation on a block explorer. If you do not need it, remove it in the app's settings.
  • A delegation you do not recognise may mean a tricked signature or a leaked key. If unsure, move to a new wallet.

Sources

  1. Phantom, "Understanding gasless EVM transactions" (official help). https://help.phantom.com/articles/understanding-gasless-evm-transactions-53467684967443
  2. Alchemy, "Deployed addresses" (Modular Account V2, SemiModularAccount7702 v1.0.0). https://www.alchemy.com/docs/wallets/smart-contracts/deployed-addresses
  3. EIP-7702: Set Code for EOAs (delegation indicator, clearing with the zero address, authorization cost, chain-independent authorizations, EXTCODESIZE, security notes). https://eips.ethereum.org/EIPS/eip-7702
  4. ethereum.org, "Pectra" (activated on mainnet on 7 May 2025; includes EIP-7702). https://ethereum.org/roadmap/pectra/
  5. USDC public source, SignatureChecker.sol (isValidSignatureNow, isContract). https://github.com/circlefin/stablecoin-evm/blob/fc85788bc7c23cefe3df1a757133048bfddadeaa/contracts/util/SignatureChecker.sol#L38-L86
  6. USDC public source, EIP3009.sol (_transferWithAuthorization, _requireValidSignature). https://github.com/circlefin/stablecoin-evm/blob/fc85788bc7c23cefe3df1a757133048bfddadeaa/contracts/v2/EIP3009.sol#L117-L140 / https://github.com/circlefin/stablecoin-evm/blob/fc85788bc7c23cefe3df1a757133048bfddadeaa/contracts/v2/EIP3009.sol#L276-L292
  7. ERC-1271: Standard Signature Validation Method for Contracts. https://eips.ethereum.org/EIPS/eip-1271
  8. x402, "Scheme: exact on EVM" (uses EIP-3009 transferWithAuthorization). https://github.com/coinbase/x402/blob/main/specs/schemes/exact/scheme_exact_evm.md
  9. Basescan, the USDC implementation contract on Base (FiatTokenV2_2, verified). https://basescan.org/address/0x2Ce6311ddAE708829bc0784C967b7d77D19FD779#code

Share this page

© 2026 ChainAnalyzer. All rights reserved.