Base‑Ethereum Account Abstraction Collaboration Ends, Two Drafts Diverge

Ethlabs founder Derek Chiang confirmed that the joint effort to align Base’s EIP‑8130 with Ethereum’s EIP‑8141 has ended, leaving each community to advance its own native account‑abstraction proposal.

Background on the effort

The collaboration aimed to create a single native transaction format that could serve both Ethereum and the Base L2. With the split, developers of wallets and dApps will need to handle separate transaction types for each chain.

How the proposals differ

EIP‑8130 introduces a typed transaction that includes an on‑chain keystore and explicit authenticator information. Nodes can reject unknown authenticators before executing any contract code, offering predictable validation costs, especially for high‑throughput L2s.

EIP‑8141 (Frame Transactions) breaks a transaction into a series of “frames” that run EVM code to validate signatures, approve gas payment, and execute user operations. This design provides flexibility for privacy‑preserving signatures and future authentication schemes, but validation costs may vary dynamically.

Portability considerations

EIP‑8130 emphasizes cross‑chain portability, allowing accounts to fall back to ERC‑4337 or other transports on chains that do not support the new transaction type, provided they accept a shared canonical authenticator set.

If the drafts continue separately, there will be no single native transaction format shared between Ethereum and Base, requiring wallets and applications to select the appropriate format per chain.

Possible paths forward

• Expand coordination across Ethereum and its L2 ecosystem to harmonize resources and standards.
• Accept divergent protocols and build abstraction layers in wallets and apps to hide complexity from end users.