Ethereum Hegota adds Frame transactions and privacy to its 2027 roadmap

64 frames: Break down a single Ethereum transaction into a sequence in which the protocol can be executed step by step

This is the MAX_FRAMES parameter proposed in EIP‑8141, which converts a single Ethereum transaction into a sequence in which the protocol can be executed step by step. It marks the arrival of the post-EOA (externally owned account) model: verification, Gas approval, and execution are no longer merged into a single block of data, but are organized frame-by-frame. This design opens up space for native account abstractions, non-traditional signature schemes, and flexible Gas payments, and is the foundation on which the next generation wallet user experience and on-chain privacy can be built. However, although the mechanism exists on paper, the Hegotá upgrade is currently dominated in another direction: mandatory inclusion.

Frame transactions reconstitute a transaction into a maximum of 64 frames

EIP‑8141 defines a new FRAME_TX type that breaks down user actions into discrete frames, each frame has a specific role: the verification frame is used to check intent and authorization, the Gas approval frame is used to resolve who pays and what rules to follow, and the execution frame is used to apply status changes. The proposal sets MAX_FRAMES to 64 and adds a clear cost to each frame, breaking down complex workflows into bounded, measurable steps rather than relying on customized contract workarounds.

The functional benefit lies in the abstraction of native accounts. Frames no longer hard-code EOA models and ECDSA, but instead allow wallets and contracts to specify custom signature schemes, rotate keys, or migrate to quantum-resistant signatures without relying on L2 or third-party repeaters. The Gas payment abstraction has also become a first-class citizen: users can define the policies of who pays and how to pay within the agreement, from the sponsor model to multi-asset rules, all encoded in frames rather than off-chain protocols.

Frames are important for privacy tools because they separate the certification and authorization logic from the writing of state changes. The wallet can verify the zero-knowledge certificate using the scheme of its choice in one frame, approve Gas in another frame, and then submit the private transfer in the execution frame. Protocols are standardized and verifiable orchestrated; application teams do not have to repeatedly build packaging contracts for each new use case.

All of this still needs to be included in the network upgrade. Here, Hegotá's priority is to include before refactoring.

Hegotá's number one feature is mandatory inclusion, not privacy

In a developer update on April 10, 2026, the Ethereum Foundation confirmed that FOCIL (EIP‑7805) is Hegotá's number one feature. The forked option mandatory inclusion list is a consensus and enforcement mechanism designed to ensure timely inclusion of transactions and alleviate constructor-level review that can quietly block transactions out of the chain of norms.

In the same update, the foundation noted that frame trading (EIP‑8141) has been moved to a "considered for inclusion" state, but is not the number one feature. The label means that the protocol team will be committed to this feature, but it has not been elevated to core status. The timetable is uncertain, and so is the timetable for the native account abstraction and wallet-level benefits unlocked by frames.

This ranking stems from basic principles. Inclusion of guarantees is a prerequisite for any serious layer of privacy. If the builder or block producer can suppress or delay transactions indefinitely, private writes will only be private if they are ultimately successfully linked, otherwise they will lose their meaning. By locking in FOCIL, Hegotá aims to strengthen a guarantee that private commits-whether they are blocked transfers or certificate-intensive updates-can actually reach the chain.

Specification blocking transfers on L1 aims to fix fragmented anonymity

Another privacy initiative currently on the Ethereum roadmap is to deploy a single pool of protocol-managed shields through forking. EIP‑8182 proposes a system contract that enables private ETH and ERC‑20-compatible transfers using a split certificate architecture: a pool certificate is used to show that the transfer status is consistent with the blocking status, and a separate certificate of authorization is used to show the spending authority. The goal is to build a pool of specifications on L1, rather than relying on a bunch of application-level currency mixers that consist of small, fragmented anonymous sets. The Ethereum Privacy Roadmap lists EIP‑8182 as a feature considered by Hegotá, alongside frame transactions, and points out that protocol changes alone are not enough to achieve end-to-end privacy.

Privacy relies on a complete chain beyond protocol changes

The roadmap updated on July 27, 2026 breaks down the problem into three outcomes-private reads, private writes, and private attestations-and clearly states that simply introducing new transaction types or system-level pools will not complete the entire puzzle. Multiple complementary layers must be in place at the same time:

Private information retrieval is used for private reads so that the wallet can discover and retrieve relevant data without revealing interest to the server.

Frame transactions plus FOCIL are used to resist censorship submissions, making private writes structured and cannot be excluded indefinitely.

Client-side attestation and zkVM are used for confidentiality semantics, allowing users to generate attestation locally without revealing sensitive details to third parties.

Only when these components are cleanly combined can the user's journey be truly private: discovering the balance without exposing it, preparing the transfer without outsourcing confidentiality, and submitting it under an agreement that can neither guess nor delay the transaction. Hegotá can pave the way for parts of this sequence, but the access layer and proof stack must follow up simultaneously.

This chain of dependence also shapes the user experience of wallets. Frame commitments standardize the expression of authorizations and Gas policies, but developers still need real-life proven libraries to support local attestation creation and efficient circuits, and users need client software that can handle attestation generation within acceptable latency and power consumption. Without these, the specification pool may be just a powerful primitive that few mainstream users can actually use.

Regulatory precedent hangs over the protocol's native shield pool

Compliance is the second constraint. On August 8, 2022, the U.S. Treasury Department's Office of Foreign Assets Control sanctioned the Tornado Cash mixer, setting a reference point for how regulators view privacy and mixed-currency infrastructure. The press release and subsequent prosecutions indicate that tools that enable anonymous transfers of money can lead to law enforcement action.

L1 pools managed through forking are not equivalent to third-party services, but this precedent remains important. Exchanges, wallet providers and infrastructure operators must interpret the risk of sanctions that may restrict or block interactions with native pools, even if the pool is regulated and audited. This not only affects perception, but also affects the actual coverage of private transfers and introduces operational decisions for entities that act as intermediaries between users and Ethereum.

Hegotá's ordering is clear: mandatory inclusion is locked, while frame-based transaction reconstructions are in a "considered inclusion" state. Ethereum may be able to ensure that private writes are not censored before decomposing and authorizing transactions at the native level (through new transaction types). Whether a shielded pool managed through forking can achieve actual privacy depends on this sequencing-and whether non-protocol components such as PIR and client certificates are in place in a timely manner.