In recent weeks, two of the most prominent blockchain platforms—Ethereum and Base, the Layer‑2 network launched by Coinbase—have announced that they will no longer pursue a single, shared wallet standard after months of negotiation and technical deliberation. The decision marks a significant shift in the way developers, wallet providers, and end‑users will have to handle transactions that span both ecosystems. While Ethereum is moving forward with the implementation of EIP‑8141, a proposal that introduces a new transaction format designed to improve scalability and user experience, Base has chosen to adopt a different specification, EIP‑8130, which aligns more closely with its own design goals and the expectations of its user base. This divergence means that applications and wallets that aim to support both networks will now need to accommodate two distinct transaction systems, each with its own set of rules, data structures, and signing mechanisms.
## Background on the competing proposals EIP‑8141, short for Ethereum Improvement Proposal 8141, was drafted by a coalition of core developers, wallet engineers, and community contributors who sought to streamline the transaction flow on Ethereum’s mainnet and its expanding ecosystem of Layer‑2 solutions. The proposal introduces a unified transaction envelope that can carry additional metadata, support batch processing, and enable more flexible fee structures. Proponents argue that EIP‑8141 will reduce the friction users experience when moving assets between Ethereum and various scaling solutions, because a single transaction format can be recognized and processed by a wide array of clients without the need for custom adapters.
Conversely, EIP‑8130 was championed by the team behind Base, which is built on the OP Stack and benefits from close integration with Coinbase’s infrastructure. This proposal focuses on optimizing transaction throughput for Base’s specific roll‑up architecture, emphasizing lower latency, cheaper gas costs, and tighter compatibility with Coinbase’s custodial services. While EIP‑8130 shares some conceptual overlap with EIP‑8141—such as the idea of richer transaction payloads—it diverges in the way signatures are encoded and how fee markets are calculated, reflecting the distinct economic model that Base employs. ## Why the talks stalled The discussions that began in early 2024 were initially optimistic.
Both sides recognized that a common standard would simplify onboarding for new users, reduce development overhead for multi‑chain wallets, and foster a more cohesive DeFi landscape. However, technical disagreements soon emerged. Ethereum’s core developers were hesitant to adopt certain optimizations that would compromise backward compatibility with legacy contracts, whereas Base’s engineers prioritized performance gains that required changes to the underlying transaction verification logic.
Moreover, governance considerations played a role: Ethereum’s decentralized decision‑making process involves a broad community vote, while Base’s roadmap is more tightly controlled by Coinbase’s product team, leading to differing timelines and priorities. Another point of contention was the handling of fee markets.
EIP‑8141 proposes a flexible, user‑selected fee model that can adapt to network congestion, whereas EIP‑8130 embeds a fixed‑price mechanism designed to keep transaction costs predictable for Base users. Reconciling these approaches proved difficult, as each side feared that compromising would either erode Ethereum’s long‑term scalability vision or dilute Base’s competitive advantage in offering low‑cost transactions. ## Implications for wallets and dApps With the split now official, wallet developers must implement dual support.
This means that a wallet that previously relied on a single transaction schema will need to detect the target chain, apply the appropriate encoding rules, and possibly present different fee options to the user. For example, a user sending USDC from an Ethereum address to a Base address will now encounter two separate signing flows: one that conforms to EIP‑8141 for the Ethereum leg and another that follows EIP‑8130 for the Base leg. Developers will need to update SDKs, UI components, and backend services to handle these nuances. Decentralized applications (dApps) that operate across both networks will also face added complexity.
Smart contracts that interact with both Ethereum and Base will need to be aware of the differing transaction formats when constructing cross‑chain calls, especially if they rely on meta‑transactions or gas‑sponsorship features. Some projects may choose to abstract the differences behind a middleware layer, but this adds latency and potential points of failure. ## Potential workarounds and future outlook Despite the setback, the community is exploring interim solutions.
One approach is the creation of adapter libraries that automatically translate between EIP‑8141 and EIP‑8130 structures, allowing developers to write code once and let the library handle the conversion. Another possibility is the emergence of a third‑party standard that sits atop both proposals, offering a common interface while delegating the low‑level details to the respective chains. In the longer term, both Ethereum and Base may revisit their standards as the ecosystem matures.
If a compelling use case arises—such as a major DeFi protocol demanding seamless cross‑chain liquidity—there could be renewed pressure to converge on a unified format. Until then, the onus remains on wallet providers, infrastructure teams, and developers to bridge the gap. ## Conclusion The decision by Ethereum to press ahead with EIP‑8141 and by Base to adopt EIP‑8130 reflects the reality that, while collaboration is desirable, technical and governance differences can lead to divergent paths. Users can still enjoy the benefits of both networks, but they should be prepared for a slightly more fragmented experience when moving assets or interacting with applications that span Ethereum and Base.
As the blockchain space continues to evolve, the industry will likely see further attempts at standardization, but for now, the two standards will coexist, each serving the specific needs of its respective community.