In a surprising turn of events for the blockchain community, two of the most prominent platforms in the Ethereum ecosystem have decided to part ways on a long‑awaited common wallet standard. After months of behind‑the‑scenes discussions, Ethereum’s core development team has moved forward with the implementation of EIP‑8141, a proposal that aims to streamline transaction handling and improve user experience on the main network.
At the same time, Base, the Layer‑2 solution launched and supported by Coinbase, has announced its commitment to a different specification, EIP‑8130, which addresses similar concerns but follows a distinct technical approach. This divergence means that developers, wallet providers, and decentralized applications (dApps) that operate on both Ethereum and Base will now need to support two separate transaction formats, potentially adding complexity to cross‑chain interactions.
### Background on the wallet standards Both EIP‑8141 and EIP‑8130 were born out of a shared desire to simplify the way users sign and broadcast transactions across multiple networks. Historically, Ethereum’s transaction model has evolved from the original simple value transfer to more sophisticated constructs that include contract calls, gas fee mechanisms, and, more recently, support for account abstraction.
Account abstraction—an idea that lets smart contracts act like user accounts—has been a focal point for many improvement proposals because it promises to make wallet experiences more intuitive, enabling features such as social recovery, multi‑signature protection, and gas‑payment flexibility. EIP‑8141, championed by several core contributors to the Ethereum Foundation, builds on the concept of "UserOperations" introduced in EIP‑4337. It proposes a unified transaction envelope that can encapsulate a variety of actions, from simple ETH transfers to complex contract interactions, while allowing the transaction fee to be paid in tokens other than ETH. The proposal also introduces a standardized method for bundling multiple operations into a single batch, reducing on‑chain overhead and improving throughput.
EIP‑8130, on the other hand, was drafted by a team of engineers working closely with Coinbase’s Base team. While it shares the overarching goal of abstraction, it takes a different route by defining a new transaction type that separates the signature payload from the execution payload.
This separation is intended to make it easier for hardware wallets and custodial services to validate signatures without needing full access to the execution data, thereby enhancing security for high‑value custodial solutions. Additionally, EIP‑8130 includes provisions for deterministic nonce handling, which can help prevent replay attacks across multiple roll‑ups and Layer‑2 networks.
### Why the split happened The negotiations between the Ethereum core developers and the Base team began in early 2023, when both parties recognized the growing demand for a universal wallet standard that could span the expanding multi‑chain landscape. Initial meetings were optimistic, with both sides agreeing on many high‑level principles: user‑centric design, backward compatibility, and support for future fee models. However, as technical details were hashed out, fundamental disagreements emerged.
One of the primary points of contention was the handling of signature schemes. Ethereum’s community has largely coalesced around the use of the secp256k1 curve, the same curve used by Bitcoin, because of its widespread hardware support and mature tooling.
Base’s engineers argued for a more flexible approach that would allow alternative curves, such as Ed25519, to be natively supported, citing better performance and stronger security guarantees for certain use cases. The Ethereum team was hesitant to adopt a multi‑curve model without a clear migration path, fearing it could fragment the ecosystem. Another area of disagreement involved fee payment flexibility.
EIP‑8141’s design permits users to pay transaction fees in ERC‑20 tokens, leveraging a paymaster contract that can convert those tokens to ETH behind the scenes. Base’s proposal, while also supporting token‑based fees, introduced a novel escrow mechanism that would lock the fee token until the transaction is finalized, providing an extra layer of assurance for validators on the roll‑up. Ethereum’s developers expressed concerns about the added state bloat and potential latency introduced by such escrow contracts.
Ultimately, after several rounds of compromise attempts, both camps concluded that the technical trade‑offs were too significant to reconcile within a single standard. Rather than force a half‑baked solution, each group decided to pursue its own path, hoping that the market would eventually favor the approach that best serves users. ### Implications for wallets and dApps The immediate fallout from the split is that wallet developers now have to implement support for two distinct transaction formats if they wish to offer seamless experiences on both Ethereum and Base. For custodial wallets, this means integrating both the EIP‑8141 bundling logic and the EIP‑8130 escrow workflow, potentially increasing development overhead and testing complexity.
Non‑custodial wallets, especially those that rely on hardware devices, must ensure that their signing algorithms can accommodate both the unified signature payload of EIP‑8141 and the separated payload model of EIP‑8130. For dApp developers, the divergence introduces additional considerations when designing cross‑chain functionalities. A DeFi protocol that wants to allow users to deposit assets on Base while also supporting withdrawals to Ethereum will need to handle two different fee‑payment mechanisms and possibly different nonce management strategies. This could lead to higher gas costs for users, as developers may need to implement fallback logic or duplicate transaction pathways.
However, the split also opens up opportunities for innovation. Some developers see the coexistence of two standards as a chance to build adapters or middleware layers that translate between EIP‑8141 and EIP‑8130, effectively acting as bridges at the protocol level. Such adapters could abstract away the complexity for end‑users, presenting a unified interface while handling the underlying differences behind the scenes.
### Looking ahead While the decision to diverge may initially appear as a setback for the vision of a single, universal wallet standard, it reflects the healthy diversity of thought within the Ethereum ecosystem. Both proposals address real user pain points, and each brings unique strengths to the table. Over time, market adoption will likely reveal which approach offers the best balance of security, usability, and scalability.
In the meantime, developers and wallet providers are encouraged to stay informed about the latest updates to both EIP‑8141 and EIP‑8130, participate in community discussions, and contribute to tooling that eases cross‑chain compatibility. The broader goal remains the same: to make blockchain interactions as simple and secure as possible for everyday users, regardless of which network they choose to engage with. As the ecosystem continues to evolve, the lesson learned from this episode may be that a single, monolithic standard is less important than a robust set of interoperable protocols that can adapt to the varied needs of users, developers, and enterprises alike.