ETH Daily
Menu

Why imToken Is Holding Back on EIP-7702 and Shifting Research Toward Native Account Abstraction

As reported on November 21, 2026, imToken’s approach to Ethereum account abstraction was to hold off on broad EIP-7702 product adoption, stop new product investment in ERC-4337, and gradually shift its research focus toward native account abstraction. The distinction matters: EIP-7702 had reached Ethereum mainnet, ERC-4337 was an application-layer approach with production use, and native account abstraction remained a longer-term protocol direction.

Why imToken Is Holding Back on EIP-7702 and Shifting Research Toward Native Account Abstraction (1)

The security question behind programmable accounts

Traditional externally owned accounts (EOAs) rely on a private key to authorize transactions. Account abstraction aims to make validation, execution and fee payment more programmable. That could support operations such as batching transactions or having another party pay gas, but it also makes the scope of an authorization harder for a user to assess.

Why imToken Is Holding Back on EIP-7702 and Shifting Research Toward Native Account Abstraction (2)

With EIP-7702, an EOA can authorize delegation to code at a deployed contract address. That can add capabilities to an existing account, but delegation to malicious or seriously flawed code could put assets across the account at risk. The original private key also retains control: adding delegated multisignature logic does not, by itself, constrain what that key can do. A user can revoke delegation by authorizing an empty address, but revocation cannot undo transfers or other on-chain changes that have already occurred.

Why imToken Is Holding Back on EIP-7702 and Shifting Research Toward Native Account Abstraction (3)
Why imToken Is Holding Back on EIP-7702 and Shifting Research Toward Native Account Abstraction (4)

ERC-4337 takes a different route through smart accounts and supporting infrastructure. A wallet creates and signs a UserOperation; a bundler checks it through EntryPoint simulation, then submits it for on-chain validation and execution. A paymaster may handle sponsored fees, while a factory may deploy a new account. These components offer flexibility but also create compatibility, security-review and maintenance demands. The two approaches are not mutually exclusive: the report notes that ERC-4337 has incorporated support for EIP-7702.

Why imToken Is Holding Back on EIP-7702 and Shifting Research Toward Native Account Abstraction (5)

A product decision, not a deployed native upgrade

The report says imToken is waiting for more mature delegation safeguards, permission displays and industry practices before broadly introducing EIP-7702. It also says the wallet has stopped new ERC-4337 product investment—not that ERC-4337 lacks value—and is directing more research toward native account abstraction. Its stated concern is the long-term cost of maintaining application-layer infrastructure and potentially migrating or adapting accounts as Ethereum’s protocol evolves.

Why imToken Is Holding Back on EIP-7702 and Shifting Research Toward Native Account Abstraction (6)

In February 2026, the Ethereum Foundation identified native account abstraction as part of its “Improve UX” protocol priorities, according to the report. EIP-8141, or Frame Transactions, was still a Draft at the time of publication. It proposes separating transaction validation, fee-payment authorization and execution into stages; the report does not describe it as deployed. Native support would not remove the need to audit account code or test new validation and payment mechanisms.