Image credit: Shutterstock
Ethereum and Base developers have ended an effort to align two competing account abstraction proposals, leaving the networks to pursue separate designs for improving wallet functionality.
The split affects Ethereum’s EIP-8141 and Base-led EIP-8130. Both aim to make features such as gas sponsorship, batched transactions and alternative authentication native to the protocol, but developers could not agree on a single architecture.
Developers Split Over Security, Privacy, and Scaling Priorities
The teams had been trying to define a shared standard that could work across Ethereum Layer 1 and Base. Ethlabs developer Derek Chiang said the talks ended last week after the remaining technical options still required one side to compromise on its core goals.
Ethereum’s approach puts more weight on censorship resistance, privacy and security, while Base is prioritizing throughput, customization, and compliance for its Layer 2 environment. If both proposals reach production, wallets, and infrastructure providers could need to support two different native transaction formats.
EIP-8141 Enters Hegotá “Must Ship” Tier
Ethereum’s EIP-8141, known as Frame Transactions, breaks transactions into programmable frames that can separately handle validation, gas payment and execution.
The design also gives accounts a path away from current ECDSA authentication toward alternatives including post-quantum schemes.
The Ethereum Foundation’s Protocol cluster placed EIP-8141 in its top “must ship” tier for the Hegotá upgrade on Sept. 7.
Base Keeps EIP-8130 on Cobalt Rollout Path
EIP-8130 takes a different approach built around an on-chain keystore and a new transaction type.
Accounts can register approved authentication methods while supporting features including passkeys, gas sponsorship, batching and portable account configuration.
Base announced in July that EIP-8130 would launch with its Cobalt upgrade and later expand to OP Stack chains.
The end of the alignment effort does not stop either proposal. EIP-8141 and EIP-8130 are continuing on separate development paths, with wallet and infrastructure compatibility remaining unresolved if both ultimately reach production.
