
When Accounts Become "Programmable": Restraints and Trade-offs from EIP-7702 and ERC-4337 to Native AA
Author: imToken

If the core responsibility of crypto wallets over the past decade has been managing private keys, signing transactions, and displaying assets, then moving forward, wallets may need to take on even more responsibilities.
Users want to no longer pay Gas separately for each transaction, desire multi-step operations completed with a single signature, prefer paying fees with stablecoins, and even hope to break free from absolute dependence on a single private key through social recovery, session keys, and flexible permission management.
Behind these needs lies a single technological direction: Account Abstraction (AA).
With the development of solutions like EIP-7702 and ERC-4337, Ethereum accounts are gradually transitioning from a relatively fixed transaction execution model to a more flexible, programmable account system.
But problems come with it.
When an account can not only receive assets and sign transactions, but also execute complex smart contract logic, manage authorizations of different levels, and even have third parties pay Gas on its behalf, are users actually gaining more control, or introducing more security risks they cannot fully understand?
From EOA to AA: Why Do Ethereum Accounts Need to Become “Programmable”?
Understanding account abstraction requires first returning to Ethereum’s most fundamental account model.
For a long time, ordinary users have primarily used EOAs (Externally Owned Accounts), which are controlled by private keys. Users sign transactions via their private keys, resulting in simple overall account structures, clear permission relationships, and relatively straightforward transaction execution paths.

Yet this design also presents some limitations in user experience.
For example, if a user wants to complete a token swap on Uniswap, they typically must first approve the ERC-20 Token before submitting the swap transaction. This means two independent on-chain operations, two signatures, and two Gas payments.
Furthermore, traditional EOAs cannot directly handle tasks like using USDT to pay Gas or having an application cover transaction fees on the user's behalf through the account's own verification logic.
More importantly, possessing the private key essentially grants full control over the account, making it difficult for users to set daily spending limits, restrict app permissions, or configure different signature rules for varying usage scenarios directly at the account level.
What AA attempts to change are precisely these restrictions.
Its core idea is to make the account’s verification, execution, and fee payment logic programmable, freeing users from relying solely on a fixed private key signature rule. Instead, they can define how accounts verify identity, execute operations, and pay fees according to their needs (For further reading: $3.35 Billion “Account Tax”: When EOA Becomes a Systemic Cost, What Can AA Bring to Web3?)
Ultimately, the greatest value of account abstraction lies in enabling wallets to perform operations that were previously difficult to achieve, but from a security perspective, this is exactly where the problems arise.
After all, users previously only needed to focus on whether they were signing a correct transaction and whether their signature was being maliciously exploited; in a smart account system, what appears to be a routine authorization may involve account execution code, permission modules, third-party payment services, and collaboration among multiple distinct roles.
What the user sees might simply be one confirmation, while what actually occurs could be a change in the entire account control logic.
From a dialectical perspective, traditional EOA accounts do indeed feel cumbersome in terms of user experience, but for a long time, they have provided the entire crypto world with a highly underrated security dividend: the relative certainty of account control relationships and verification rules.
While users hold private keys and directly sign to authorize transactions—and risks such as private key leakage, malicious approvals, and phishing persist—the accounts themselves do not need to load complex smart contract logic to adjudicate the verification and execution of each transaction.
AA breaks down this singular structure.
The Other Side of AA Convenience: When Accounts Lose “Certainty”
Once accounts possess stronger programmability and batch execution capabilities, objects mistakenly signed by users may no longer just be token approvals, but could involve account delegation, execution modules, and broader operational permissions. Once these permissions lack clear boundaries, risks can quickly spread from individual transactions to the entire account.
This is why, under the AA roadmap, while both EIP-7702 and ERC-4337 aim to improve account experiences, the risk exposures exposed at the wallet security level are drastically different. It should be noted that these two are not entirely mutually exclusive schemes; the latter already incorporates compatibility support for the former. They are discussed separately here mainly to understand their typical account implementations and the distinct challenges they face from a product security perspective.

EIP-7702: A Single Authorization Could Change the Behavioral Boundaries of an Entire Account
The security proposition most warranting vigilance in EIP-7702 lies in account delegation (Delegation).
By signing an authorization message, an originally rule-bound EOA can delegate itself to a deployed smart contract address and execute directly according to that contract’s code.
Contracts that are thoroughly audited and possess strict permissions can indeed grant existing accounts capabilities like batch transactions and Gas sponsorship at a low cost; however, if delegated by mistake to a malicious or severely vulnerable contract, the risk will directly penetrate into the account's assets.
This differs significantly from conventional DApp interactions. Misapproving a malicious authorization in a DeFi application typically confines the risk initially within the scope defined by specific tokens, approval limits, and target contracts; however, if users grant unlimited allowances, the losses can still be severe.
In contrast, under EIP-7702’s delegation scenario, the authorized code runs directly in the account context. If the delegated code possesses unrestricted asset transfer or contract call capabilities, the risk could expand from specific token approvals to the entire account, affecting ETH, various ERC-20 assets, and subsequent transaction operations.
However, EIP-7702 does not strip the original private key of its control over the EOA. Even if a user delegates an account to a contract with multi-signature logic, the original private key can still directly control the account, bypassing certain signature policies set by the delegated contract.
In other words, stacking smart contract execution capabilities onto an EOA is not equivalent to automatically tightening the underlying private key’s permission constraints. Similarly, although users can revoke delegation by re-authorizing an empty address, the revocation action cannot roll back already executed asset transfers and on-chain state changes.
This dictates that wallets must never treat EIP-7702 simply as a new form of signature. They must reconstruct a comprehensive security defense system centered around approval interfaces, contract identification, permission display, delegation revocation, and risk control prompts.

ERC-4337: Risks Extend Beyond the Account Contract
Unlike transforming existing EOAs, ERC-4337 separates account verification, transaction execution, and Gas payment into independent modules. This grants developers flexible combination space but also burdens wallets with more complex component management costs.
A UserOperation typically traverses an entire collaborative chain from creation to on-chain inclusion: the wallet generates the operation and completes the signature → the Bundler receives the UserOperation and performs off-chain checks via the EntryPoint’s simulation verification logic → the Bundler packs the verified operation and submits it to the on-chain EntryPoint → the EntryPoint executes the account and payer’s verification logic again, and upon passing, performs the actual operation.
If fee sponsorship is involved, a Paymaster must participate in verification and fee settlement; if creating a new smart account is required, it may involve the deployment and initialization of a Factory contract.
As the number of components surges, wallets must simultaneously tackle more complex challenges in compatibility, runtime reliability, and security audits. Additionally, since smart accounts are not merely adding a feature toggle to existing EOAs, their contract implementation, signature verification methods, module configurations, EntryPoint versions, and supporting infrastructure will profoundly impact future evolution paths.
As Ethereum gradually moves toward Native AA, questions regarding how existing accounts will compatible with new protocols, how original permissions will migrate, and how account addresses and assets will maintain continuity must be factored in advance.
Ultimately, for wallets, the true cost of integrating a technology today is never just development and launch, but rather the continuous maintenance and fallback commitments for the next several years.

From Application-Layer AA to Native AA: Restraint and Trade-offs in Technological Roadmaps
Once the security complexity and maintenance costs behind these two roadmaps are understood, how should wallet products choose? The answer has actually become increasingly clear: adopting a technology shouldn’t just depend on how many features it enables, but must weigh technological maturity, user cognitive thresholds, and the long-term sustainability of the architecture.
Taking imToken’s practice in account abstraction as an example, the team made clear trade-offs after evaluating multiple roadmaps: maintaining a cautious stance on EIP-7702, halting new productization investments in ERC-4337, and gradually shifting research focus toward Ethereum’s native account abstraction (Native AA).
First, regarding EIP-7702: its technical capabilities are commendable, but there is no rush for full productization.
To be objective, EIP-7702, now live on the Ethereum mainnet, empowers traditional accounts with capabilities like batch transactions and Gas sponsorship, and its engineering design and UX improvements are undeniable.
However, before truly opening up to large-scale ordinary users, several core prerequisites remain immature: Can users intuitively understand the difference between “account delegation” and conventional signing? Has the industry formed a reliable consensus on security audits for delegated contracts, permission display standards, and emergency recovery?
These issues are especially critical in the EIP-7702 scenario. If an average user cannot clearly grasp what their approved authorization entails, then even if the technology itself can implement complex security strategies, it may not genuinely elevate user security levels.
Therefore, imToken chooses a cautious wait-and-see approach for EIP-7702, temporarily refraining from fully integrating it into its product ecosystem. This gradual waiting allows related implementations, permission management mechanisms, and industry practices to undergo longer-term validation, aiming to establish a more reliable security boundary between technical capability and users’ actual comprehension.
By comparison, ERC-4337 has already proven the feasibility of smart accounts through extensive production practices, accumulating invaluable experience for the industry.
But viewed from a longer technological cycle, as Ethereum’s development direction increasingly points toward protocol-level native support, continuing to expand productization investments around application-layer account abstraction architectures requires reevaluating the ongoing maintenance costs of peripheral infrastructure, as well as potential compatibility and migration costs when connecting with native protocol capabilities in the future.
Consequently, imToken’s decision to halt new ERC-4337 productization investments and gradually shift its research focus to Native AA does not negate ERC-4337’s technical value. On the contrary, it aims to avoid continuously piling complexity onto existing architectures, channeling limited engineering and security research resources more heavily into native account abstraction directions with long-term development potential.
This choice also echoes Ethereum’s own protocol evolution trajectory.
In February 2026, when updating its protocol development priorities, the Ethereum Foundation explicitly listed Native AA as one of the core initiatives under the “Improve UX” track. Its long-term goal is to make smart contract wallets the default account format while reducing reliance on peripheral infrastructure like Bundlers and Relayers, thereby eliminating the associated extra Gas overhead.
In terms of specific technical proposals, EIP-8141 (Frame Transactions) is currently a representative direction worth monitoring. It attempts to split transaction verification, fee payment authorization, and actual operation execution into different phases, allowing accounts to define verification rules and payment methods through their own logic, offering a new implementation path for native protocol-level support of smart accounts.
Of course, EIP-8141 remains in the Draft stage at present, and there is still a considerable distance before formal deployment and large-scale application. Native AA also does not mean security risks will automatically vanish; account verification code still requires rigorous auditing, and new transaction verification and fee payment mechanisms must undergo thorough testing.
But looking at it from a long-term architectural perspective, compared to constantly adding functions to existing middleware and maintaining complex compatibility relationships, proactively laying out security architecture on a more native and unified protocol base obviously aligns better with imToken’s considerations for the long-term security of its wallets.
Final Thoughts
From initial private key signing to today’s batch transactions, Gas sponsorship, session keys, and smart accounts, account abstraction is continuously expanding the capability boundaries of crypto wallets.
But no matter how the technological forms evolve, the most essential value of wallets has never changed: not only must they enable users to accomplish more operations, but they must also ensure that during every interaction, users always clearly know what they have authorized and who exactly controls their assets.
Returning to concrete product practices, this is also the underlying logic behind imToken’s recent clear trade-offs in its account abstraction technological roadmap: maintaining a cautious wait-and-see stance on EIP-7702 while awaiting a more stable, long-term protocol and security paradigm; simultaneously halting new productization investments in ERC-4337 and gradually shifting its research focus toward Native AA.
This is by no means abandoning account abstraction innovation. Quite the opposite, it is a pragmatic choice based on user asset security, technological maturity, and long-term architectural evolution—refusing to prematurely convert transitional-phase protocol complexities into asset risks and migration costs for ordinary users.
Ethereum’s account evolution is a marathon. In the journey toward native account abstraction, carefully assessing technological maturity and security risks may be far more important than pursuing rapid feature deployment.















