Ethereum and Base Abandon Shared Wallet Standard, Exposing a Philosophical Rift Over Fees, Privacy, and Control

After months of behind-the-scenes negotiations, Ethereum and Base have agreed to disagree — and the outcome could reshape how crypto transactions are approved, paid for, and settled for years to come. At the center of the split are two competing proposals: Ethereum’s EIP-8141, known as Frame Transactions, and Base’s EIP-8130. Both are still drafts, and both aim to change the fundamental rules of blockchain transactions: who gets to approve them, who pays for them, and what happens after they are confirmed.

For most crypto users, a transaction is a simple thing: sign, broadcast, wait. But behind that simplicity lies a delicate stack of assumptions. Today’s conventional Ethereum wallets rely on a single cryptographic key to authorize every move, and every transaction must be paid for with ETH from that same account. That works, but it is rigid. As wallets become more programmable — executing complex strategies, bundling actions, or operating without a human in the loop — the industry needs a more flexible transaction format. Ethereum and Base both recognized this. They just could not agree on what that format should look like.

Insiders say the conversations were serious and sustained. For a while, there was hope that the community could rally around one wallet standard, making life easier for developers and users alike. But the more the two sides talked, the clearer it became that their priorities were not simply incompatible — they were philosophically opposed. Ethereum, with its focus on decentralization and user sovereignty, wanted a proposal that protected privacy and resisted censorship. Base, the fast-growing layer-2 network built by Coinbase, wanted room to optimize for high-volume applications, including those with compliance obligations. In the end, neither side believed it could bend without breaking what made its approach worth pursuing.

Ethereum’s Frame Transactions: Privacy First, Security Always

Ethereum’s proposal, EIP-8141, is rooted in a simple question: how should a transaction behave when the wallet approving it is no longer a simple key pair, but a piece of programmable software? The answer, according to the Ethereum Foundation’s framing, is to create a more flexible and secure transaction type that preserves the core principles of Ethereum even as wallets become far more capable.

The proposal is called Frame Transactions, and it is designed to rethink the relationship between the signer, the payer, and the final state of the network. In traditional Ethereum transactions, these roles are typically fused. The account that signs is the account that pays. But Frame Transactions would allow those roles to be separated in ways that are both practical and privacy-preserving. A wallet could authorize a transaction without necessarily being the entity that pays for it, enabling new kinds of sponsored transactions and fee structures. More importantly, the frame around each transaction can be designed to constrain what happens after approval — preventing malicious or unintended side effects.

Privacy is a central concern. The Ethereum team has repeatedly argued that as wallets become more programmable, the risk of transaction-level surveillance and coercion grows. If every transaction must expose the same level of detail to validators and third parties, then users lose some of the autonomy that makes permissionless networks valuable. Frame Transactions aim to keep the details of user intent protected while still allowing the network to verify that everything is legitimate.

There is also a longer-term threat that the proposal is meant to address: quantum computing. Most Ethereum wallets today rely on elliptic curve cryptography, a signature scheme that has served the industry well but could become vulnerable in a future where quantum computers are powerful enough to break it. If that day comes, users would need a way to move their assets to new, quantum-resistant keys. Ethereum’s proposed standard is designed to make that migration easier, giving accounts a path to transition away from today’s cryptography without losing access to their funds or being forced to manually interact with complicated recovery tools. That is not just a technical feature; it is a form of insurance against one of the most disruptive risks on the horizon.

Base’s Counterproposal: Flexibility, Scale, and Compliance

Base’s EIP-8130 takes a different approach, shaped by the practical demands of a rapidly growing layer-2 ecosystem. Base is not just another rollup; it is a gateway for mainstream crypto adoption, backed by the resources and user base of Coinbase. That position brings with it a particular set of priorities: high throughput, low friction for users, and the ability to serve businesses that operate under regulatory oversight.

Where Ethereum’s proposal emphasizes privacy and resistance to censorship, Base’s proposal emphasizes flexibility. Developers on Base want to build applications that can handle millions of transactions without being constrained by a one-size-fits-all standard. They also want to accommodate systems with compliance requirements — think financial institutions, trading platforms, and tokenized asset issuers that need to enforce know-your-customer rules, transaction limits, or other regulatory safeguards.

For those use cases, the transaction format needs to allow more control over who can submit a transaction and under what conditions. A compliance-friendly standard might let a regulated entity approve transactions that satisfy certain predicate logic, or allow a third-party service to sponsor fees on behalf of users while maintaining auditable records. Base’s backers argue that this kind of flexibility is essential if blockchain technology is going to move beyond niche crypto enthusiasts and into the mainstream economy.

That vision is not radical. In the traditional financial world, every transaction passes through layers of checks and balances. Banks can block suspicious transfers. Exchanges can require additional authorization for large withdrawals. Base wants blockchain transactions to offer similar hooks — not because it wants to undermine decentralization, but because it wants to create a bridge between decentralized networks and regulated institutions.

The two proposals are not merely different technical specs. They represent two competing visions of what blockchain should be. One treats privacy and censorship resistance as sacred. The other treats adaptability and institutional access as equally important. Those visions are not impossible to reconcile in theory, but in practice, every attempt to force them into a single standard required someone to give up something they considered essential.

Why One Standard Was Never Going to Work

According to Chiang, who has been closely involved in the discussions, the breakdown came down to trade-offs that neither side could accept. “Attempts to force a common standard eventually meant one side would have to give up features it considered important,” Chiang said. That observation may sound simple, but it gets to the heart of why blockchain governance is so difficult. Technology standards are not just about code; they are about values.

Ethereum’s core developers have spent years building a network where ordinary users — including those in adversarial environments — can transact without asking for permission. A wallet standard that made it easier for third parties to filter or block transactions would undermine that mission, even if it made life easier for regulated businesses. Privacy is not a feature Ethereum can quietly deprioritize in a standards negotiation; it is foundational to the network’s reason for existing.

Base, for its part, cannot simply adopt Ethereum’s proposal and hope that compliance needs can be solved later. For Base, the ability to build transaction flows that satisfy regulators is a business imperative. The network has positioned itself as a bridge between traditional finance and decentralized applications, and that position depends on being able to support institutional workflows from day one. If Base were to support a standard that made compliance difficult, it would lose the very market share it is trying to grow.

The result is a classic standards standoff. In theory, developers could support both EIP-8141 and EIP-8130. In practice, having two competing standards in the same ecosystem creates confusion for wallet makers, application developers, and infrastructure providers. Translation layers can be built, but they add complexity and risk. For a technology community that values interoperability, the split is an uncomfortable outcome.

Still, there is an argument that the split is the natural outcome of a maturing ecosystem. Ethereum and Base are no longer building in the same context. Ethereum is a settlement layer for the entire crypto ecosystem, with responsibilities to a broad and diverse user base. Base is a specialized rollup focused on consumer and institutional applications. It would be surprising if they produced the same answer to a question as intricate as transaction formatting.

Hegotá Ahead: Ethereum Pushes Forward on Its Own Timeline

Despite the collapse of the joint effort, Ethereum is not slowing down. The Ethereum Foundation has announced that EIP-8141 has been placed on the list of execution-layer features that “must ship” with Hegotá, the network’s planned upgrade after Glamsterdam. Hegotá is expected later this year, though no one familiar with Ethereum development would call the date a hard promise.

Upgrades on Ethereum move through phases. Glamsterdam, widely regarded as a stepping stone, will lay the groundwork for more ambitious changes. Hegotá is intended to be the stage where those changes become visible to users. By including EIP-8141 on the must-ship list, the Ethereum Foundation is sending a strong signal that Frame Transactions are a strategic priority for the network’s immediate future.

But being on a must-ship list is not the same as being live. The Ethereum Foundation’s list is a declaration of intent, not a final seal of approval. EIP-8141 is still in development, and it is not running on Ethereum today. Before it can be activated, it will need to be fully specced, peer-reviewed, implemented across client software, and tested on testnets. That process can reveal issues that force a proposal to be redesigned or postponed, regardless of how well-intentioned the timeline is.

Still, the decision to place EIP-8141 on the critical path for Hegotá is meaningful. It tells wallet developers, infrastructure providers, and the broader community that this is not a side experiment. Ethereum’s leadership sees transaction format innovation as a core part of the network’s future. That matters because standards adoption in crypto is as much about political will as it is about technical merit.

The move also sets up an interesting dynamic between Ethereum and Base. Ethereum is now committing publicly to a timeline for its own proposal, while Base’s EIP-8130 remains an alternative that could gain traction among layer-2 networks and private blockchain deployments. The two standards may end up competing for attention, or they may find a way to coexist in separate corners of the ecosystem. What seems unlikely now is that one will simply absorb the other — at least not without a long period of rivalry and experimentation.

What Comes Next: Paying Gas Without ETH and the Rise of Multiple Standards

The most immediately exciting part of EIP-8141, and the one most likely to catch the attention of everyday users, is its commitment to letting people pay gas fees without having to hold ETH. For anyone who has ever been blocked by a lack of ETH — a problem known in the crypto world as “gas fee friction” — this is a potentially transformative change.

Think about what it means for new users. A person wants to use a decentralized application, but they don’t want to buy ETH just to cover a few dollars in transaction costs. They have a token, or they hold an NFT, or they are using a stablecoin. Under the current system, they often have to go to an exchange, buy ETH, and send it to their wallet before they can do anything. That is a steep barrier to entry, especially for people who are new to crypto and not interested in trading the network’s native token.

Frame Transactions could change that. If a wallet can authorize a transaction while another account pays the gas fee in a different asset, then millions of users could interact with Ethereum without ever worrying about maintaining an ETH balance. This is sometimes called “gasless transactions” or “sponsored transactions,” and it has been a long-standing goal for wallet developers. The fact that Ethereum is now pursuing it at the protocol level is a major signal.

For Base, the value proposition is different but just as important. A transaction format that can be optimized for compliance and high volume opens doors in traditional finance. Payment networks, asset managers, and even governments may be more willing to experiment with blockchain rails if they can control certain aspects of the transaction flow. Base’s proposal could become the blueprint for regulated blockchain use cases, just as Ethereum’s proposal could become the gold standard for permissionless wallets.

In the long run, the failure to agree on a single standard may not matter as much as it appears to today. Many industries live with multiple standards for years before a dominant one emerges. Sometimes the market chooses; sometimes regulators choose; sometimes the technology itself evolves to make the choice obsolete. Crypto has already survived countless disputes over block sizes, token standards, and smart contract languages. A little more competition in the wallet standard space may actually accelerate innovation.

What matters most is that the conversation is happening now. Ethereum and Base have both acknowledged that the old way of doing transactions is not good enough for the future. They just disagree on what should come next. That disagreement is not a failure; it is a sign of a healthy, complicated, and fiercely independent ecosystem. The next year will determine whether Frame Transactions become an Ethereum cornerstone or just another chapter in the blockchain industry’s endless debate about how best to build the future of money.