Ethereum and Base choose separate account abstraction standards EIP-8141 and 8130
Ethereum and Base ended efforts to agree on a shared account-abstraction standard. Derek Chiang, an Ethlabs developer and co-author of one proposal and founder of ZeroDev, confirmed the split. Ethereum will implement EIP-8141, known as Frame Transactions. Base will proceed with EIP-8130, a Keystore-based design. Talks ended the week before Chiang’s post.
What changes for account abstraction
Account abstraction moves smart-wallet logic into base-layer transaction validation. Native support enables fee payments without holding ETH, passkey-based signing on phones, and key rotation without external infrastructure. The split creates two native approaches in the Ethereum ecosystem:
- EIP-8141 Frame Transactions: splits a transaction into frames so accounts define validation and gas payment in code. Flexible design. Heavier for high-throughput chains. Marked “must-ship” for Hegotá, Ethereum’s next hard fork.
- EIP-8130 Keystore-based: introduces a new transaction type paired with an onchain Keystore. Each transaction names the authenticator that validates it, giving nodes predictable costs. Tuned for scale and compliance.
Ethereum prioritizes censorship resistance, privacy, and security. Base optimizes for scale, customization, and compliance. Both networks continue to support ERC-4337 smart-wallet flows, which preserves cross-chain reach but adds interoperability cost when native AA features diverge.
Implications for developers and users
Wallets face the main burden. Providers may need to support both transaction formats to serve users across Ethereum and Base. Chiang argues wallet software can abstract differences from end users, but this claim requires testing as implementations mature.
Ethereum and Base have failed to agree on a shared account abstraction standard.
The two networks will now pursue separate approaches, with Ethereum backing EIP-8141 and Base pushing EIP-8130.
Both are designed to make Ethereum wallets easier to use, including features like… pic.twitter.com/uM6Af7jxl4
— That Martini Guy ₿ (@MartiniGuyYT) September 15, 2026
Why compromise failed
The joint effort attempted to merge Base’s EIP-8130 by Coinbase engineer Chris Hunter with Ethereum’s EIP-8141. Chiang wrote that technical solutions existed but required at least one side to compromise on core goals. The outcome reflects diverging priorities within the ecosystem and raises interoperability friction as networks diverge technically. As Chiang noted, separate paths put fragmentation handling on wallets.
Key takeaways:
- Ethereum: EIP-8141 Frames is slated for Hegotá. Emphasis on flexibility, censorship resistance, and privacy, with higher implementation complexity.
- Base: EIP-8130 provides predictable validation cost via named authenticators and an onchain Keystore, aligning with throughput and compliance.
- Interoperability: ERC-4337 remains a bridge for cross-chain smart-wallet operations, reducing but not eliminating fragmentation.
- User experience risk: success depends on wallet providers masking differences without adding friction or security regressions.
Developers should monitor client support timelines for EIP-8141 on Ethereum and EIP-8130 on Base, the impact on bundlers and paymasters in ERC-4337 flows, and potential cross-chain tooling updates as both standards progress.








