When Accounts Become 'Programmable': The Trade-offs from EIP-7702, ERC-4337 to Native AA
AA is endowing Ethereum accounts with unprecedented programmability while quietly breaking the security certainty of traditional EOAs.
If the core responsibilities of crypto wallets over the past decade have been to manage private keys, sign transactions, and display assets, then wallets may need to take on more tasks moving forward.
Users hope to no longer pay Gas for each transaction separately, to complete multiple operations with a single signature, to use stablecoins to pay fees, and even to escape absolute reliance on a single private key through social recovery, session keys, and flexible permission management.
These demands point to the same technological direction: Account Abstraction (AA).
With the development of proposals like EIP-7702 and ERC-4337, Ethereum accounts are gradually transitioning from a relatively fixed transaction execution model to a more flexible and programmable account system.
But problems arise as well.
When an account can not only receive assets and sign transactions but also execute complex smart contract logic, manage different levels of authorization, and even allow third parties to pay Gas, are users gaining more control or introducing more security risks that they cannot comprehend?
1. From EOA to AA: Why Do Ethereum Accounts Need to Become 'Programmable'?
To understand account abstraction, we first need to return to the most basic account model of Ethereum.
For a long time, the main type of account used by ordinary users has been EOA (Externally Owned Account), which is controlled by private keys. Users sign transactions with their private keys, making the overall account structure simple, with clear permission relationships and relatively easy-to-understand transaction execution paths.
However, this design also has some experiential limitations.
For example, when a user wants to complete a token swap on Uniswap, they often need to authorize the ERC-20 Token first and then submit the swap transaction, which means two independent on-chain operations, two signatures, and two Gas payments.
If a user wants to pay Gas with USDT or let the application bear the transaction fees, traditional EOAs cannot directly accomplish these tasks through the account's own verification logic.
More importantly, mastering the private key essentially means having full control over the account, making it difficult for users to set daily spending limits, restrict application permissions, or configure different signing rules for different usage scenarios at the account level.
AA aims to change these limitations.
Its core idea is to make the verification, execution, and fee payment logic of accounts programmable, allowing users to define how accounts verify identity, execute operations, and pay fees according to their needs (see further reading "The $3.35 Billion 'Account Tax': What Can AA Bring to Web3 When EOA Becomes a Systemic Cost?").
Ultimately, the greatest value of account abstraction is to enable wallets to perform operations that were previously difficult to achieve, but from a security perspective, the problems also arise here.
After all, in the past, users only needed to focus on whether they were signing a correct transaction and whether the signature was being maliciously exploited; in a smart account system, a seemingly ordinary authorization may involve account execution code, permission modules, third-party payment services, and collaboration among multiple different roles.
What users see may only be a confirmation, but what actually happens may be a change in the entire account control logic.
From this dialectical perspective, traditional EOA accounts do seem cumbersome in experience, but they have long provided an often-underestimated security dividend for the entire crypto world—the relative certainty of account control relationships and verification rules.
Users hold private keys and directly sign authorized transactions; although risks of private key leakage, malicious authorization, and phishing always exist, accounts themselves do not need to load complex smart contract logic to adjudicate the verification and execution of each transaction.
AA breaks this singular structure.
2. The Other Side of AA Convenience: When Accounts Lose 'Certainty'
When accounts possess stronger programmability and batch execution capabilities, the objects that users mistakenly sign may no longer just be the authorization of a specific token but may also involve account delegation, execution modules, and broader operational permissions. Once these permissions lack clear boundaries, risks can quickly spread from a single transaction to the entire account.
This is why, under the AA route, although both EIP-7702 and ERC-4337 are improving account experiences, the risk exposures revealed at the wallet security level are completely different— it should be noted that the two are not entirely mutually exclusive solutions, and the latter has incorporated compatibility support for the former. Here, we will discuss the two separately mainly to understand their respective typical account implementation methods and the different challenges they face in product security.
1. EIP-7702: One Authorization May Change the Behavioral Boundaries of the Entire Account
The most concerning security proposition of EIP-7702 is account delegation.
By signing an authorization message, a previously rule-fixed EOA can delegate itself to a deployed smart contract address and run directly according to that contract's code.
Well-audited and tightly controlled contracts can indeed provide existing accounts with capabilities for batch transactions, Gas payment, etc., at a low cost; however, once mistakenly delegated to a malicious contract or a contract with serious vulnerabilities, the risk will directly penetrate to the account's assets.
This is distinctly different from conventional DApp interactions. In DeFi applications, mistakenly signing malicious authorizations usually first affects the specific Token, authorization limits, and the permission scope defined by the target contract; however, if a user grants unlimited access, the losses can also be severe.
And in the delegation scenario of EIP-7702, the authorized code runs directly in the account context. If the delegated code has unrestricted asset transfer or contract call capabilities, the risk can expand from specific token authorization to the entire account, affecting ETH, different ERC-20 assets, and subsequent transaction operations.
However, EIP-7702 does not deprive the original private key of its control over the EOA. Even if a user delegates the account to a contract with multi-signature logic, the original private key can still directly control the account, bypassing some of the signature strategies set by the delegated contract.
In other words, adding smart contract execution capabilities to EOA does not equate to automatically tightening the permission constraints of the underlying private key. Similarly, although users can revoke delegation by reauthorizing an empty address, the revocation action cannot roll back already occurred asset transfers and on-chain state changes.
This also determines that wallets must not simply view EIP-7702 as a new signing method; they must reconstruct a complete security defense system around authorization interfaces, contract recognition, permission display, delegation revocation, and risk control prompts.
2. ERC-4337: Risks Are Not Just in Account Contracts
Unlike transforming existing EOAs, ERC-4337 separates account verification, transaction execution, and Gas payment into independent modules, giving developers flexible combination space but also placing a heavier burden of component management on wallets.
A UserOperation typically goes through a complete collaborative chain from creation to being on-chain: the wallet generates the operation and completes the signature → Bundler receives the UserOperation and performs off-chain checks through the EntryPoint's simulation verification logic → Bundler packages the verified operation and submits it to the on-chain EntryPoint → EntryPoint executes the verification logic for the account and payer again and performs the actual operation after passing.
If fee payment is involved, a Paymaster also needs to participate in verification and fee settlement; if a new smart account needs to be created, it may involve deploying and initializing a Factory contract.
As the number of components increases, wallets must simultaneously deal with more complex compatibility, operational reliability, and security review challenges. Additionally, since smart accounts are not just adding a functional switch to existing EOAs, their contract implementations, signature verification methods, module configurations, EntryPoint versions, and supporting facilities will profoundly affect future evolutionary paths.
As Ethereum gradually moves towards Native AA, how existing accounts will be compatible with the new protocol, how original permissions will migrate, and how account addresses and assets will maintain continuity all need to be considered in advance.
Ultimately, for wallets, the real cost of adopting a technology today is not just development and launch but also the ongoing maintenance and risk management over the coming years.
3. From Application Layer AA to Native AA: The Restraints and Trade-offs of Technical Routes
After understanding the security complexity and maintenance costs behind the two routes, how should wallet products choose? The answer is gradually becoming clear: whether to adopt a technology cannot just be based on how many functions it can achieve, but must also weigh the technology's maturity, user cognitive thresholds, and the sustainability of long-term architecture.
Taking imToken's practice in account abstraction as an example, the team made clear trade-offs after evaluating multiple routes—to maintain a cautious outlook on EIP-7702 while halting new product investments in ERC-4337, gradually shifting research focus towards Ethereum's native account abstraction (Native AA).
First, regarding EIP-7702, its technical capabilities are commendable, but there is no rush for full productization.
Realistically speaking, EIP-7702, which has entered the Ethereum mainnet, can enable traditional accounts to gain batch transaction and Gas payment capabilities, and its engineering design and experience improvements are evident.
However, before it is truly opened up to a large number of ordinary users, several core prerequisites have not yet fully matured: Can users intuitively understand the difference between "account delegation" and conventional signing? Has the industry formed a reliable consensus on the security review, permission display standards, and anomaly rescue of delegated contracts?
These questions are particularly important in the context of EIP-7702. If an ordinary user cannot clearly understand what the authorization they signed means, then even if the technology itself can implement complex security strategies, it may not genuinely enhance the user's security level.
Therefore, imToken chooses to cautiously observe EIP-7702, temporarily refraining from fully integrating it into the product system, and slowly waiting for relevant implementations, permission management mechanisms, and industry practices to undergo longer-term testing. This is also to establish a more reliable security boundary between technological capabilities and users' actual understanding.
In contrast, ERC-4337 has already proven the feasibility of smart accounts through rich production practices, accumulating valuable experience for the industry.
However, from the perspective of a longer technical cycle, as Ethereum's development direction gradually points towards native protocol support, continuing to expand product investments around application layer account abstraction requires re-evaluating the ongoing maintenance costs of peripheral infrastructure and the potential compatibility and migration costs that may arise when connecting with native protocol capabilities in the future.
Thus, imToken's decision to halt new product investments in ERC-4337 and gradually shift research focus towards Native AA is not a denial of the technical value of ERC-4337; rather, it is a desire to avoid continuously adding complexity to the existing architecture, allocating limited engineering and security research resources more towards the direction of native account abstraction with long-term development potential.
This choice also resonates with Ethereum's own protocol evolution direction.
In February 2026, the Ethereum Foundation, in updating its protocol development priorities, explicitly listed Native AA as one of the core tasks in the "Improve UX" direction, with the long-term goal of making smart contract wallets the default account form while reducing reliance on peripheral infrastructures like Bundler and Relayer, as well as the additional Gas costs that arise from this.
In specific technical proposals, EIP-8141 (Frame Transactions) is currently one of the representative directions worth paying attention to, attempting to split transaction verification, fee payment authorization, and actual operation execution into different stages, allowing accounts to define verification rules and payment methods through their own logic, providing a new implementation path for native protocol support of smart accounts.
Of course, EIP-8141 is still in the Draft stage and is some time away from formal deployment and large-scale application. Native AA does not mean that security risks will automatically disappear; account verification code still needs to be strictly audited, and new transaction verification and fee payment mechanisms also need to undergo thorough testing.
But from a long-term architectural perspective, compared to continuously adding functions and maintaining complex compatibility relationships on existing intermediate layers, laying out security architecture in a more native and unified protocol foundation in advance clearly aligns more with imToken's considerations for long-term wallet security.
-- Price
Conclusion
From the initial private key signing to today's batch transactions, Gas payment, session keys, and smart accounts, account abstraction is continuously broadening the capability boundaries of crypto wallets.
However, regardless of how the technological form evolves, the essential value of wallets has never changed: not only to enable users to perform more operations but also to ensure that users are always clear about what they have authorized and who ultimately controls their assets in every interaction.
Returning to specific product practices, this is also the underlying logic behind imToken's recent clear trade-offs in the account abstraction technology route—maintaining a cautious outlook on EIP-7702, waiting for more stable protocols and security paradigms in the long term; while halting new product investments in ERC-4337 and gradually shifting research focus towards Native AA.
This is not a retreat from the innovation of account abstraction; on the contrary, it is a pragmatic choice based on user asset security, technological maturity, and long-term architectural evolution—not to prematurely translate the complexity of protocols in transition into asset risks and migration costs for ordinary users.
The evolution of Ethereum accounts is a long-distance race. In the process of moving towards native account abstraction, carefully assessing technological maturity and security risks may be more important than pursuing the rapid landing of functions.
This content is provided for general informational purposes only and doesn't constitute financial, investment, legal, or tax advice. Any events, rewards, online promotions, or related information mentioned herein should not be considered a recommendation, solicitation, or invitation to purchase, sell, trade, or otherwise deal in any crypto assets. Crypto assets are highly volatile and may result in loss. The availability of WEEX services, products, and related events may vary by region. You are responsible for ensuring that your participation is in accordance with applicable local laws and regulations.
You may also like

3 Data Center Power Stocks Down More Than a Third From Their Records to Buy Now and Hold Through 2030

The S&P 500 Just Entered Correction Territory. Here's What It Means for Investors Right Now.

DWF Labs: Bitcoin is Not Digital Gold, It Follows the Nasdaq

Is Coca-Cola a Millionaire-Maker Stock?

Can Solana become quantum-safe without losing its speed advantage?

Burnham Signs Agreement to Reboot UK-EU Relations

Most of crypto is dead, but 4 sectors will survive: Anthony Pompliano

Rejoining the EU Would Boost the UK Economy Twice as Much as a Swiss-Style Agreement

Is Wall Street Trapped? The $80,000 Cost Line of Bitcoin ETF

ChatGPT Wallet Partners with Visa: Does the Agent Economy Still Need Stablecoins?

Tom Lee: Market Decline Due to Panic, Abandoning is Like Selling at a Low Point

U.S. Congress Passes Bill Aimed at Protecting Elderly Investors from Financial Fraud

Is Nvidia Stock a Once-in-a-Decade Buying Opportunity After Its Latest Earnings?

Meet SHRINCS: Bitcoin's Emerging Frontrunner for a Post-Quantum Signature

Poland Expected to Sign Nuclear Power Plant Construction Agreement with US Consortium Early Next Year

Veteran CFO Bill Zerella Accelerates Stord's Expansion

Large-scale Attack Targets 178 Organizations Including Zoom and BBC with Malicious Code

Artificial Intelligence: A Threat to Crypto Market Security

From Madonna's Manager to Sound Ventures Partner, Guy Oseary Drives $7 Billion Investment in Anthropic

Cryptocurrency Tier One Investment: The Triangular Game of Humanity, Law, and Capital

Germany moves to freeze Bitcoin for up to 180 days, even without access to private keys

Stablecoin supply falls $16 billion as Bitcoin slides

Interest Rates Rebound to Three-Week High, Mortgage Demand Weakens

Target's Q3 Earnings Exceed Expectations, Raises Full-Year Guidance

Mining Giant MARA's Strategic Shift: Selling 40,000 BTC for Power Plants

Emerging Markets: Over $60 Billion Flees in Two Months Amid Growing AI Crisis Fears

Warnings Behind 50 Authorizations: How TBC Tightens Signature Permissions

a16z Frontier Explores AI Agent Sector, Uncovering a New Startup Opportunity

US Judge Acquits in $25 Million Fraud Case





