Ethereum and Base account joint abstraction standard

Ethereum and Base have stopped working on a standard for a shared account after attempts to reconcile EIP-8141 & EIP-8130 were unsuccessful. The two networks will now pursue their own transaction design.

Derek Chiang, an Ethlabs Developer said that last week the two authors stopped their work on a common specification after discovering that there were no technical alternatives that would allow Ethereum or Base not to meet the core requirements.

The two proposals aim to simplify the way users interact with their crypto wallets. This includes allowing users to make transactions without first having ETH on hand for gas, and supporting authentication techniques such as mobile passkeys. Teams were investigating whether the same design could be used for both Base Layer 2 as well as Ethereum Layer 1.

“While we identified a number of technical solutions, they all required one side or the other to compromise at least a little bit on their core goals,” Chiang said. “So separate ways we went, putting the burden on wallets to deal with the fragmentation that ensues.”

Chiang says that Ethereum’s developers place a high priority on censorship resistance and privacy while Base focuses more on customization and compliance. The teams couldn’t settle on one format of transaction due to their differences.

The Ethereum Base Account and Abstraction Plans have been split

The wallet developer now has to support two native formats of transaction if EIP-8141 You can also find out more about the following: EIP-8130 both reach production.

Chiang stated that wallets can still offer users a consistent user experience, despite technical differences among networks. This depends on the way developers manage the different standards.

“If they execute well, and if the wallet community can bridge over the fragmentation, we may well end up with the best possible UX for the end users,” “He said”

Developers are now moving in a different direction than they were a few days ago. Crypto.news reported on Sept. 7 that EIP-8141 developer were exploring compatibility with EIP-8130 They worked to find ways of keeping their transactions programmable, but making it easier for infrastructure suppliers to inspect.

Chiang then said that EIP-8130 would provide structures for EIP-8141 frame. This proposed solution was designed to maintain the frames’ programmability while providing wallets and networks with a more clear transaction format.

EIP-8130 makes use of an onchain keystorage where account holders can store approved actors or authenticator contracts. The transactions identify which authentication method is used, so that a network can determine what validation procedure to use before running wallet code.

EIP-8141 goes a completely different direction by structuring the transactions into programmable contracts called frames. Within the same transaction frames may perform various functions, such as validation, approval for gas, and execution.

Now, the teams have abandoned their efforts to convert these approaches into a single standard.

EIP-8141 is now a MUST-SHIP Ethereum proposal

Ethereum is continuing with EIP-8141, or Frame Transactions, as part of its planned Hegotá upgrade.

Ethereum Foundation Protocol cluster has placed this proposal in its “must-ship” According to the sources, the proposal is to integrate account abstraction into Ethereum to enhance security and prepare for the post-quantum era.

Frame Transactions break a transaction down into several programmable frames. A frame may validate a sender’s identity, while another authorizes the gas account. Subsequent frames will execute actions as requested by the customer.

This model allows for the accounts initiating and paying an action to be distinct.

Ethereum Developers have already been around scheduled EIP-8141 for Hegotá On or before Sept. 7, Core developers were able to move the proposal from Considered For Inclusion (CFI) to Scheduled For Inclusion (SI) during the All Core Developers Execution meeting on Aug. 27, giving Frame Transactions the official status in the upgrade planned for 2027, even though its specifications remained in draft.

In the proposed system an application can cover a users transaction fee, or make arrangements for them to pay using another asset. Ethereum validators will continue to receive their network fee via ETH.

This structure would remove the requirement that users of stablecoins and other tokens must have ETH in order to make transactions.

You can also use frames for batching transactions. Similar actions can be grouped together so they all work or get reversed if any one fails.

Token trades, for instance, require an approval before they can be executed. Frame Transactions allow for related transactions to occur within the one programmable transaction.

Ethereum Account Controls Expanded by Programmable Frames

EIP-8141 aims to transfer more account logic into code that can be programmable, rather than relying on fixed authentication processes for conventional Ethereum accounts.

This proposal describes the end-state as one that is where “an account simply becomes an address with code.”

Vitalik Buterin (co-author of EIP-8141) described the proposal as “an” in February. “omnibus that wraps up and solves every remaining problem that AA was intended to address.”

Buterin stated that the proposal was made on Sept. 5. “a lot of important progress” Over the previous months, I was getting “close to optimal.”

Afterwards, developers discovered that many transaction features can be expressed by using programmable EIP-8141 frames Ethereum does not need to be expanded.

In a Sept. 7 report, crypto.news said that the approach would handle transactions expiry, privacy proofs, post-transaction affirmations, and signature aggregation as programmable contracts calls. Although Frame Transactions will still need to be modified, they can also include individual functions through the use of frame targets and calls patterns.

Programmatic validation can give users more control of authentication. EIP-8141 was designed to include features like alternative signatures systems, sponsored payments for gas, transaction batching, and key rotation.

This architecture would allow Ethereum accounts to be independent of the signature system that is used for conventional externally held accounts. The user can change the account’s authentication without having to transfer the funds.

Ethereum researchers had been considering Frame Transactions for Hegotá before the proposal was formally scheduled. Developers were notified in August that the proposal was to be scheduled. comparing EIP-8141 with EIP-8130 As competing approaches to native accounts abstraction, while narrowing scope of 2027 upgrade.

At the time, the proposals were part of a larger Hegotá selection process covering censorship resistance, privacy, gas pricing, validator economics and Layer 1 scaling.

Researchers at Ethereum had independently examined Frame Transactions and how they could be used to support privacy-focused applications. The August proposal was discussed self-funded privacy pools In which the programmable payment of fees could enable a private pool to pay for its own gas without relying upon an external relayer.

The work included Frame Transactions as well as other changes proposed, including Recent Roots, Keyed Nonces or Transaction Assertions. Privacy-pool was not a developer’s final choice, but rather a preferred package for researchers.

Continue base with EIP-8130

Base’s EIP-8130 proposal will be handled separately from Ethereum Frame Transactions.

Base-authored design is a combination of a new type of transaction with onchain. “Keystore” This app allows you to track the approved signers for a particular account. This application is designed to provide custom authentication, gas sponsorship and call batching.

The two proposals may share some account abstraction objectives, but their different technical structures allow their respective networks to have a greater level of control on the way transactions are processed and authenticated.

Ethereum’s developers were trying to figure out, before the two teams split up, if EIP-8130’s structured authentication could be combined EIP-8141’s programmable frame without forcing Layer 1 and Layer 2 networks into giving up their desired properties.

Ethlabs previously listed Frame Transactions as one of its top priorities. priorities for the Hegotá upgradeThis is a native account abstraction that cites censorship resistence, faster blocking and Layer 1 scaling.

With the joint effort now ended, EIP-8141 remains Ethereum’s planned native account abstraction route for Hegotá, while Base will continue developing EIP-8130 around its separate transaction type and onchain keystore.