.png)
On May 7, 2025, EIP-7702 officially went live on the Ethereum Mainnet, and its impact was immediately felt across the ecosystem. Within a week, The Block reported more than 11,000 authorizations using the protocol, and BeInCrypto showed a move from just a few transactions to 1000 daily within a month of the release.
Today, analysis from Dune Analytics reveals that there have been over 60 million authorizations and more than 17 million transactions using the protocol. Dune tracks 11 of the largest chains implementing EIP-7702, though many more mainnets and testnets are now supporting it.
This article details why EIP-7702 is such an important improvement to Ethereum. It offers insight into how EIP transactions work, and it provides a comprehensive list of EIP-7702-enabled chains to explore.
What is EIP-7702 and why does it matter for web3 developers
EIP-7702 is an Ethereum Improvement Proposal that introduces a new transaction type enabling Externally Owned Accounts (EOAs) to temporarily execute smart contract logic. This proposal redefines how wallets behave, merging the simplicity of EOAs with the flexibility of smart contract accounts.
Historically, EOAs were simple key-pair wallets capable only of signing and sending transactions. Smart Contract Wallets, on the other hand, used programmable code to enable features such as batch transactions, gas sponsorship, and multi-signature authorization. These two account types were separate, creating friction for developers and users alike.
EIP-7702 bridges this divide. It allows an EOA to attach a set code transaction, effectively turning the account into a Smart EOA for the duration of that operation. This smart layer can authorize other contracts, perform delegation, or even sponsor gas for users. After the transaction completes, the account reverts to a standard EOA state.
For Web3 developers, this is a foundational shift. It makes Account Abstraction (AA) native to the protocol, reducing reliance on higher-level frameworks like EIP-4337. It simplifies the creation of smart wallets, gasless transactions, and multi-step executions without needing external relayers or bundlers.
Vitalik Buterin and the Ethereum core team designed EIP-7702 to unify account types under one flexible standard. By giving EOAs programmable behavior, developers can now design smarter onchain experiences with fewer moving parts and stronger security guarantees.
In practice, this means developers can build wallets that seamlessly handle authorization lists, delegation mechanisms, and custom policy logic directly at the protocol layer.
How EIP-7702 transactions work and the unification of wallet design
At the heart of EIP-7702 lies a simple but powerful idea: an EOA can temporarily act like a smart contract. Instead of being limited to signing transactions, an EOA can deploy logic for the duration of a call, execute it, and then return to its normal state. This is made possible through a set code transaction, which lets a wallet define and attach a piece of smart contract code that executes as part of the operation.
When a user initiates a 7702 transaction, the wallet sends an authorization list along with a delegation designator. These define which contracts or accounts are allowed to act on behalf of the user during that transaction. The network validates this information, confirms the logic is tied to the sender’s verified address, and then executes the operation within a verifiable context.
This transforms what was once a static signature into programmable, verifiable logic. A wallet’s authorization can now contain onchain conditions such as:
- Multisig checks to ensure multiple parties approve a transaction
- Access control rules that restrict execution to approved contracts
- Gas payment policies that allow delegated or sponsored fees
In effect, the transaction itself becomes a mini smart contract, capable of handling complex flows that previously required deploying a dedicated contract. For developers, this introduces an entirely new level of flexibility.
The benefits of EIP-7702 for wallets
EIP-7702 makes it possible to perform batch transactions that combine multiple actions into a single call, create gasless operations sponsored by a trusted delegate, and initiate dynamic contract deployments directly from EOAs. Each of these capabilities dramatically simplifies onchain development by bringing programmability and composability to the wallet layer itself.
This simplifies onchain interactions by embedding authorization logic into the transaction itself rather than relying on external middleware or paymaster services. It also helps eliminate the fragmentation that previously existed between smart contract wallets and traditional EOAs.
The result is the rise of Smart EOAs, hybrid accounts that combine the simplicity of user-controlled keys with the extensibility of smart contracts. These Smart EOAs allow developers to design wallets that offer both user friendliness and programmable depth, without requiring separate account infrastructures or bridges.
In this model, every EOA becomes a programmable shell. It can execute smart contract code when needed, apply delegated permissions through authorization lists, and revert to a lightweight key-pair account afterward. This unification streamlines wallet design, reduces deployment costs, and aligns the Ethereum ecosystem toward a future of natively abstracted accounts.
For builders working with Account Abstraction frameworks, this change means:
- Fewer custom relayers and external gas mechanisms
- Simpler interoperability across EVM networks
- A consistent developer experience for smart wallet construction
Instead of designing around limitations, developers can now treat every wallet as a flexible, secure, and programmable endpoint, one that speaks the same language as the EVM itself.
Chain adoption: 38 EVM networks supporting EIP-7702
Tracking down which chains actually support EIP-7702 can be a difficult process. There are a few sites that give this information, but as new chains come into the fold and roll out their implementations, it’s difficult to get a good idea of how many networks support the protocol (for example, Moonbeam Network just upgraded at the end of September).
You can search the internet or use an LLM, but that likely won’t produce the most reliable of lists. Searching through docs and marketing material for any particular chain is also an option but can be a long process.
EIP-7702 support as of October 2025
Below is a list of mainnets and testnets, and their chain IDs, that currently support EIP-7702l:
✅ Confirmed mainnets
🧪 Confirmed testnets
Developer considerations and migration path
For Web3 developers, EIP-7702 marks a major evolution in how wallets, accounts, and smart contract logic interact. Migrating to 7702-compatible accounts introduces new opportunities but also new design considerations.
Compatibility and migration
Because 7702 transactions are executed at the protocol layer, developers can continue using existing RPC endpoints, relayers, and bundlers with minimal adjustments.
In practice, this means developers can gradually transition to 7702 accounts without breaking compatibility for existing users. EOAs can remain unchanged until developers decide to enable smart behavior dynamically.
Authorization lists and delegation indicators
EIP-7702 also introduces two new transaction components: authorization lists and delegation indicators.
The authorization list defines which accounts or contracts are allowed to act on a user’s behalf during a transaction. The delegation indicator shows when an EOA has temporarily attached code, allowing it to function like a smart account for that operation. Together, they enable secure delegation and precise permission control at the protocol level.
From a security perspective, this requires careful handling. Developers should:
- Validate that only approved contracts or signers appear in authorization lists.
- Audit delegation logic to ensure permissions do not persist beyond the intended transaction.
- Use verification tools and explorers to confirm that on-chain authorizations match expected parameters.
By using authorization lists and delegation as programmable access controls, developers can design wallets with fine-grained permissions while maintaining user ownership and control.
How to get the most out of EIP-7702 with Turnkey
Turnkey provides developers with ready-to-use, enclave-backed wallet infrastructure that already supports the core primitives EIP-7702 enables: delegated operations, sponsored transactions, programmable authorization lists, and multi-step transaction execution. These capabilities form the building blocks for teams that want to experiment with Account Abstraction today, without building new infrastructure from scratch.
Turnkey policies: From gas sponsorship to full delegation
EIP-7702 allows wallets to temporarily assign permissions or delegate payment responsibilities to another contract. Turnkey extends that capability with policy-based controls that define who can act, what can execute, and how gas is sponsored or reimbursed. This creates the foundation for:
- Native gas sponsorship — transactions where a delegate or service covers gas fees for the user.
- Delegated execution — operations performed on a user’s behalf under programmable rules.
- Sponsored smart contract deployment — initializing and funding contracts without direct ETH ownership.
Turnkey abstracts away the infrastructure complexity behind these models, letting developers build user-friendly wallet experiences that “just work” across chains, all while maintaining cryptographic guarantees of security and control.
Because EIP-7702 supports multi-call logic, developers can bundle multiple operations, like swap, approve, and stake, into one atomic transaction. Paired with Turnkey’s verifiable signing and policy engine, these meta-transactions reduce friction for onboarding and keep sensitive logic inside audited, attested environments. The result is a simplified developer workflow and a seamless user experience.
Turnkey: EIP-7702 and programmable policy
EIP-7702 represents one of the most meaningful steps toward unifying how wallets, accounts, and smart contracts operate on Ethereum. EIP-7702 transforms every wallet into a potential smart account, one capable of delegation, gas sponsorship, and complex onchain coordination without ever leaving the protocol layer.
The networks listed in this article highlight just how rapidly this standard is spreading across the EVM ecosystem. From major L2s like Optimism and Base to experimental testnets like Ink and Soneium Minato, developers are embracing 7702 as the foundation for native Account Abstraction.
As developers build on this standard and infrastructure projects like Turnkey extend it through programmable policies, the Ethereum ecosystem moves closer to a future of universal, user-centric smart accounts where abstraction, security, and usability finally converge.
