Account Abstraction Standards Split
Ethereum and Coinbase Base diverge on new native account-abstraction standards.
Anonymous
Key Points
1
The existing ERC-4337 account-abstraction standard operates as an overlay rather than a protocol-level change: users submit UserOperation objects to a separate mempool, and bundlers package them into transactions for an EntryPoint contract.
2
EIP-8130 would combine a new typed transaction with an on-chain keystore and account-configuration system. Its design allows each transaction to declare its authenticator, enabling nodes to identify required validation work and reject unknown authenticators before executing wallet code.
3
EIP-8141, or Frame Transactions, is described as emphasizing flexible transaction primitives, value capture and post-quantum readiness, and is expected to be included in Ethereum’s planned Hegotá upgrade if it advances beyond its draft stage.
4
Derek Chiang said the failed reconciliation effort was effectively “putting the burden on wallets to deal with the fragmentation that ensues,” while also suggesting software could hide the differences from end users.
Ethereum and Coinbase's Base have abandoned efforts to align competing account-abstraction standards, ending weeks of negotiations that failed to bridge their different priorities. The Block reported that Ethereum will pursue EIP-8141 (Frame Transactions), while Base advances EIP-8130, creating two separate native standards for features like gasless transactions and passkey authentication.
The split reflects a philosophical divide: Ethereum prioritizes censorship resistance and long-term security, while Base emphasizes scalability and compliance. CryptoNews noted that the divergence will shift integration work to wallet and application developers, though software may ultimately hide the differences from end users.
How Account Abstraction Currently Works
Today, Ethereum uses ERC-4337, an overlay standard that operates outside the protocol layer. BigGo Finance explained that users submit UserOperation objects to a separate mempool, and bundlers package them into transactions for an EntryPoint contract. This design separates wallet logic from the base blockchain but requires extra coordination steps.
Base's EIP-8130: On-Chain Keystore Approach
EIP-8130 combines a new typed transaction with an on-chain keystore and account-configuration system. Each transaction declares its authenticator, allowing nodes to identify required validation work and reject unknown authenticators before executing wallet code. This design prioritizes CoinGape noted Base developers' focus on configurability and compliance across Layer 2 networks.
Ethereum's Frame Transactions and Post-Quantum Security
Ethereum's EIP-8141, or Frame Transactions, emphasizes flexible transaction primitives, value capture, and post-quantum readiness. Ethlabs researcher Derek Chiang indicated the proposal is expected to be included in Ethereum's planned Hegotá upgrade if it advances beyond draft stage. This approach reflects Ethereum's emphasis on long-term security and censorship resistance.
Fragmentation Burden Falls on Wallets and Developers
The failed reconciliation effort means wallet and application developers must now support incompatible standards across Ethereum and Base. CryptoNews quoted Derek Chiang saying the split amounts to "putting the burden on wallets to deal with the fragmentation that ensues." However, Chiang suggested that software abstraction layers could ultimately mask these technical differences from end users, softening the practical impact of the divergence.
Sentiment
Mostly NegativeNEGATIVENEUTRALPOSITIVE
Publishers
16
Articles
9
Reach
25
A
AnonymousAuthor
