The Ethereum developer community is currently discussing how to implement native account abstraction (AA) as plans for the upcoming Hegota hard fork move forward.
Several proposals have emerged in recent weeks, with EIP-8141, also known as “frame transactions,” gaining traction. This proposal has been formally introduced as a major feature candidate for upgrade.
Next, discussionVitalik Buterin publicly responded to this proposal, stating that frame transactions have the potential to simplify wallet architectures while supporting a broader range of privacy and censorship-resistant use cases.
Discussion about native account abstraction gains momentum
Our efforts towards native account abstraction have increased over the past month, introducing multiple Ethereum improvement proposals.
EIP-8141 We propose a model known as frame transactions. This differs from traditional transaction formats by removing embedded signature fields. Instead, the signature and authorization logic is passed as data to a smart contract that validates the transaction.
The proposal introduces a new opcode, APPROVE, that allows smart contracts to authorize transaction submissions, gas payments, or both.
Additionally, this design allows transaction authentication to be handled by programmable logic rather than fixed transaction fields. According to the proposal, this structure could support alternative signature systems, conditional gas sponsorship, and privacy-oriented trading mechanisms.
https://t.co/8L45rn3Zgx
— Derek Chan | ZeroDev (@decentrek) March 9, 2026
For example, gas sponsorship can be arranged through agreements that pay network fees in exchange for token transfers, while authorization logic can be implemented using multi-signature or alternative encryption schemes.
See also Solana Price Analysis: Solana Prepares to Challenge 71.8% FIB Retracement at $49
At the same time, this model brings new operational challenges. Ethereum clients require additional protection against denial of service attacks from memory pools, as smart contract code may be executed during transaction validation.
Frame transactions and tempo transactions
The debate over native account abstraction hints at two different design philosophies in Ethereum development.
One approach, exemplified by Tempo Transactions, is to embed commonly used account abstraction functionality directly into the protocol. These include gas abstraction, atomic batching of multiple operations, transaction scheduling, and sponsored transaction fees.
Tempo-style transactions organize these features directly into a transactional format. Fields such as arrays of calls enable atomic batch processing, and timestamp parameters can be used to support scheduled execution. A separate signature field allows a third party to cover the gas bill by co-signing the transaction.
Developers promoting this model argue that building functionality directly into the protocol is easier to integrate and provides a better user experience. However, this approach may be somewhat scalable, as new features require protocol upgrades.
Frame transactions take the opposite approach by using generalized primitives instead of predefined functions. Authorization and gas payment logic can be implemented in smart contracts, allowing developers to create custom systems for signing, authorization, and transaction validation.
See also Cryptocurrency Perpetual Futures Trading: Things to Consider
Vitalik Buterin highlights privacy and implications for wallet design
In response to ongoing discussions, Vitalik Buterin Frame transactions also make it possible to run privacy-sensitive applications without the need for a public transaction broadcaster, he said.
According to Buterin, this design allows privacy systems like Railgun and other protocols to interact directly with network capabilities like FOCIL while remaining censorship-resistant.
this is a good post. Thank you for your contributions to improving Frame TX.
Adding further:
*Frame TX is also intended to cover long-tail use cases of privacy and censorship resistance. These allow railguns, PP, etc. to function without public broadcast intermediaries, and…
— vitalik.eth (@VitalikButerin) March 9, 2026
He also identified potential changes to the wallet’s architecture. Citing Bitcoin’s multi-signature wallet design, Buterin said the idea that “every wallet is a smart contract” has already been successfully implemented in other ecosystems.
In his opinion, wallets built using EIP-8141 are relatively simple and may only be able to perform a small number of operations similar to Bitcoin scripts.
Buterin said that many wallet functions currently implemented in large-scale smart contracts, such as transaction batching and signature hash calculations, could potentially be moved outside of the wallet code using the proposed structure.
