Ethereum Developers Prioritize Censorship Resistance Over Buterin-Backed UX Proposal in Hegota Upgrade

Ethereum core developers voted on March 26, 2026, to deprioritize “frame transactions,” a proposal supported by co-founder Vitalik Buterin that would enhance user experience and quantum resistance, in favor of making Fork-Choice Enforced Inclusion Lists (FOCIL) the sole “headliner” feature in the upcoming Hegota upgrade expected in the latter half of 2026.

Frame transactions will instead be “considered for inclusion” as a non-headliner proposal, allowing further vetting without committing to a fixed shipping timeline. Client developers cited complexity concerns, while proponents argued that native account abstraction—a key component of the proposal—is “long overdue” for improving the user experience of blockchain applications.

Hegota Upgrade and the Headliner Decision

FOCIL Secures Priority

In February 2026, Ethereum developers selected FOCIL as the first headliner feature for Hegota. FOCIL is designed to boost the network’s censorship resistance by allowing validators to enforce inclusion of specific transactions. At the March 26 virtual meeting, developers declined to name frame transactions as a second headliner, instead agreeing to consider it for inclusion as a non-mandatory feature. Client developers expressed concern that adding a second headliner could delay Hegota at a time when Ethereum leadership is working to accelerate the cadence of upgrades.

Frame Transactions Proposal

Frame transactions introduce a new transaction type designed to prepare Ethereum for a post-quantum world while offering a more robust version of account abstraction—a feature that would enable familiar web experiences such as username-and-password-style logins and fee-free transactions. The proposal received public support from Vitalik Buterin during the meeting.

Developer Perspectives

Proponents: UX Is Overdue

Parthasarathy Ramanujam, an Ethereum developer, stated: “Native account abstraction on Ethereum is long overdue. If frame transactions isn’t chosen as a headliner, the worry is that we may never implement native account abstraction in the near future.” Biconomy co-founder Ahmed Al-Balaghi added: “We’re all wanting Ethereum to win, and for that to happen we really need the UX to be way better,” noting that frame transactions would enable innovation on both user experience and privacy fronts.

Client Developers Cite Complexity

Ben Adams of Nethermind explained that designating a headliner signals “This is what we are shipping in the fork, we hold the fork until it ships,” which could introduce delays. Besu’s Daniel Lehrner stated: “We think it’s too complex for what it delivers.” Developers from other client teams echoed concerns about the complexity of implementing frame transactions within the Hegota timeframe.

Path Forward

The group agreed to tag frame transactions as “considered for inclusion,” a formal designation that ensures thorough vetting without committing to a specific upgrade timeline. Ansgar Dietrichs, an Ethereum Foundation leader and meeting facilitator, noted: “It seems like there’s overall agreement account abstraction is something that’s important, that needs attention. I do think it will receive that attention now, everyone here wants to work on a resolution.”

Frequently Asked Questions

What is the Hegota upgrade?

Hegota is an Ethereum network upgrade expected in the latter half of 2026. It follows the Glamsterdam upgrade scheduled for the first half of the year. Developers have selected Fork-Choice Enforced Inclusion Lists (FOCIL) as the headliner feature to enhance censorship resistance.

What are frame transactions and why did Vitalik Buterin support them?

Frame transactions are a new transaction type designed to prepare Ethereum for a post-quantum computing environment while implementing a more robust form of account abstraction. Account abstraction would enable traditional web experiences such as username-and-password logins and fee-free transactions. The proposal was intended to improve user experience and security.

Why did developers decide not to include frame transactions as a headliner?

Client developers expressed concern about the complexity of implementing frame transactions within the Hegota timeline. They noted that designating a second headliner could delay the upgrade, while the proposal’s complexity made it difficult to commit to a fixed shipping schedule. The proposal was instead tagged as “considered for inclusion” for further vetting.