Collaboration Ceases Between Ethereum and Base
Developers from Ethereum and Base have officially ceased their collaboration on a shared account abstraction standard after their attempts to merge EIP-8141 and EIP-8130 were unsuccessful. Their partnership ended last week due to significant differences in core technical requirements, as stated by Ethlabs developer Derek Chiang on Monday. He expressed his disappointment, noting:
“I’m sad to report that the AA collaboration between 8130 and 8141 (Frames) broke down last week, and Base and Ethereum are now going separate ways to implement different AA standards.”
Goals of EIP-8141 and EIP-8130
Both Ethereum’s EIP-8141 and Base’s EIP-8130 proposals aimed to enhance user interactions with crypto wallets, allowing transactions without needing to hold ETH for gas fees and introducing new authentication methods like phone passkeys. The teams initially explored the possibility of developing a single design that would be applicable across Ethereum Layer 1 and Base Layer 2. However, Chiang explained that every potential technical solution required one party to make compromises that affected their essential goals.
“We identified a number of technical solutions, but they all required one side or the other to compromise on their core goals,”
he commented. As a result, the fragmentation that now looms will require a response from wallet developers as they adjust to supporting multiple native transaction formats if both proposals are implemented.
Future of User Experience
Chiang highlighted that despite the differences, wallets could still create a unified user experience, contingent on how well developers adapt to managing the two distinct standards. He suggested:
“If they execute well, and if the wallet community can bridge over the fragmentation, we may well end up with the best possible UX for the end users.”
Initial Optimism and Development Agenda
Originally, discussions between the teams showcased optimism for a shared future. Just days earlier, on Sept. 7, it was reported that EIP-8141 developers were considering how to ensure compatibility with EIP-8130 while also focusing on efficient, programmable transactions and simplifying the authentication requirements for infrastructure providers. Earlier this month, the Ethereum Foundation had positioned EIP-8141 within its vital development agenda, labeling it as essential for the upcoming Hegotá upgrade. This proposal aims to weave account abstraction natively into Ethereum while enhancing security and readiness for post-quantum challenges.
Distinct Approaches to Transactions
Frame Transactions, as outlined in EIP-8141, are structured to create a sequence of programmable frames within transactions. This approach allows different aspects of a transaction, such as authorization and execution, to be handled in a modular fashion. In contrast, EIP-8130 is designed around a new transaction type that features an on-chain keystore, allowing users to register approved actors and authentication contracts, which could support customized interactions.
Looking Ahead
With this partnership now disbanded, Ethereum is committed to advancing the EIP-8141 initiative independently, while Base will continue refining the functionalities outlined in EIP-8130. The distinction between the two proposals underscores divergent philosophies regarding user authentication and transaction processing, which developers had aimed to harmonize before splitting paths.
As the blockchain space evolves, the separation of these two proposals indicates a shift in focus toward differing priorities—Ethereum leans towards security and privacy, while Base emphasizes scalability and compliance. The outcome suggests that developers will need to manage the implications of the new transaction architectures introduced by both Ethereum and Base as they look toward the future of decentralized finance and user interactions with crypto wallets.
