Ethereum and Base, the L1 and its most prominent L2, have abandoned their attempt to build a joint account abstraction standard, and the developer who brokered the collaboration announced its death with unusual candor. Derek Chiang of Ethlabs wrote: "I'm sad to report that the AA collab between 8130 and 8141 (Frames) broke down last week, and Base and Ethereum are now going separate ways to implement different AA standards." The breakdown, during the week of September 7-14, ends the effort to reconcile EIP-8141, Ethereum's Frame Transactions standard designated a must-ship for the 2027 Hegotá upgrade on the August 27 ACD call, with EIP-8130, Base's account abstraction format built around an onchain Keystore recording approved actors and authenticators. Chiang's explanation is the anatomy of an irreconcilable difference: "While we identified a number of technical solutions, they all required one side or the other to compromise at least a little bit on their core goals. So separate ways we went, putting the burden on wallets to deal with the fragmentation that ensues."
Vitalik Buterin, an EIP-8141 co-author, had called the standard in February "an omnibus that wraps up and solves every remaining problem that AA was intended to address" — a promise now split into two incompatible half-solutions.
Why Account Abstraction Split
The substance of the split is a genuine values conflict, not a scheduling failure, and it maps precisely onto the L1-L2 relationship. EIP-8141's Frames structure transactions into programmable segments, validation, gas sponsorship, execution, turning every account into "an address with code," enabling gas sponsorship, non-ETH fee tokens, call batching, key rotation, and self-funded privacy pools, all in service of Ethereum's core priorities: censorship resistance, privacy, security, and post-quantum readiness. EIP-8130 optimizes for Base's world: throughput scale, custom execution, compliance-friendly structured authentication, predictable pre-execution validation, the requirements of an L2 whose users arrive from Coinbase's consumer funnel and whose commercial model needs throughput and enterprise integration. Neither priority list is wrong, which is exactly why the negotiation failed, the technical solutions existed, as Chiang said, but each one diluted something a side considered non-negotiable. The split also lands awkwardly for Coinbase, which operates Base while pushing wallet UX convergence through the ecosystem integrations we have tracked, from Robinhood Chain's unification economics to the identity work like Keys' passkey-based web3 identity: the company that wants to abstract wallets for a hundred million consumers now helps maintain a world where the two most important Ethereum-family chains read transactions differently.
Who Pays for the Fragmentation
The direct cost lands on wallet developers, who must now maintain dual native transaction parsers, two signing flows, two upgrade cadences, across what users experience as one Ethereum ecosystem, a tax that will be paid in consolidation, with smaller wallets dropping support for one chain or the other and the surviving ones passing costs into fees. The indirect cost is strategic: account abstraction is crypto's mainstream-ux project, the fix for seed phrases and the enabler of passkeys, social recovery, and sponsored fees, and a standards split at this stage means the L2 era's fragmentation problem now exists at the protocol's most user-facing layer. The steelman for the split deserves its space, because it is not nothing: shipping a compromised standard to both chains would have guaranteed a mediocre result everywhere, whereas two strong implementations preserve each side's ability to serve its actual users, and history suggests wallet middleware will eventually paper over the divergence the way EVM chains absorbed a dozen opcode quirks. The counterpoint: account abstraction was supposed to end the era of wallets compensating for protocol awkwardness, not extend it.
What to Watch
Watch Hegotá's 2027 scope, where EIP-8141's must-ship status means L1 consensus changes now carry the fragmentation question into Ethereum's upgrade calendar; watch whether a wallet intermediary, a Voyager-class standard or a shared SDK, emerges to bridge the two formats, because whoever ships it owns the UX layer; and watch Base's alternative distribution, if its EIP-8130 stack reaches millions of Coinbase users first, the market may render the standards debate moot with a fait accompli. Two Ethereums was always a thesis. Now it ships in two transaction formats.



































.jpg)









