Effort to Reconcile EIP-8141 and EIP-8130 Reportedly Breaks Down
Ethereum and Coinbase-backed Base are reportedly moving ahead with separate approaches to native account abstraction after an effort to reconcile two competing standards broke down last week, potentially leaving wallets and applications to manage compatibility between the two systems.
Ethlabs researcher Derek Chiang said the collaboration around Ethereum’s EIP-8141 Frame Transactions and Base-backed EIP-8130 had ended, according to a Sept. 14 report. Chiang is also listed as one of the authors of EIP-8141.
The disagreement does not mean Ethereum and Base have different goals for users. Both proposals are designed to make blockchain accounts substantially easier to use by enabling features such as sponsored or gasless transactions, transaction batching, alternative authentication methods and wallets that do not depend exclusively on traditional private-key signing.
The dispute is instead about how those capabilities should be implemented at the protocol level.
EIP-8141, known as Frame Transactions, introduces a new Ethereum transaction format that divides transactions into programmable frames. Those frames can perform validation, authorize gas payments and execute user operations, giving developers considerable flexibility over how an account behaves.
The design is intended to make accounts programmable at a deeper level while supporting features such as key rotation, alternative fee-payment systems and future post-quantum security.
Ethereum developers have now formally placed EIP-8141 among the proposals scheduled for inclusion in Hegotá, the network’s upcoming upgrade. The Hegotá Meta EIP currently lists Frame Transactions alongside EIP-7805 as scheduled features, although specifications can still change before activation and no mainnet activation date has yet been set.
Base is pursuing EIP-8130.
The proposal, authored by Base’s Chris Hunter, combines a new account-abstraction transaction type with an onchain keystore and a system of authenticators that define how an account can authorize transactions.
A key design objective is predictability. Rather than requiring nodes to execute arbitrary wallet logic simply to determine whether a transaction is valid, EIP-8130 lets a transaction identify its authenticator in advance. Nodes can therefore understand the validation work required before executing the transaction.
That matters particularly for high-throughput Layer 2 networks, where unpredictable validation workloads can complicate performance and denial-of-service protections.
Base says EIP-8130 will form part of its planned Cobalt upgrade, with Sepolia and mainnet deployments both currently listed as being in planning for September.
According to Base, native account abstraction under EIP-8130 is designed to support batch transactions, gas sponsorship, session keys, multiple authentication schemes, account portability and parallel nonces. Base also says the architecture can cut transaction costs by more than half compared with the previous generation of smart accounts.
The proposal reflects a broader shift toward treating wallet infrastructure as part of the underlying financial stack rather than merely as an interface sitting above the blockchain.
The technical disagreement has been developing for several weeks.
Chiang wrote in August that Ethlabs had been working with authors of both proposals to identify common ground between the approaches. Ethereum developers were interested in preserving the flexibility of Frame Transactions, while Layer 2 developers were concerned about the operational cost of allowing highly dynamic transaction-validation logic.
A native standard shared by Ethereum and its Layer 2 networks could have made the same account behavior available across multiple chains without wallets having to understand substantially different transaction formats.
That concern is particularly important as crypto increasingly depends on cross-chain interoperability. Assets may already move between networks relatively easily, but moving the user’s account configuration, authentication method and transaction experience between those networks is a separate challenge.
The two proposals still contain mechanisms intended to preserve portability.
EIP-8130 says accounts can continue operating on chains that do not support its native transaction type through mechanisms such as ERC-4337. It also defines a canonical authenticator set intended to give wallets a common baseline across compliant networks.
EIP-8141 takes a more general approach, using EVM execution to make transaction validation and gas payment programmable.
Both standards remain drafts. The reported breakdown therefore represents a divergence in the current development path rather than two permanently finalized and incompatible protocols.
But if both systems ship substantially as currently designed, developers could eventually face different native account-abstraction environments on Ethereum and Base.
Fragmentation May Be Manageable, but It Moves Complexity Somewhere Else
Account abstraction sounds like an obscure protocol debate until you look at what it is actually trying to fix.
Crypto wallets are still unnecessarily difficult.
Users need gas tokens. They manage seed phrases. One transaction often requires several approvals. Changing keys can be painful. Applications frequently build their own workarounds for features that consumers already expect from normal financial apps.
Native account abstraction is supposed to make much of that disappear.
The irony is that Ethereum and Base appear to agree on the experience they want to create while disagreeing about the infrastructure underneath it.
That may not be disastrous.
The web works despite browsers, operating systems and payment systems using different internal architectures because applications hide most of that complexity. Crypto can do the same thing.
Wallets could detect which network a user is on and automatically construct an EIP-8141 transaction on Ethereum or an EIP-8130 transaction on Base. Applications could expose the same button while entirely different transaction logic operates underneath.
But somebody still has to build and maintain that abstraction layer.
This is where the cost of fragmentation moves.
Instead of Ethereum and Base agreeing on one native standard, wallet providers, SDK developers and onchain applications may need to support multiple transaction models.
For large wallet companies, that is probably manageable. For smaller developers, every additional execution path creates more testing, security work and maintenance.
There is also a deeper security issue.
Cross-chain systems repeatedly demonstrate that complexity tends to create attack surfaces. Problems do not always exist in the blockchain itself; they can emerge in the surrounding infrastructure responsible for translating information between systems. The failure of a component supporting multichain applications can be enough to disrupt an otherwise correctly functioning protocol.
Account abstraction raises a similar concern. If wallets have to translate between different authentication, sponsorship and transaction-validation schemes, that translation layer becomes critical infrastructure.
There is nevertheless a strong argument for allowing Ethereum and Base to optimize for different priorities.
Ethereum L1 is designed around extreme neutrality, censorship resistance and long-term protocol durability. Base operates a high-throughput Layer 2 and can make more opinionated engineering choices to improve performance and compliance.
Forcing both networks into one standard could produce a compromise that neither side particularly wants.
Separate standards also let the market test both approaches.
If EIP-8130 delivers lower costs and better performance without meaningful portability problems, other Layer 2 networks could adopt similar architecture. If Frame Transactions prove easier for developers to extend and better suited to new cryptography, privacy systems or authentication models, Ethereum’s more flexible approach could become the stronger long-term foundation.
The biggest risk is therefore not that Ethereum and Base are experimenting differently.
It is that the ecosystem fails to hide those differences from users.
Crypto already has enough fragmentation across bridges, wallets, networks and liquidity venues. Recent incidents involving bridge infrastructure show how technically complex cross-chain systems can become when multiple moving parts must remain synchronized.
If account abstraction succeeds, users should eventually stop thinking about gas tokens, transaction formats and signature standards altogether.
Whether Ethereum and Base use the same mechanism underneath may not matter.
But if users or developers have to understand the difference between EIP-8130 and EIP-8141 just to make the same wallet work on both networks, the infrastructure has failed to deliver the abstraction its name promises.
Shane Neagle is a financial markets analyst and digital assets journalist specializing in cryptocurrencies, memecoins, prediction markets, and blockchain-based financial systems. His work focuses on market structure, incentive design, liquidity dynamics, and how speculative behavior emerges across decentralized platforms.
He closely covers emerging crypto narratives, including memecoin ecosystems, on-chain activity, and the role of prediction markets in pricing political, economic, and technological outcomes. His analysis examines how capital flows, trader psychology, and platform design interact to create rapid market cycles across Web3 environments.
Alongside digital assets, Shane follows broader fintech and online trading developments, particularly where traditional financial infrastructure intersects with blockchain technology. His research-driven approach emphasizes understanding why markets behave the way they do, rather than short-term price movements, helping readers navigate fast-evolving crypto and speculative markets with clearer context.