Ethereum developers are evaluating EIP-8182, a draft proposal that would introduce native privacy transfers for ETH and compatible ERC-20 tokens through the planned Hegotá hard fork. If accepted, the proposal would create a protocol-managed shielded pool that allows users to send assets without publicly exposing sender, recipient and amount details in the same way as ordinary Ethereum transfers.
The proposal was authored by Tom Lehman, co-founder of Facet, and created on March 3, 2026. It is classified as a Draft Standards Track Core EIP, meaning it proposes a change to Ethereum’s protocol but has not yet been finalized or scheduled for inclusion. Hegotá, Ethereum’s planned upgrade after Glamsterdam, is expected to focus on infrastructure and protocol-level improvements, with candidate EIPs still subject to debate among core developers and the wider community.
EIP-8182 aims to address one of Ethereum’s long-running weaknesses: the lack of a shared default privacy layer for everyday payments. Today, ETH and token transfers are public by design. Anyone can inspect wallet balances, counterparties and transaction histories. While that transparency supports auditability and open finance, it also makes common use cases such as payroll, donations, treasury management and personal transfers difficult to conduct privately on the base layer.
A shared privacy pool
The core idea behind EIP-8182 is to create a canonical shielded-pool system contract at the protocol level. Users would be able to deposit ETH or compatible ERC-20 tokens into the pool and later spend notes using zero-knowledge proofs. The system would rely on a UTXO-based note model rather than Ethereum’s normal account-balance model, allowing transfers to be validated without revealing the full transaction graph.
The proposal uses a split-proof architecture. A fork-managed pool proof would verify the validity of shielded transfers, while separate authorization proofs would allow users to choose different authentication methods, such as ECDSA signatures or passkeys. The design also includes a private authentication-policy registry, hidden owner identifiers and proof-free deposits.
Importantly, EIP-8182 does not propose a new transaction type, opcode or precompile. Instead, it would install a system contract at fork activation. The proposal also avoids an admin-controlled upgrade mechanism or pause function, meaning changes to the pool would need to occur through Ethereum’s hard-fork governance process rather than through a privileged contract owner.
That design is intended to solve a problem faced by app-layer privacy tools. Smaller privacy pools offer weaker anonymity, while upgradeable pools can introduce governance and custody risks. A protocol-managed shared pool could provide a larger anonymity set and reduce reliance on fragmented privacy applications.
Privacy returns to Ethereum’s roadmap
The proposal comes as privacy has returned to the center of Ethereum’s roadmap debate. Public blockchains expose more financial information than traditional banking systems, creating risks for users, companies and institutions. At the same time, privacy features face intense regulatory scrutiny because they can be misused to obscure illicit fund flows.
EIP-8182 tries to separate protocol-level privacy from compliance decisions. The EIP notes that end-to-end privacy would still require supporting infrastructure, including wallet integration, note delivery, mempool protection and network-layer privacy. Compliance tools would likely develop outside the base protocol, rather than being hard-coded into the shielded pool.
If included in Hegotá, EIP-8182 would represent one of Ethereum’s most significant privacy upgrades. It could make private payments a standard wallet feature instead of a niche application, while giving developers a common base layer for privacy-preserving financial products.
The proposal remains early. Core developers must still evaluate its cryptographic assumptions, state growth, denial-of-service risks, wallet requirements, regulatory implications and compatibility with Ethereum’s broader roadmap. Its inclusion is not guaranteed.
Still, the proposal is important because it reframes privacy as shared public infrastructure rather than an optional application layer. If Ethereum adopts EIP-8182, it would mark a major shift in how the network balances transparency, usability and financial confidentiality.
