Ethereum and Base Split on Account Abstraction Standards

Ethereum and Base have officially ended collaboration on a unified account abstraction standard. The effort to merge EIP‑8141 (Ethereum) and EIP‑8130 (Base) collapsed when technical options required one side to compromise on core goals.

Why the split occurred

Ethereum’s priority list emphasizes censorship resistance, privacy and security, while Base focuses on scalability, customization and compliance. According to Ethlabs developer Derek Chiang, the two proposals could not be combined without sacrificing at least one of these objectives.

What the proposals entail

EIP‑8141 (Frame Transactions)

• Structures transactions as programmable “frames” that can validate, sponsor gas and execute actions.
• Enables separate accounts for transaction initiation and gas payment.
• Supports features such as sponsored gas, transaction batching, alternative signatures and key rotation.
• Designated a “must‑ship” proposal for Ethereum’s upcoming Hegotá upgrade.

EIP‑8130 (Base Keystore Model)

• Introduces an on‑chain keystore where accounts register approved signers and authenticators.
• Allows custom authentication methods, call batching and gas sponsorship.
• Tailored to Base’s Layer‑2 environment and compliance requirements.

Implications for wallets

If both standards reach production, wallet developers may need to support two native transaction formats. Chiang notes that a well‑executed wallet layer could still present a seamless user experience despite the underlying fragmentation.

Next steps

Ethereum will continue advancing EIP‑8141 as part of the Hegotá upgrade, scheduled for 2027. Base will proceed independently with EIP‑8130, developing its own transaction type and keystore architecture.