Base-Ethereum Account Abstraction Collaboration Broke Down, Developer Says
Ethlabs’ Derek Chiang, who based ZeroDev, mentioned a collaboration to reconcile Base-led EIP-8130 with Ethereum’s EIP-8141 Body Transactions ended final week, leaving the 2 sides to pursue separate native account-abstraction requirements.
The official Ethereum Enchancment Proposal registry lists each EIP-8130 and EIP-8141 as drafts. Ethlabs backs Body Transactions for Hegotá, which it describes as an upcoming Ethereum arduous fork, and says it intends to work with Layer 2s and wallets on a rollout.
In sensible phrases, incompatible native transaction sorts would shift extra integration work to pockets and software builders. Chiang mentioned the failed effort was “placing the burden on wallets to cope with the fragmentation that ensues,” though he argued that software program might nonetheless cover these variations from customers.
How the Designs Differ
Account abstraction permits smart-contract accounts to outline their very own validation logic quite than relying solely on fastened guidelines for externally owned accounts. The ultimate ERC-4337 normal gives account abstraction with out altering Ethereum’s consensus guidelines: customers submit `UserOperation` objects to a separate mempool, and bundlers package deal them into transactions for an EntryPoint contract.
Each new drafts transfer account-abstraction capabilities into native transaction dealing with, however they use completely different management factors.
EIP-8130 combines a brand new typed transaction with an onchain keystore and account-configuration system. It helps customized authentication, batched calls and fuel sponsorship. As a result of every transaction declares its authenticator, nodes can determine the required validation work and reject unknown authenticators earlier than executing arbitrary pockets code.
The 8130 draft defines an L1 profile with permissive authenticator acceptance and an L2 profile that limits its native transaction path to a canonical authenticator set. That construction is meant to present high-throughput chains predictable validation prices whereas preserving a typical baseline for wallets.
EIP-8141 as a substitute divides a transaction right into a sequence of “frames,” or contract calls that validate the transaction, approve fuel cost and execute person operations. Its design lets accounts use EVM code to outline validation and gas-payment guidelines, with help for options together with key rotation, batched calls and different charge funds.
Ethlabs has described the central tradeoff: permissionless, EVM-based validation offers Body Transactions flexibility for privateness and future signature methods, however dynamic validation prices can create challenges for high-throughput Layer 2s. EIP-8130 prioritizes extra predictable validation by making the authenticator express earlier than execution.
Portability Strikes Up the Stack
EIP-8130’s draft nonetheless calls portability a high concern. It says accounts can operate on EVM chains that don’t help the 8130 transaction sort through the use of ERC-4337 or one other transport mechanism. It additionally requires compliant chains to simply accept a shared canonical authenticator set.
The reported break up due to this fact wouldn’t essentially make an 8130 account unusable on one other EVM chain. It will, nevertheless, finish the hassle to determine one shared native transaction format for Ethereum and Base if the 2 drafts advance individually. Wallets and apps would want to pick the suitable transaction transport and validation guidelines for every chain.
Chiang outlined two doable responses: broaden coordination over sources shared by Ethereum and Layer 2s, or settle for protocol variations and construct wallets and purposes that summary them from customers. For now, the official EIP registry lists each designs as drafts.
