Author Tom Lehman has officially proposed EIP-8182, which introduces private ETH and ERC-20 transfers directly into the Ethereum protocol. The proposal is currently in the "Draft" status.
Core Idea
Today, nearly every transaction on Ethereum is public - you can track the transfer amount, sender address, and recipient address. EIP-8182 aims to change this by creating a built-in mechanism for private transfers without relying on third-party applications.
Key Elements of the Proposal
· Shared Shielded Pool. A global custody system operating as a system-level smart contract at a fixed address (similar to EIP-4788). It manages all private notes, the note commitment tree, nullifier set, and user registries.
· ZK Precompilation. A special function added to the protocol for efficient zero-knowledge proof (ZKP) verification, allowing private transfer validity to be confirmed without revealing transaction details.
· No Administrative Keys. The system contract has no on-chain upgrade mechanisms, is not governed by multisigs, DAOs, or tokens. Any changes can only be made through an Ethereum hard fork.
· Atomic Flows. Users can de-anonymize funds (withdraw from the pool), interact with any public smart contract (e.g., swap tokens on a DEX), and re-shield the result - all within a single transaction.
Why This Matters Now
The problem with existing privacy solutions (separate protocols and mixers) is the "chicken and egg" problem. A new service cannot offer anonymity to its first users because privacy requires a large user base, but without privacy, no one wants to join first. As a result, anonymity remains fragmented - in 2025, fewer than 1 in 10,000 Ethereum transactions were private.
EIP-8182 solves this by embedding a single pool at the protocol level. Any wallet or application can use it "out of the box," and every new user strengthens privacy for everyone else.
Limitations and Modest Goals
The authors clearly state what EIP-8182 does not solve:
· Mempool encryption: Transactions awaiting confirmation are still visible to validators.
· Network‑level anonymity: Protection against IP address analysis.
· Changes to wallet interfaces: These would still be required for a smooth experience with private transfers.
Thus, the proposed solution addresses only part of the privacy problem - but does so at the most fundamental level.
Status and Prospects
It is important to understand that EIP-8182 is at the very earliest stage of the Ethereum improvement proposal process.
1. EIP Lifecycle. Draft → Review → Last Call → Final. Currently, the document has not even been submitted to core developers for consideration.
2. Open questions. On the Ethereum Magicians forum, technical details are already being discussed:
· How lightweight should the precompilation be to avoid overloading the protocol?
· How to solve state growth issues caused by storing notes and nullifiers?
· How to compensate for gas fees in private transfers?
3. Timelines. Even if the EIP is accepted, implementation will require at least one hard fork. In 2026, the Glamsterdam upgrade is expected (primarily focused on scaling to 10,000 TPS), and EIP-8182 will most likely not be included.
Conclusion
EIP-8182 is an ambitious attempt to move privacy from the category of "optional applications" to a "core property" of Ethereum. If implemented, any user could send funds confidentially using a regular ENS address and a standard wallet.
However, the current "Draft" status means that implementation could take years, and the proposal may be rejected or radically changed during the discussion process. Nonetheless, raising this issue at the core protocol level is an important signal that Ethereum is considering privacy an integral part of its 2026 roadmap, especially in the context of growing institutional investment and real‑world asset tokenization.