Why do I get "EIP-7702 is not supported on entry point" when sending a user operation?

Last updated: August 14, 2026

If you're sending a user operation (for example, through wallet_prepareCalls) from an EIP-7702-delegated smart account such as ModularAccountV2, you may see this error even though your request and Gas Manager policy are configured correctly.

Symptom

The request fails with an InvalidParamsError similar to:

Caused by: RpcResponse.InvalidParamsError: Invalid parameters were provided to the RPC method.
Details: EIP-7702 is not supported on entry point 0x...

This can happen even when other operations on the same account, like minting, are sponsored successfully under the same Gas Manager policy.

Cause

This error is not tied to a specific token standard, contract method, or your policy configuration. It means the target network's EntryPoint does not yet support EIP-7702-style user operations. Because your smart account operation is built as an EIP-7702-style user operation, the bundler rejects it during validation, before Gas Manager sponsorship is ever attempted.

Two things need to be true for EIP-7702-style operations to succeed on a given network: the chain itself needs to support EIP-7702 at the protocol level, and Alchemy's bundler needs EIP-7702 support enabled for that network. If either piece is missing, any EIP-7702-style user operation sent to that network's EntryPoint is rejected, regardless of the contract method it calls. Other flows on the same account, like minting, can still succeed under the same policy if they don't require an EIP-7702-style operation on that EntryPoint.

Resolution

If you see this error, check whether the network you're using has EIP-7702 support enabled on Alchemy's bundler.

If you hit this error on a different network, contact Alchemy support to check whether EIP-7702 is enabled for that specific chain.