The EIP-8182 provides native private transfers for the Ethereum protocol

TLDR

The EIP-8182 provides a shared protection pool built directly into Ethereum as a native system contract.

Less than 1 in 10,000 Ethereum transactions were private in 2025, still below the 2020 peak.

The pool has no admin key or admin token and will only update through Ethereum's hard fork process.

Users can exchange tokens on the DEX and withdraw funds in a single transaction while keeping their identities private.

EIP-8182 is a draft proposal that could bring private transfers directly to the Ethereum protocol. Currently, every Ethereum transaction is completely public, exposing balances, payment amounts, and collateral.

The proposal aims to solve this problem by incorporating a pool of mutual protection into Ethereum itself. Fewer than 1 in 10,000 Ethereum transactions were private in 2025, remaining below 2020 levels.

A major problem with Ethereum's current privacy landscape

Privacy solutions on Ethereum face a structural challenge known as the chicken-and-egg problem of anonymity.

Privacy on Ethereum works by pooling funds together, making it difficult to trace individual transactions. Large pools provide strong privacy for all users. Small, compartmentalized pools undermine privacy on board.

New privacy applications may not provide meaningful privacy to existing users. Without enough privacy, new users have little reason to join.

Once the pool grows large enough, users are reluctant to leave even for a better product because migration reduces privacy protections.

This dynamic means that the largest pool tends to dominate regardless of quality. More competing apps mean smaller private pools and worse results for users overall. So the common standard is missing from the ecosystem.

A second problem compounds this: application-level privacy systems require update mechanisms controlled by specific entities – multi-sig holders, token holders or DAOs. Public transfers on Ethereum do not have such a trust requirement, and private transfers cannot default either.

EIP-8182 how to solve these structural issues

EIP-8182 puts the shared protection pool directly into Ethereum as a system contract at a fixed address. It also introduced ZK authentication precompile. The pool lacks an admin key, admin token, and on-chain upgrade mechanism.

In the year In April 2025, Ethereum founder Vitalik Buterin called for privacy tools to be built into existing wallets. He wrote: “Wallets should have a shielded balance attitude, and when you send to someone else there should be a ‘send from shielded balance' option, ideally enabled by default. A year later, that integration is not available at scale.”

Any wallet that integrates the EIP-8182 connects to a shared anonymous pool. Each new user reinforces privacy for all existing participants. Apps can compete on user experience, validation speed, and developer tools rather than a pool.

The pool is only created through Ethereum's hard-fork process – the same mechanism that governs all other protocol changes. This eliminates the need to trust any third party updates.

Developers can build using EIP-8182

Recipients use standard Ethereum addresses and ENS names. No special privacy-sensitive address format is required and no off-chain coordination step is required. A recipient registers once, and the individual then sends work to the same address.

EIP-8182 Separates transaction authorization from credential generation. Users sign transaction details in an existing wallet and can optionally send them to a remote prover.

As the proposal puts it, “the model has the power to calculate but not the power to determine,” meaning that changed transaction parameters fail to validate.

Private funds can leave the pool and interact with and return to any public Ethereum smart contract – all in a single transaction.

This pattern supports exchanging one token for another on a decentralized exchange while keeping the user's identity and destination confidential.

EIP-8182 is currently in the draft stage. The proposal is open for review at eip8182.com, where a full specification and reference application is also available.