Ethereum Core Developers Prioritize Protocol-Level Privacy for Hegotá Upgrade

The batch, currently under technical review, pushes privacy primitives down to the protocol layer rather than leaving them to application-level workarounds.

What the proposals actually change

The core mechanism under review is EIP-8141, "Frame Transactions." It decouples gas payment from the originating account. A privacy pool can settle its own transaction fees without an external relayer touching the transaction. The attack surface shrinks: every intermediary in the current pipeline — the relayer that submits the tx, the RPC node that broadcasts it — is a metadata leak. Removing that hop eliminates a deterministic correlation vector between sender and submitter.

EIP-8182 proposes a native shared shielded pool for ETH and ERC-20 transfers. Users prove compliance to a regulator without disclosing the full transaction graph. EIP-8250 introduces keyed nonces to break transaction correlation when parallel private sequences run. Without keyed nonces, sequential nonce values themselves form a fingerprint that links a user's private transactions.

EIP-7805, FOCIL (Fork-Choice Enforced Inclusion Lists), is the single EIP confirmed for Hegotá so far. It forces validators to honor pending transactions, closing a censorship channel where block builders selectively exclude operations.

Constraints and execution risk

Scope is not locked. Toni Wahrstätter, an Ethereum Foundation contributor, outlined the privacy case in a Sunday X post arguing multiple mechanisms are required to deliver protocol-level privacy without routing around the base layer. The remaining EIPs face months of security review, specification refinement, and client implementation work before they ship.

Timing leaves a narrow window. Glamsterdam, Ethereum's prior major upgrade, is expected to mainnet in the second half of 2026 per the public roadmap. Hegotá targets 2027. That puts roughly one upgrade cycle between Glamsterdam's delivery and any new privacy primitives landing at the protocol level.

What to watch

Build-level teams building on or integrating privacy pools should track two signals. First, which EIPs survive the next core developer call — scheduled for Monday at 2:00 pm UTC — and advance from the 66-proposal backlog into scoped inclusion. Second, whether EIP-8141's frame-based gas model holds under adversarial review: any abstraction layer that lifts fee payment from the EOA introduces new assumptions about replay protection, signature schemes, and mempool economics. Until those are formalized, assume current relayer-based privacy pool architecture remains the production default.