# Hegotá selects 62 proposals and leaves Ethereum with two favorites

> The Ethereum Foundation shortlists 62 proposals for Hegotá: FOCIL and Frame Transactions at the top, 15 in A and 28 rejected with documented reasons.
> By José Maldonado · Ethereum · 2026-10-30

The Ethereum Foundation has published the list it will use to order the work on Hegotá, the upgrade planned for 2027, and the result is an exercise in prioritization that is unusual for the sector. [The foundation's Protocol Cluster](https://www.tokenpost.com/news/technology/42240) evaluated 62 proposals and ranked them by tier. Two came out on top: FOCIL, known as EIP-7805, and Frame Transactions, EIP-8141. The list was published on September 7 and the details became known this week.

The volume of work shows the scale of what lies behind it. Around 60 researchers and engineers from nine different teams issued 397 ratings, which means each proposal was read by several people applying their own criteria and that the result does not depend on its author's enthusiasm.

The final breakdown is useful in itself: two proposals at tier S, fifteen at A that are expected to be included unless scope is cut, seven at C, two awaiting more data and 28 rejected with written justification. Almost half of what was submitted does not make it, and that is the healthy part of the process. For anyone following Ethereum from the outside, what matters is not the jargon but the criteria. A network planning its next upgrade two years out needs to decide what goes in before knowing what will be broken in 2027, and that decision is made with public documentation.

## The two favorites for Ethereum

FOCIL is an inclusion list proposal. The problem it targets is validator-level censorship: a validator can decide not to include certain transactions and, if it controls enough weight, keep them out. Inclusion lists require valid transactions to be included within a deadline, regardless of who proposes them.

Frame Transactions targets account abstraction, a topic Ethereum has been discussing for years and which changes who can pay fees and how an operation is authorized. In practice, abstraction allows an account to be not just a key with a balance but a contract with its own rules, including recovery rules.

Both are at S because they touch the foundations. The first affects the neutrality of the system; the second, the experience of anyone who holds an account. These are changes that require touching clients, tools and contracts, which is why they are planned years in advance.

## The value of a documented no

The most interesting part of the list is what is left out. Of the 62 proposals, 28 were rejected and each has a written reason. In an ecosystem where any change is discussed on forums and social media, having a record of why an idea does not make it is the difference between a decision and a vote by sympathy.

The seven that ended up at C do not disappear either. It means they are considered useful but not a priority, so they remain in reserve for the next upgrade or for a smaller format.

The two awaiting data are the most honest case in the exercise. They are neither approved nor rejected: more information is requested before deciding, which is exactly what should happen when a proposal promises benefits and has not measured them.

Tier

Proposals

What it means

S

2 (EIP-7805 FOCIL and EIP-8141 Frame Transactions)

Core components of Hegotá

A

15

Expected to be included unless scope is cut

C

7

Useful, not a priority for this cycle

On hold

2

Not enough information to decide

Rejected

28

Rejected with written justification

## Why does this matter?

Each update redefines costs and behaviors, and the decisions on the list are felt in the pocket. An inclusion proposal that forces block builders to work with external lists changes latency; an account abstraction one changes how signing works and how a lost account is recovered.

For wallets and application developers, the list is a notice with a two-year margin. Anyone building on Ethereum should read what goes into S and what stays in A: the former will require adapting code, the latter may as well.

There is also a market effect. Proposals that affect fees and transaction ordering are of interest to maximal extractable value teams and block builders, and that is the ground where the most noise is generated. Tiered classification reduces the bargaining surface.

For a small team, the list also serves as a work calendar two years in advance: knowing what is at level A makes it possible to plan migrations without waiting for the final announcement of the upgrade, which always arrives with less lead time than one would like.

It is the same logic other large projects follow when planning fundamental changes. We saw it when analyzing the [Fedora 45 delay due to a compromised certificate](https://observatorioblockchain.com/en/technology/fedora-45-retraso-certificado-emudhra-noviembre/)a well-documented technical blocker delays a delivery and does not sink it. In Ethereum, the equivalent is a proposal that is rejected with arguments instead of being left in eternal limbo.

## The context of the previous cycle

Ethereum reaches Hegotá after a year focused on data capacity, with blobs as the centerpiece and rollups absorbing the cost. That work is not finished and the Hegotá list reflects it: there is no first-tier scaling proposal at level S, and the two chosen ones point to neutrality and accounts.

That choice says a lot about priorities. With scaling delegated to layer two, layer one concentrates on what only it can solve: ensuring no one can be excluded and that accounts work as users expect. It is a division of tasks that the ecosystem has been discussing for some time and that here appears written down.

## What could change between now and 2027

An S level is not a guarantee of delivery. Ethereum's history is full of proposals that were trimmed, split into pieces or postponed when an unexpected problem appeared in testing. Two years remain and the scope can still be reduced, meaning some of the fifteen level A proposals will fall by the wayside.

To follow the process, what is useful is not reading headlines about the next upgrade, but the list and its reasons. There you can see what was decided, with what information and who signed off on it, which is more than most projects in the sector offer when planning their future.

That habit has a low cost and a high return. Anyone who reads the level S proposals with two years to spare can adapt their product calmly; anyone who waits for the final announcement will compete with everyone else for the same engineering time.

And an interesting question remains for the community. If 28 proposals are rejected with documentation, how many of those ideas will come back reformulated in the next cycle? The track record suggests quite a few, and that the classification process serves more to organize the debate than to close it.
