Ethereum’s Hegotá Upgrade Review Puts Frame Transactions and Privacy Tools in Focus

What to Know

• Ethereum developers are reviewing 66 proposals for Hegotá, the network’s next major upgrade expected to ship in 2027.
• Frame Transactions, also known as EIP-8141, is under consideration and would let accounts customize how transactions are approved, executed and paid for.
• The proposal is being discussed alongside Keyed Nonces, or EIP-8250, and EIP-8272, with the package aimed at reducing the outside infrastructure needed by private payment applications.
• Ordinary ETH transfers would remain transparent; the proposed changes would not make Ethereum itself a private blockchain.
• Only one proposal has been approved so far for Hegotá: FOCIL, a censorship-related measure intended to reduce the power of a single block builder to exclude transactions.
• The deadline for new Hegotá proposals passed on Aug. 6, leaving core developers to decide which candidates can realistically move toward implementation, devnets and testnets.

Ethereum Developers Narrow Hegotá Scope

Ethereum’s Hegotá upgrade is moving into a decisive scoping phase as core developers weigh which changes deserve a path toward implementation, testing and possible release in 2027. The current candidate list includes 66 proposals, covering a wide range of network-level changes that could affect transaction handling, censorship resistance, validator economics, block production and future cryptographic security.

The most closely watched item for privacy-focused developers is Frame Transactions, formally identified as EIP-8141. The proposal would change how Ethereum accounts can define the approval, execution and payment process for transactions. In practical terms, it could make wallets and applications more flexible by allowing different transaction flows rather than forcing every user through the same standard structure.

For Ethereum users, the implications could be broad even if the change remains highly technical. A wallet could support fee payment by another party, combine several actions into a single payment flow, or change the cryptographic method used to approve a transaction without requiring the user to migrate to a new account. For application developers, especially those building privacy systems, the proposal could reduce the need for outside services that currently help get more complex transactions onto the blockchain.

Why Privacy Remains a Challenge on Ethereum

Ethereum’s public ledger is one of its defining features. Every address is permanent, and each address maintains a visible history and balance. That openness allows users, developers and auditors to verify activity across the network, but it also creates a privacy problem for individuals, businesses and institutions that do not want their financial activity exposed to the public.

The issue is especially relevant for payroll, treasury management and payment workflows where revealing balances, counterparties or transaction history can create operational and security risks. While transparency is valuable for settlement integrity, it is not always compatible with private financial activity. As a result, much of the privacy burden has been handled by applications built on top of Ethereum rather than by the base network itself.

Private payment systems can use cryptographic proofs to hide sensitive information, but those systems often require additional infrastructure to submit transactions and coordinate activity. Some designs rely on relayers, which are outside services that send transactions on behalf of users. That can help obscure certain details, but it also introduces another layer of dependency between users and the blockchain.

Frame Transactions is being considered as a way to move part of that complexity into Ethereum’s own transaction model. The goal is not to erase Ethereum’s transparency or turn every transfer into a hidden payment. Instead, the change would give privacy applications more native tools so they require less external machinery to operate reliably.

Frame Transactions Would Change Transaction Flexibility

At the center of the discussion is the idea that an account should be able to define how a transaction is handled. Today, Ethereum transactions generally follow a common structure, with approval, execution and fee payment bound to a relatively standardized flow. EIP-8141 would introduce a more customizable approach, opening the door for accounts that behave differently depending on the needs of the user or application.

Technical traders and market participants may view this as part of Ethereum’s broader effort to make the network more useful for sophisticated application design. The proposal touches the infrastructure layer rather than a single consumer-facing product, meaning its full impact would depend on how wallets, payment systems and privacy applications use the added flexibility if it is eventually approved.

One possible user-facing benefit is fee abstraction, where someone other than the account owner pays the transaction cost. Another is batching, where several actions are packaged into a single payment experience. A further use case involves changing the cryptographic authorization method tied to an account without requiring a disruptive move to a new address.

Those capabilities matter because Ethereum applications increasingly need more advanced transaction handling than simple one-step transfers. The more complex a payment or contract interaction becomes, the more likely developers are to need external coordination services under the current model. Frame Transactions would aim to reduce that dependency.

Keyed Nonces and EIP-8272 Add Supporting Pieces

Frame Transactions is not being evaluated in isolation. Two related proposals, Keyed Nonces and EIP-8272, are part of the same privacy-oriented package under discussion. Together, they address practical problems that can emerge when many users interact privately through shared account structures or more complex transaction pathways.

Keyed Nonces, formally EIP-8250, would allow transactions to use separate counters rather than forcing them to queue behind a single one. On Ethereum, nonce ordering is important because it determines the sequence in which transactions from an account can be processed. If one transaction is delayed, later transactions can be blocked behind it. Separate counters would reduce that bottleneck and help prevent one delayed action from holding up unrelated activity.

EIP-8272 addresses a different problem: making sure a transaction can prove itself against a recent cryptographic record without depending on information that might change while the transaction waits. That matters for applications using cryptographic proofs, where timing and state changes can affect whether a transaction remains valid by the time it reaches execution.

In combination, the proposals are designed to make privacy applications easier to build and operate. They do not perform the privacy work by themselves. Rather, they provide network-level support that could allow privacy tools to function with fewer external components and fewer points of operational friction.

Ordinary ETH Transfers Would Stay Visible

A critical distinction for users and market observers is that Ethereum would not become private by default if the package advances. Normal ETH transfers between standard addresses would remain visible in the same way they are today. Address histories and balances would still be readable on the public ledger.

The privacy benefits would come from applications that use cryptographic methods to hide selected information. Frame Transactions and the accompanying proposals would simply give those applications better support inside Ethereum itself. In other words, the network would remain transparent at the base level, while developers would gain tools to build more private transaction experiences on top of it.

That balance reflects a familiar Ethereum design pattern: preserve the verifiability of the base layer while enabling specialized applications to handle more complex requirements. Privacy remains a sensitive topic in blockchain development, and proposals that support it often need to show that they can improve legitimate use cases without undermining network accountability.

FOCIL Is the Only Approved Hegotá Change So Far

While Frame Transactions has attracted attention, it has not been approved for Hegotá. It is currently marked as considered, which means it remains in the discussion but still has to clear further technical and coordination hurdles. Core developers will decide in upcoming meetings which of the remaining candidates can move forward toward actual implementation work.

So far, only one change has been approved: FOCIL. The measure targets censorship concerns in the block-building process. Under the current structure, the company or operator assembling a block has influence over which waiting transactions are included and can leave some transactions out. FOCIL is designed to reduce that concentration of power by allowing a group of network operators to compile a list of transactions that must be included.

That approach would shift inclusion decisions away from any single builder and toward a broader mechanism. For Ethereum, censorship resistance remains a central value because users expect the network to process valid transactions without arbitrary exclusion. FOCIL’s approval indicates that developers are prioritizing transaction inclusion guarantees as part of Hegotá’s design.

What Comes Next for Hegotá

The deadline for new Hegotá proposals passed on Aug. 6, so the process has moved from collecting ideas to narrowing the field. Core developers are now assessing what can realistically be built, tested and shipped on the expected timeline. Proposals that survive this phase would move closer to implementations, devnets and testnets before any final inclusion decision.

Other Hegotá candidates would speed up block production, change what validators earn for securing the network, and prepare Ethereum for cryptography that can withstand quantum computers. Those areas show the breadth of the upgrade discussion, which extends well beyond privacy and transaction customization.

For investors and builders, the immediate takeaway is that Hegotá remains a work in progress. Frame Transactions could become an important infrastructure change for wallets and privacy applications, but its inclusion is not guaranteed. The next developer meetings will determine whether the proposal package receives enough support, implementation confidence and testing bandwidth to keep advancing toward the 2027 upgrade window.

Ethereum’s upgrade process is deliberately cautious because base-layer changes can have far-reaching consequences. Even widely supported ideas must fit within engineering constraints and avoid introducing unacceptable risk. That means the Hegotá roadmap will likely continue to evolve as developers weigh ambition against what can be safely delivered.

Frequently Asked Questions (FAQs)

What is Ethereum’s Hegotá upgrade?

Hegotá is Ethereum’s next major upgrade under discussion, with developers reviewing a list of 66 proposals and targeting a possible release in 2027.

What are Frame Transactions?

Frame Transactions, or EIP-8141, would let an Ethereum account define how a transaction is approved, executed and paid for, giving wallets and applications more flexibility.

Would Frame Transactions make Ethereum private?

No. Ordinary ETH transfers would remain transparent. The proposal would support privacy applications by reducing some external infrastructure needs, but it would not make Ethereum private by default.

What is Keyed Nonces?

Keyed Nonces, or EIP-8250, would allow separate transaction counters so one delayed transaction does not necessarily block other transactions waiting behind it.

What does EIP-8272 do?

EIP-8272 would let a transaction prove itself against a recent cryptographic record without relying on information that may change while the transaction is waiting.

Has Frame Transactions been approved for Hegotá?

No. Frame Transactions is being considered for Hegotá, but it has not been approved. Core developers still need to decide which proposals will move forward.

What has already been approved for Hegotá?

FOCIL is the only approved change so far. It is a censorship-related measure designed to reduce the ability of a single block builder to exclude transactions.

Why does Ethereum need privacy tools?

Ethereum addresses have visible histories and balances, which can be a problem for payroll, treasury operations and users who do not want to publish financial activity.

When did the deadline for new Hegotá proposals pass?

The deadline for new proposals passed on Aug. 6, leaving developers to narrow the existing list and decide what can realistically be tested and shipped.

Photo by Alesia Kozik on Pexels