Ethereum researcher Toni Wahrstätter posted on 16 August that 66 separate proposals are now in the running for Hegotá, the upgrade currently pencilled in for 2027. Most of them will not ship. Only one, EIP-7805 (FOCIL), is actually scheduled so far, and it is about censorship resistance rather than confidentiality. But the cluster pulling the attention is the privacy one: EIP-8182, from Facet co-founder Tom Lehman, which would build a protocol-managed shielded pool directly into the chain using a UTXO-style contract and Groth16 proofs over BN254, alongside EIP-8141 and EIP-8250 supplying the plumbing (frame transactions, keyed nonces, recent state roots) that privacy constructs need to work at all.
Strip the numbers off and the sentence is simple. Ethereum is seriously considering making private transfers a base layer feature instead of an app you have to go and find.
That is good news. It is also the single best excuse crypto gaming has been handed in years, and the industry will take it.
TL;DR
- Ethereum devs are narrowing 66 Hegotá proposals for 2027; EIP-8182 would bake a shielded pool into the protocol, with EIP-8141 and EIP-8250 as supporting primitives.
- Privacy and provable fairness answer different questions: privacy hides who, verifiability proves what happened. They are not opposites and they are not substitutes.
- Expect “shielded” to become the new “certified RNG”. Zero-knowledge vocabulary is perfect cover for hiding resolution logic while sounding like more cryptography, not less.
- The test is symmetry: privacy that hides you from everyone including the operator is a feature; privacy that hides the operator from you is the oldest trick in gambling with a new wardrobe.
- Satoshie runs fully public on Base, and that exposure is a genuine cost we pay for verifiability. Any privacy we ever adopt will hide players, never the draw.
Two words that both sound like “trust me”
Privacy and verifiability get discussed as though they are on a slider, and pulling one up drags the other down. They are not on the same axis at all. Verifiability answers “what happened, and could anyone have leaned on it”. Privacy answers “who did it”. A provably fair draw tells you the wheel was straight. It tells you nothing about who was standing at the table.
The reason people conflate them is that public blockchains answered the second question by accident. Nobody chose to publish your losing streak. It fell out of the architecture that also lets you check the result. Confidentiality was the tax, verification was the product, and the industry has spent five years pretending the tax was a principle. A base layer shielded pool splits the two apart properly, which is the genuinely interesting part of Hegotá.
What crypto gaming will do with it
Here is the prediction, on record. Within a month of any native privacy feature shipping, you will read landing pages explaining that game logic runs “in a shielded environment for player protection”, or that outcomes are “computed privately and settled on-chain”. Some of those platforms will be honest. Most will have found a way to describe a closed black box in the language of advanced cryptography.
Zero-knowledge is ideal cover because it inverts the usual smell test. A closed server binary is obviously opaque and everyone knows it. A circuit nobody publishes is opaque with a maths degree, and the audience upgrades its assumption of honesty precisely because the words got harder.
The distinction that survives the marketing is direction. Legitimate privacy hides the player from other players, from chain analysis firms and from anyone watching the mempool, while the outcome proof stays public and checkable by a stranger. Illegitimate privacy hides the resolution from the player while the operator retains full sight of everything, which is not privacy at all. It is an information advantage, and an information advantage in a game of chance has a name: the house edge you cannot measure.
So the rule is symmetry. If a privacy feature hides you from everyone, including the people running the game, it is a feature. If it hides them from you, it is the thing provable fairness was invented to kill.
The cost we currently pay, stated plainly
Satoshie is fully public. Your address, your entries, your wins and your losses sit on Base permanently, readable by anyone with a browser. We have said before that this is the price of verifiable gaming rather than a free lunch, and it is a real price. Leaked customer data has been seeding physical coercion attempts on crypto holders all year. Screening vendors walk the transaction graph backwards through the contract to your funding addresses without asking anybody’s permission. Every winner who posts a screenshot links a public balance to a person.
A protocol-level shielded pool would remove a slice of that without touching a single fairness property, because a Chainlink VRF proof does not care who you are. The coordinator verifies randomness, not identity: that the random word was generated without interference, and that the callback fired with the value it verified. Nothing in that evidence requires your wallet history to be legible to a stranger. That is the version worth wanting.
Why we are not promising it
Satoshie runs on Base, an L2. Hegotá is an L1 upgrade targeted at 2027, and “66 proposals to be narrowed over the coming core dev calls” is engineering-speak for most of these dying. Even the survivors take time to reach rollups, and combining a shielded pool with a VRF request, a stake escrowed in the same transaction and a callback that pays a winner is not a configuration flag. Anyone telling you today what their game will support in 2027 is describing a roadmap, not a product.
What we will commit to is direction rather than delivery. Whatever privacy Satoshie eventually adopts will hide players and never the draw. The randomness proof stays on chain, stays public, and stays checkable by someone who does not work here. If we ever ship a version where you have to take our word for the resolution, we have become the thing we spent two years arguing against, and you should treat it as exactly that.
The unglamorous proposal that matters more
While everyone stares at shielded pools, note again that FOCIL is the only scheduled EIP so far. It lets a committee of validators force pending transactions into blocks, which is a liveness property, and liveness is where gaming actually breaks. A draw you cannot request and a payout that cannot get included are functionally a rigged game, no matter how immaculate the proofs are. Censorship resistance will get a fraction of the coverage that privacy gets, and it is more relevant to whether you get paid.
Two questions to keep in your pocket
When a game starts advertising privacy, ask what exactly is hidden, and ask whether the operator can still see it. If the answer to the second is yes, you have not been given privacy, you have been given a smaller share of the information.
Then ask whether the outcome still arrives with a proof that a stranger can verify without permission. On Satoshie, a coinflip resolves inside the VRF callback with a single modulo, a raffle resolves as keccak256 of the VRF word and the prior blockhash modulo ticketsMinted, and ticketsMinted is readable contract state. That is checkable by anyone, today, without an account and without asking us anything. Privacy that leaves those properties intact is progress. Privacy that quietly replaces them is a downgrade with better branding.
📷 Photo by FlyD (@flyd2069) on Unsplash
