Don't want to trade it yourself?
Our desk runs DEX portfolios on profit share.
AI translated#Base#Ethereum#wallets
Ethereum and Base Developers Abandon Unified Wallet Standard
Ethereum and Base to develop separate wallet standards.
The Ethereum and Base teams will continue to develop two separate account abstraction mechanisms: EIP-8141 and EIP-8130. Ethlabs researcher Derek Chiang announced the end of their joint effort on a unified solution.
https://x.com/decentrek/status/2099490351337902392
Both initiatives aim to integrate some wallet functions directly into the protocol. Users will be able to confirm transactions with a smartphone access key, bundle multiple actions into a single transaction, and designate another party to pay transaction fees.
Why Developers Parted Ways
The authors attempted to create a common standard for Ethereum and Base. Talks ended last week due to differing requirements for the future mechanism.
According to Chiang, Ethereum developers focused on censorship resistance, privacy, and security. Base prioritized scalability, configurability, and regulatory compliance.
“We found several technical solutions, but each required one side to compromise on key goals,” he wrote.
As a result, the teams decided to develop EIP-8130 and EIP-8141 independently.
If both proposals are implemented, wallet developers will need to support two native transaction formats—one for Ethereum and one for Base.
Chiang suggested that users might not notice the differences if applications can automatically determine the required format. However, implementing this will increase the workload for wallet developers.
Differences Between the Proposals
EIP-8141 breaks down a transaction into programmable stages, or “frames.” These stages separately verify the sender, determine the fee payer, and execute user-specified actions.
The mechanism allows changing the method of transaction confirmation without transferring assets to a new address. Wallets could switch from current secp256k1 keys to other signature schemes. This is seen as a step in preparing Ethereum for potential quantum attacks.
The proposal also supports batch operations and fee payments by another account, eliminating the need for users to pre-store ETH in each wallet.
Developed by Coinbase engineer Chris Hunter, EIP-8130 takes a different approach. It proposes storing account configurations—authorized keys, confirmation methods, and their permissions—in a separate on-chain Keystore.
When sending a transaction, the wallet specifies the confirmation method in advance. This allows nodes to determine the necessary computations without executing arbitrary code. For high-performance L2 networks, the document provides a limited set of standard authentication methods.
Both proposals are currently drafts, so their specifications may change. EIP-8141 is included in the Hegota upgrade plan, while the implementation timeline for EIP-8130 is unspecified.
In September, the Ethereum Foundation assigned the highest priority to EIP-8141. The proposal became one of two mandatory components of Hegota, alongside the FOCIL censorship resistance mechanism.
Found a mistake in the text? Select it and press CTRL+ENTER
EU Mandates 24-Hour Reporting of Crypto Wallet Vulnerabilities
Coinbase Rebrands Base App to Coinbase Wallet
Researchers Halve Computational Estimate for Quantum Attack on Bitcoin and Ethereum
Ethereum Foundation Protocol Cluster names two must-ship EIPs for Hegota
Bitcoin Falls Below $78,000 Following Fed Chair’s Speech
Ledger Fixes Transaction Replacement Vulnerability in Ethereum App
Ethereum Developers Propose New Deposit Contract for Post-Quantum Signatures
Wintermute Increases Short Positions on Hyperliquid Despite Bitcoin Rally
GnosisDAO Approves Transition of Gnosis Chain to Ethereum Rollup
Source: forklog.com