Ethereum and Coinbase’s Layer-2 network Base are officially set to implement different account abstraction standards, marking a significant fork in the road for the broader Ethereum ecosystem. The divergence comes after weeks of intensive discussions and ultimate failures to arrive at a shared, unified account abstraction standard broke down last week.
According to industry researchers, interoperability standards ultimately took a backseat to each chain’s core architectural and philosophical goals. This friction has pushed both networks to go their separate ways, effectively shifting a substantial operational burden onto the developer community. Derek Chiang, a founding member and researcher at Ethlabs and a co-author of Ethereum’s EIP-8141 proposal, highlighted this challenge in a post on X on Monday. Chiang noted that the current trajectory is "putting the burden on wallets" as developers grapple with diverging protocols.
This technical divergence means that wallet developers may soon be forced to support separate transaction formats, custom logic, and independent codebases just to provide a seamless, consistent user experience across the Ethereum mainnet and its most prominent scaling networks. Account abstraction—often abbreviated as AA—is a major technological evolution in the blockchain space. It allows users to introduce programmable rules for authorizing transactions, setting up social recovery mechanisms, automating recurring payments, and managing flexible fee-paying structures without relying on traditional, rigid externally owned accounts.
Following the breakdown of harmonization efforts, Ethereum is now advancing Frame Transactions under EIP-8141 as a headliner item under its upcoming Hegotá upgrade. This inclusion aims to introduce native account abstraction to the Layer-1 network while simultaneously forging a clear, robust path toward post-quantum authentication and long-term cryptographic security.
On the other side of the ecosystem, Base is taking a different path by developing its own native account abstraction framework via Keystore under EIP-8130, a specification that is currently live on devnet for testing and developer integration.
This bifurcation underscores deeper, structural differences in priorities between foundational Layer-1 blockchain networks and execution-focused Layer-2 scalability networks. Chiang explained that Layer-1 networks are increasingly focusing their development roadmaps on censorship resistance, core security, capture-resistance, open-source integrity, and advanced privacy features. These foundational requirements naturally favor different account standards tailored to the security-maximalist ethos of a base settlement layer. Conversely, Layer-2 networks like Base are primarily optimized for high scalability, developer adoption, and immediate user-facing fluidity, making them naturally more aligned with streamlined standards such as EIP-8130.
Despite the immediate friction and potential fragmentation for wallet infrastructure providers, Chiang argued that this separation will not necessarily lead to a negative outcome for the ecosystem at large. Instead, both Ethereum and Base are now completely free to innovate on account abstraction to the maximal extent possible, tailoring their approaches precisely in accordance with their distinct architectural visions and community needs.
Looking ahead, the timeline for these upgrades reveals a busy period for core developers. Ethereum developers could begin implementing the Hegotá upgrade in late 2026, following the rollout of Glamsterdam, which is widely regarded by developers and analysts as one of the most consequential protocol upgrades of the year. Glamsterdam is explicitly designed to improve overall network scalability, harden the Layer-1 infrastructure, and make the network significantly easier to use for both everyday users and application developers. According to Ethereum’s public roadmap, a mainnet launch for Glamsterdam is expected sometime in the second half of 2026, setting the stage for the subsequent integration of EIP-8141 and native account abstraction features across the primary network.

