Tom Lehman pushes for EIP 8182 inclusion in Ethereum Hegota upgrade

Lehman, who co-founded the Layer 2 network Facet, argued that Ethereum currently faces a structural problem where privacy pools struggle to gain enough users to create effective anonymity while users avoid joining pools that lack sufficient privacy guarantees.

Under the proposal, Ethereum would deploy the shielded pool as a system contract with no admin key, proxy contract, or pause function. Lehman said the design would follow a fork-managed structure similar to existing Ethereum protocol contracts, meaning future changes could only happen through network upgrades.

At the same time, EIP-8182 would add a zero-knowledge proof verification precompile to Ethereum’s base layer, allowing clients to process private transaction proofs directly at the protocol level. The proposal relies on a UTXO-style architecture and Groth16 BN254 proofs for transaction verification.

Unlike many existing privacy systems, the draft proposal would still let users send funds to normal Ethereum addresses or ENS names. According to Lehman’s design notes, hidden ownership identifiers stored inside registries would manage the private side of the transfer process without forcing users to create separate privacy-specific addresses.

How would EIP-8182 change Ethereum privacy?

Lehman said the proposal is intended to create a single shared anonymity set for the Ethereum ecosystem rather than dividing users across multiple competing privacy pools. The system contract would store the note commitment tree, nullifier set, delivery-key registries, and authorization policy registry in one protocol-managed location.

The draft proposal also outlines support for atomic transaction flows. According to the specification, users could deposit assets into the shielded pool, interact with public smart contracts, and move assets back into private balances within the same sequence.

Meanwhile, Lehman acknowledged that EIP-8182 does not fully solve Ethereum privacy on its own. The proposal notes that complete transaction privacy would still depend on encrypted mempools, network-layer protections, and wallet-level changes that remain outside the EIP’s scope.

Three proposals connected to Ethereum’s privacy infrastructure are now being discussed for the Hegota upgrade cycle. EIP-8141 would let privacy pools pay withdrawal fees using withdrawn assets, while EIP-8250 introduces keyed nonces designed to support shared-sender privacy systems.

Why is Ethereum discussing protocol-level privacy now?

Ethereum developers have increasingly discussed privacy as part of the network’s long-term roadmap ahead of expected institutional adoption and tokenization growth. According to reports, Ethereum Foundation leaders have recently identified compliant privacy systems and faster finality as important priorities for 2026.

Earlier this year, Ethereum developers also added FOCIL, a censorship-resistant mechanism, to the Hegota upgrade roadmap. At the time, Ethereum co-founder Vitalik Buterin described the direction as part of building a more “cypherpunk principled” Ethereum.

Regulatory debates surrounding privacy protocols are also shaping discussions around EIP-8182. Projects such as Privacy Pools have attempted to use zero-knowledge proofs to separate legitimate funds from illicit activity without exposing complete transaction histories.

According to Lehman’s proposal, a shared protocol-level privacy layer could eventually help decentralized finance platforms and tokenized real-world asset systems balance transaction privacy with compliance requirements.