imToken Halts New ERC-4337 Productization Investment, Leans Into Native AA
imToken has halted new ERC-4337 productization investment and will not rush EIP-7702, shifting focus to Native account abstraction research on Ethereum.
AI SummaryAI
- imToken halted new ERC-4337 productization investment and slowed EIP-7702 rollout, announced November 21.
- imToken says ordinary users may find EIP-7702 delegation authority hard to understand.
- The EIP-7702 specification warns flawed delegation contracts could let attackers seize the signer's account.
- ERC-4337 routes smart account activity through UserOperation objects, bundlers, an EntryPoint contract and paymasters.
imToken Pulls Back From ERC-4337
imToken, the Ethereum wallet provider, has stopped new productization investment in ERC-4337 and decided not to rush a full productization of EIP-7702, redirecting its weight toward Native account abstraction research that would move account functions into the protocol itself. The company set out its position in an invited column published on Saturday, November 21.
Existing ERC-4337 support is not being withdrawn; what stops is fresh productization work on top of it. The company judged that ordinary users may find it difficult to understand the delegation authority EIP-7702 grants. The wider context is account abstraction, the technical direction that lets a wallet set its own flexible rules for verifying transactions and paying fees. Conventional externally owned accounts, or EOAs, sign every action with a private key, which makes it hard to bundle several operations together or have another party cover the gas fee from inside the account. EIP-7702 addresses that by letting an existing EOA take on delegated smart contract code, enabling batching and third-party fee payment without creating a new account. The trade-off sits in the signature itself: the scope a user signs over extends beyond an ordinary transfer to any code that runs from the account, and the EIP-7702 specification warns that a delegation contract implemented badly could let a malicious actor take effective control of the signer's account.
How ERC-4337 Differs From EIP-7702
ERC-4337 takes a different route to the same destination. It leaves the base transaction format untouched and carries smart account activity in a separate UserOperation object: a bundler collects multiple operations and submits them, an EntryPoint contract handles verification and execution on-chain, and a paymaster can step in when fee sponsorship is needed. That separation lets a wallet design account verification, execution and fee handling independently, but it also obliges the wallet to review the compatibility and security of every contract it connects to and of the processing infrastructure behind them. imToken named the burden of maintaining these application-layer components as the reason for halting new productization investment.
The two proposals are not mutually exclusive. The ERC-4337 specification already contains a route for handling EIP-7702 delegated accounts, so a wallet can evaluate the functions of both standards together, alongside the signing authority they grant and the infrastructure they depend on. That combined review is what imToken says it now prioritizes over shipping new builds on either track.
Native AA moves the same problem into the protocol. Instead of leaving verification and fee payment to auxiliary application infrastructure, it would place them inside Ethereum itself, and the representative proposal, EIP-8141, frames each transaction across verification, fee approval and execution stages. The Ethereum Foundation listed Native AA as a user-experience improvement task in its protocol priorities in February 2026, placed EIP-8141 as a non-core review item for the Hegota upgrade in April 2026 after developers failed to agree on an implementation approach, and classified it in September 2026 as an execution-layer core proposal for Hegota.
A Core Proposal Still in Draft
The operative fact for anyone following account abstraction is the gap between a core classification and shipped code. EIP-8141 remains in Draft status, no mainnet deployment date has been attached to it, and imToken has not said when, or in which product, its Native AA research will materialize. By stepping out of new ERC-4337 builds, the wallet exits the maintenance treadmill of bundlers, paymasters and per-application components while the protocol route is still unfinished. The practical state for its users is a holding pattern: delegated code under EIP-7702 and smart account flows under ERC-4337 keep running as they are, and the next material step for the standard now sits with the Hegota upgrade process rather than with any single wallet vendor.
AI-generated, AI-reviewed, under COINOTAG editorial oversight.

