Lehman Revives EIP-8182 to Add Protocol-Level Privacy to Ethereum

Tom Lehman, co‑founder of Layer‑2 network Facet, is reviving a push to bake privacy directly into Ethereum’s protocol with EIP‑8182 — a proposal he wants included in the upcoming Hegota upgrade. Why it matters - Today’s privacy tools on Ethereum are fragmented: multiple “shielded pools” compete for users, leaving each pool with a small anonymity set and weak privacy guarantees. Lehman argues this creates a coordination problem that prevents effective privacy at scale. - EIP‑8182 aims to solve that by creating a single, protocol‑managed shielded pool — a shared anonymity set maintained by Ethereum itself rather than by separate apps. What the proposal would add - A shielded pool implemented as a system contract with no admin key, proxy, or pause — changes would only come via network upgrades (fork‑managed, like other protocol contracts). - A base‑layer zero‑knowledge proof verification precompile, so clients can validate private transaction proofs at the protocol level. - A UTXO‑style architecture using Groth16 BN254 proofs for transaction verification. - Hidden ownership identifiers stored in registries so users can make private transfers while still sending to normal Ethereum addresses or ENS names, avoiding the need for separate privacy‑only addresses. - Protocol storage of core privacy primitives (note commitment tree, nullifier set, delivery‑key registries, authorization policy registry) to create a single shared anonymity set. - Support for atomic flows: users could deposit into the shielded pool, interact with public smart contracts, then return assets to private balances within the same transaction sequence. Caveats and limits - Lehman acknowledges EIP‑8182 isn’t a silver bullet. Full privacy depends on complementary pieces outside the EIP’s scope: encrypted mempools, network‑layer protections, and wallet changes. - Regulatory and compliance considerations remain central: projects like Privacy Pools are already exploring ZK techniques to separate legitimate from illicit funds without exposing full histories, and regulators are watching how privacy tech is designed. Context in Hegota and broader roadmap - EIP‑8182 joins other privacy‑adjacent proposals under Hegota consideration, including: - EIP‑8141 — enabling privacy pools to pay withdrawal fees using withdrawn assets. - EIP‑8250 — introducing keyed nonces to support shared‑sender privacy systems. - Ethereum devs and Foundation leadership have flagged compliant privacy and faster finality as priorities for 2026. Earlier this year they also added FOCIL (a censorship‑resistance mechanism) to Hegota; Vitalik Buterin described the overall direction as moving toward a more “cypherpunk principled” Ethereum. Implications - If adopted, a protocol‑level shielded pool could give decentralized finance and tokenized real‑world asset systems a unified privacy primitive that’s easier to audit, maintain, and potentially align with compliance needs. - The proposal still faces technical, social, and regulatory hurdles, but it reframes privacy on Ethereum from isolated application features to a core protocol capability — a shift that could be decisive as institutional use and tokenization grow. Lehman has shared slides and technical notes on the proposal as discussions continue ahead of Hegota’s upgrade cycle.