Ethereum's Hegotá upgrade: 66 proposals, one privacy question

On 16 August 2026, Cointelegraph reported that Ethereum core developers are winnowing 66 proposals tied to the network's next major upgrade, branded Hegotá, with the stated objective of making applications on the chain more private and more resistant to outside censorship. The framing is deliberately soft: "native privacy for Ethereum applications" is the line developers are testing in public. The mechanics underneath that line are still being argued over.

Hegotá is being positioned as the next inflection point after a year in which Ethereum has talked less about throughput and more about what its blocks actually contain and who can read them. The 66-proposal field reflects the usual Ethereum process: competing Ethereum Improvement Proposals (EIPs) and broader research write-ups, drafted across client implementations and research teams, each carrying a different theory of how privacy should be added without breaking composability or inviting regulator pushback. The narrowing now underway is the moment the loudest ideas get cut.

From scaling to silence

For most of the last cycle, the Ethereum roadmap read as a scaling story. That frame has been quietly retired in the developer literature. The current public message is about selective disclosure: transactions that settle on a public chain but reveal only what the participants choose to reveal, to the parties they choose to reveal it to.

The list of approaches under consideration, judging by the volume of proposals, is broad. Some submissions extend zero-knowledge rollup designs that already let users transact inside a shielded pool. Others propose new primitives at the base layer: encrypted mempools that obscure the contents of pending transactions until they are ordered; viewing keys that let a user prove specific facts about their history to a counterparty without dumping the whole address; account abstraction upgrades that let a wallet prove solvency or accreditation without linking back to a known identity. Each route carries different trade-offs in trust assumptions, hardware requirements, and the degree to which validators can still see what they are validating.

The 66-proposal figure is not, on its own, a measure of how close any of these ideas are to shipping. Ethereum upgrades have historically consolidated dozens of research ideas into a smaller number of included EIPs before mainnet activation. The number matters mainly as a signal of how seriously the developer community is treating the brief.

What "private" actually defends against

The honest argument for native privacy is not that users have something to hide. It is that public-by-default blockchains leak information in ways that change behaviour. Address linkage lets analytics firms cluster wallets; clustering lets anyone with a subscription trace donations, salaries, treasury holdings and trading strategies. Front-running bots read the mempool for profitable trades; sandwich attacks cost ordinary users basis points on every large swap. Censorship resistance, in this framing, is not only about governments blocking transactions, but about any well-capitalised observer being able to see them coming.

The counter-read is also worth taking seriously. Regulators in the European Union, the United States and parts of Asia have spent two years pushing for traceability on exactly the tooling that privacy upgrades would dilute. A default-private Ethereum is, in their reading, a compliance headache with a developer logo on it. Several of the 66 proposals explicitly try to thread this needle by preserving optional auditability: viewing keys for tax authorities, selective disclosure for regulated entities, attestations that a transaction came from a non-sanctioned address. Whether those concessions satisfy either camp is the open political question the technical narrowing will not, on its own, settle.

The structural read

Monexus analysis: the more revealing shift is what the upgrade pitch says about Ethereum's centre of gravity. Two years ago, the dominant developer narrative was throughput: rollups, danksharding, layer-2 settlement. The current pitch is closer to a public-goods argument. Privacy and censorship resistance are pitched as properties the network either has or does not have, independent of how many transactions per second it processes. That is a softer sell to enterprise clients and a harder sell to retail traders, who tend to care about fees and speed. It is also the framing most likely to survive contact with regulators, because it puts the network on the side of the user rather than the side of the surveillance economy.

A secondary structural point: the proposal field is wide precisely because there is no consensus on which privacy primitive is correct. Zero-knowledge systems have matured faster than expected, but their integration into a live settlement layer is non-trivial. Encrypted mempools have raised concerns about validator complexity. Viewing-key designs have raised concerns about key management and recovery. The narrowing process will reveal not just which ideas are technically sound, but which ones the client teams are willing to ship, maintain and defend at a hard fork.

Stakes and what to watch next

If Hegota delivers a credible default-private experience without breaking composability, the network's pitch to payments, payroll and identity use cases strengthens considerably. If the upgrade ships as a compliance-friendly compromise that adds friction for ordinary users while not satisfying regulators, the credibility cost is real: Ethereum will have spent a year telling the market it was the privacy chain, and arrived with optional privacy tucked behind a settings menu.

Two concrete watchpoints. First, the composition of the final included proposals, which will signal whether the client teams have converged on a single privacy primitive or are shipping a portfolio. Second, the public posture of major staking and infrastructure providers, whose compliance departments will be the first to declare whether the upgrade is deployable in their environments. Both data points are likely to land before the next scheduled developer call.

Desk note: Cointelegraph framed Hegotá as a privacy upgrade aimed at making Ethereum applications more resistant to censorship; this article extends that framing into the regulatory and structural arguments the original reporting does not address, and flags what the available source items do not specify about which proposals will survive the narrowing process.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://cointelegraph.com/news/ethereum-devs-66-proposals-hegota-upgrade
• https://t.me/Cointelegraph/71645
• https://t.me/cointelegraph/71645
• https://t.me/Cointelegraph/71635
• https://t.me/cointelegraph/71635