What to Know

  • Ethereum is moving ahead with EIP 8141, known as Frame Transactions, while Coinbase backed Base is advancing EIP 8130.
  • The two networks ended efforts to create a shared standard for next generation crypto wallets after months of discussions.
  • The split could require wallets and applications that operate across both networks to support two different transaction systems.
  • Ethereum’s proposal emphasizes privacy, censorship resistance, security and protection against possible future quantum threats.
  • Base’s proposal prioritizes flexibility for high volume applications and systems that may have compliance requirements.
  • EIP 8141 is being pushed toward Hegotá, Ethereum’s planned upgrade after Glamsterdam, but it remains under development and is not live on Ethereum today.
  • EIP 8130 is already available for testing on Base’s Vibenet development network and is planned for the Cobalt upgrade, with testnet and mainnet deployments currently listed for September.

Ethereum and Base Choose Different Wallet Paths

Ethereum and Coinbase backed Base have abandoned an effort to create a common standard for the next generation of crypto wallets, marking a notable split between two major parts of the Ethereum based ecosystem. After months of technical discussions, developers on both sides concluded that a merged design would force each network to surrender features it considers central to its long term roadmap.

The disagreement does not mean either network is walking away from the broader goal of improving wallets. Both Ethereum and Base are trying to make crypto accounts easier to use, more flexible and more suitable for mainstream applications. The divide is about how those improvements should be built into transaction rules, who should have authority to approve actions, who should be able to pay fees and how much flexibility applications should receive when coordinating user activity.

Ethereum is proceeding with EIP 8141, also called Frame Transactions. Base is backing EIP 8130, a competing proposal designed around different performance and application needs. Both proposals remain draft level standards, but the decision to stop pursuing a unified approach is already important for developers who build wallets, apps and infrastructure that span Ethereum and Base.

What the Wallet Standards Are Trying to Change

The next generation wallet effort is aimed at making crypto wallets behave more like modern apps. In the current user experience, many people still need to manage seed phrases, hold ETH for network fees and approve separate blockchain steps one by one. The proposed wallet standards are designed to open the door to more flexible account behavior without abandoning the security guarantees that make blockchains useful.

Under the new models being discussed, users could log in with passkeys, recover accounts through different methods, allow an application to pay transaction fees on their behalf and bundle several blockchain actions into a single transaction. The practical result could be a smoother experience in which holding ETH just to pay a network fee becomes optional rather than mandatory.

That kind of change matters because wallet friction remains one of the largest obstacles for crypto adoption. A user who wants to try an application can be stopped by the need to buy ETH, transfer it to the correct network, approve multiple actions and understand why each step costs gas. More programmable wallets could reduce that complexity, especially for users who are not already familiar with blockchain mechanics.

Why the Common Standard Broke Down

The effort to merge the Ethereum and Base approaches broke down because each network has different priorities. Ethereum wants its design to protect privacy, censorship resistance and security as wallets become more programmable. Base wants more room to optimize transactions for high volume applications and for systems that may involve compliance requirements.

Derek Chiang, an Ethlabs developer involved in the work, said on X that Ethereum wanted to be the best version of Ethereum, while Base wanted to be the best version of Base. He said both sides recognized the benefits of interoperability, but that those benefits ultimately became secondary to each chain’s core goals. Chiang also said the cooperation effort broke down last week.

That framing highlights the central trade off. A shared standard can make life easier for developers and users because tools behave consistently across networks. But a shared standard can also limit what each network can optimize for. In this case, attempts to force a common design would have required one side to give up features it viewed as important.

Ethereum’s EIP 8141 Focuses on Security and Resilience

Ethereum’s EIP 8141, known as Frame Transactions, is designed to preserve the network’s core values while expanding what wallets can do. Ethereum developers are especially focused on privacy, censorship resistance and security. Those priorities reflect Ethereum’s role as the base layer for a broad ecosystem in which neutrality and reliability are treated as foundational design principles.

The proposal is also intended to help accounts move away from the cryptography most Ethereum wallets use today if quantum computers eventually make it unsafe. That quantum related concern is not a claim that an immediate threat has arrived. Rather, it reflects long term planning around how accounts could transition if current cryptographic assumptions were to weaken in the future.

EIP 8141 is being pushed toward Hegotá, Ethereum’s planned upgrade after Glamsterdam. Glamsterdam is scheduled for later this year. The Ethereum Foundation this month placed EIP 8141 among the execution layer features it says must ship with Hegotá. That gives the proposal priority, but it does not guarantee final inclusion. EIP 8141 is still being developed and is not running on Ethereum today.

Base’s EIP 8130 Prioritizes Application Flexibility

Base is moving forward with EIP 8130, a design built to provide more freedom for transaction optimization. The Coinbase backed network has become closely associated with consumer applications, stablecoin activity, tokenized markets and developer focused infrastructure. For that environment, Base developers appear to be prioritizing flexibility for high volume applications and for use cases where compliance needs may influence transaction design.

EIP 8130 is already available for testing on Base’s Vibenet development network. It is planned for the Cobalt upgrade, with testnet and mainnet deployments currently listed for September. That makes Base’s path more concrete in the near term, although the standard remains part of an evolving technical process.

The Base approach reflects a broader trend among Ethereum based networks. Layer two ecosystems often inherit Ethereum’s security culture and developer tooling, but they also compete on speed, cost, user experience and app specific customization. As those networks mature, they may decide that identical rules are less valuable than designs tailored to their own users and application demands.

What It Means for Wallets and Apps

The immediate consequence is that wallets and applications operating across both Ethereum and Base may need to support two ways of constructing and approving similar transactions. That could increase engineering complexity for wallet teams, infrastructure providers and app developers that want users to move smoothly between networks.

For users, the impact may not be obvious right away. Wallet providers often hide technical differences behind familiar interfaces. However, supporting multiple standards can affect development timelines, testing requirements and the consistency of features across networks. A wallet feature available on one chain may need additional work before it works the same way on another.

Cross network applications could also face design choices. Some may adopt both standards and abstract the differences away. Others may prioritize the standard used by the network where they see the most activity. Technical traders and infrastructure teams will likely watch whether fragmentation slows adoption or whether specialized standards allow each network to improve faster.

A Turning Point for Ethereum Based Interoperability

Ethereum based networks were once expected to inherit a common set of wallet rules even as they diverged in other areas. The Ethereum and Base split shows that this assumption is no longer certain. Wallet standards sit close to the user experience, and user experience is increasingly a competitive arena.

The decision also illustrates a wider tension in crypto infrastructure. Interoperability helps ecosystems feel unified, while customization lets networks pursue distinct goals. Ethereum’s focus on neutrality and long term resilience may not always align with Base’s push for application flexibility and high volume use cases. Both strategies can be rational, but they may not fit neatly into one standard.

For FXCOINZ readers, the key takeaway is that wallet infrastructure is becoming a major battleground in the next phase of crypto development. The debate is not only about convenience. It touches security, censorship resistance, compliance, scalability and future proofing. As EIP 8141 and EIP 8130 advance separately, developers and users will learn whether the ecosystem can preserve a seamless experience even when the underlying standards diverge.

Frequently Asked Questions (FAQs)

What did Ethereum and Base decide?

Ethereum and Coinbase backed Base ended efforts to create a shared next generation wallet standard. Ethereum is moving ahead with EIP 8141, while Base is continuing with EIP 8130.

Why did the two sides stop pursuing one standard?

Developers concluded that a compromise would require each network to give up features it considered important. Ethereum prioritized privacy, censorship resistance and security, while Base prioritized flexibility for high volume applications and possible compliance needs.

What is EIP 8141?

EIP 8141, known as Frame Transactions, is Ethereum’s proposed standard for more programmable wallet transactions. It is intended to address approval rules, fee payment and post approval behavior while preserving Ethereum’s security and resilience goals.

What is EIP 8130?

EIP 8130 is Base’s competing wallet transaction proposal. It is designed to give Base more freedom to optimize for high volume applications and different types of app requirements.

Will users still need ETH to pay gas fees?

The next generation wallet designs are intended to make holding ETH for network fees optional in some cases. They could allow an app or another party to pay transaction fees, depending on how the wallet and application are built.

Is EIP 8141 already live on Ethereum?

No. EIP 8141 is still being developed and is not running on Ethereum today. It is being pushed toward Hegotá, Ethereum’s planned upgrade after Glamsterdam, but priority does not guarantee final inclusion.

Is EIP 8130 available now?

EIP 8130 is available for testing on Base’s Vibenet development network. It is planned for the Cobalt upgrade, with testnet and mainnet deployments currently listed for September.

How could this affect wallet developers?

Wallet developers that support both Ethereum and Base may need to implement and maintain two different transaction systems. That could increase engineering work and make feature parity across networks more difficult.

Does this mean Ethereum and Base are no longer interoperable?

No. The split concerns next generation wallet standards, not a full break in ecosystem compatibility. However, it does mean that wallets and apps may need extra work to deliver a consistent experience across both networks.