EIP-7702 FAQs
What is EIP-7702?
EIP-7702 is an Ethereum upgrade that allows EOAs to become smart accounts. It went live on Ethereum mainnet in the Pectra hard fork on May 7, 2025, and is live on many other EVM chains. See which chains Pimlico supports for EIP-7702.
How does EIP-7702 differ from ERC-4337?
In short, EIP-7702 allows for a way for EOAs to become smart accounts, while ERC-4337 creates a standard for smart accounts to plug into a standardized set of relayers and gas sponsorship modules (paymasters). Refer to the ERC-4337 vs EIP-7702 guide for more details.
Is EIP-7702 compatible with ERC-4337?
Yes, EIP-7702 is compatible with ERC-4337. They cover different responsibilities. ERC-4337 is a standard for smart accounts to plug into a standardized set of relayers and gas sponsorship modules (paymasters), while EIP-7702 allows EOAs to become smart accounts. Refer to the ERC-4337 vs EIP-7702 guide for more details.
Do I still need a bundler and paymaster if I use EIP-7702?
Not to use EIP-7702 itself, but yes to make it gasless. EIP-7702 gives an EOA smart account code; it doesn't change who pays for gas. A user who holds ETH can batch calls from their delegated EOA without any extra infrastructure. To sponsor their gas or let them pay in ERC-20 tokens, someone else has to send and pay for their transactions: either an ERC-4337 bundler and paymaster, such as Pimlico's, or a relayer and delegate contract you build yourself. See Do I still need a bundler and paymaster with EIP-7702? for each case.
Should an existing wallet with millions of EOAs use EIP-7702 or ERC-4337?
Usually both: upgrade existing EOAs in place with EIP-7702 so users keep their address and assets, delegate them to an ERC-4337-compatible implementation, and use ERC-4337 bundlers and paymasters for batching and sponsorship. Use new ERC-4337 smart accounts for chains without EIP-7702 and for users who need key rotation, multisig or social recovery, since a delegated EOA's original key always keeps full control. See Choosing between EIP-7702 and ERC-4337 for an existing wallet with millions of EOAs.
Does Pimlico support EIP-7702?
Yes, Pimlico supports EIP-7702 by allowing an eip7702Auth object to be included in eth_sendUserOperation and eth_estimateUserOperationGas requests, and supports EntryPoint 0.8. Pimlico's paymasters sponsor gas, or charge it in ERC-20 tokens, for delegated EOAs as for any smart account. You can read more about how to use it on the relevant reference pages for eth_sendUserOperation and eth_estimateUserOperationGas.
Which chains are supported by Pimlico for EIP-7702?
Each chain's EIP-7702 support status is listed in the Chain Details section of the Supported Chains page.
How does an EOA transition to smart account under EIP-7702?
The EOA signs an authorization naming the smart account implementation, the chain ID and its account nonce. Any account can then submit it in the authorization_list of a set code transaction (transaction type 4) and pay the gas, so the user doesn't need ETH. With ERC-4337 and EntryPoint 0.8, the bundler includes the authorization in the transaction that carries the user's first user operation.
How does EntryPoint v0.8 prevent frontrunning for EIP-7702 user operations?
The smart account factory is able to make the check require(msg.sender == entryPoint.senderCreator()); to ensure only the EntryPoint's senderCreator is calling it.
In addition, the userOpHash now also depends on the delegate address so users also sign over the 7702Auth object (source)
Is it possible to turn an EOA into a smart account under EIP-7702 for all chains?
Yes, as per the spec, by signing over a chain ID of 0, it is possible to make an authorization tuple that is valid for all chains and can be applied on all chains that support EIP-7702. With this, it is possible to for instance generate an ephemeral private key, sign over the 7702Auth object with it, discard the private key and then use the same 7702Auth object on all chains that support EIP-7702, even if the chain comes out many years later.