What Hegotá would change for wallets
Ethereum’s core developers are weighing 66 improvement proposals for the network’s next major upgrade, Hegotá, and have begun trimming the field to the ones that will actually get built CoinDesk report. Only one change has been formally approved so far — a censorship-resistance measure called FOCIL — while the other 65 will be argued through the coming core developer meetings. The window for submitting new proposals closed on August 6, and Hegotá is slated to follow 2026’s Glamsterdam release and ship in 2027.
The headline item for privacy advocates is a three-part package centered on Frame Transactions, filed as EIP-8141 CoinDesk report. Frame Transactions would let an account set its own rules for how a transaction is approved, executed, and paid for, rather than forcing every user through an identical setup. In practice a wallet could let a third party pay the gas, roll several steps into a single signed action, or swap the approval cryptography without forcing the user to migrate to a fresh account. Two companion proposals handle the congestion that arises when many people transact privately through one account: Keyed Nonces (EIP-8250) would give transactions their own counters rather than a shared queue, so one stuck transaction can’t block the others waiting behind it, and EIP-8272 would let a transaction validate itself against a recent cryptographic checkpoint instead of relying on state that could shift while the transaction sits pending. Ethereum Foundation researcher Toni Wahrstätter co-authored the proposal, and the wider list also weighs faster block production, changed validator rewards, and cryptography built to resist quantum computers.
Why the privacy push matters now
The change matters because Ethereum’s ledger is fully transparent by default: every address keeps a permanent, readable history of balances and activity CoinDesk report. That works for open payments but is awkward for payroll, corporate treasuries, or anyone who would rather not publish their finances. At present those users lean on applications built on top of Ethereum that hide details using cryptographic proofs, but getting those private transactions onto the chain still requires extra infrastructure such as relayers. Ethereum itself would not become private overall — moving ether between two ordinary wallets would still be completely public — so the hiding still happens inside the applications, which would simply need less outside machinery. Ethereum has been folding privacy and quantum readiness into its roadmap Ethereum privacy and quantum roadmap, and the earlier Glamsterdam upgrade already reshaped how blocks are built and executed Glamsterdam upgrade explainer.
What’s already locked in
The one proposal already approved, FOCIL, targets censorship by handing a group of operators a mandatory list of transactions that builders must include, so no single block assembler can quietly drop payments Ethereum Magicians discussion. The Magicians note FOCIL first used a lightweight nonce-and-balance check on excluded transactions, whereas Frame Transactions must run validation code because their sender alone doesn’t reveal the paying account.
