WuBlockchain
EIP-8182, a proposal to add native privacy transfers to Ethereum at the L1 protocol layer, has formally entered Proposed for Inclusion (PFI) for the upcoming Hegotá hard fork. Developer Tom Lehman announced the milestone on X after the spec cleared its draft stage and was filed for core-developer review.
Why it matters
The proposal introduces optional, protocol-fee-free privacy transfers for ETH and compatible ERC-20s via a system contract and a split-proof architecture. Unlike Tornado Cash or rail-based mixers, EIP-8182 is meant to live inside the protocol itself — meaning compliance-relevant visibility is preserved by design rather than bolted on at the application layer.
Market impact
A protocol-level privacy primitive has been a recurring ask from institutions weighing on-chain settlement. If Hegotá ships with EIP-8182 included, it removes the single largest piece of regulatory ambiguity that has kept bank-grade money sitting on private chains and consortium L2s. The next gate is All Core Developers sign-off on the hard fork scope; until then, the proposal can still be deferred to a later fork.
Source: [EIP-8182: Private ETH and ERC-20 Transfers [DRAFT] — Ethereum Improvement Proposals](https://eips.ethereum.org/EIPS/eip-8182)
Frequently asked questions
-
What does EIP-8182 actually do?
It introduces optional, protocol-fee-free privacy transfers for ETH and compatible ERC-20 tokens directly at the Ethereum L1, using a system contract and a split-proof architecture instead of an application-layer mixer.
-
How is this different from Tornado Cash?
Tornado Cash is an app-level mixer that attracted OFAC sanctions. EIP-8182 bakes privacy into the Ethereum protocol itself with compliance-relevant visibility preserved by design, shifting the legal question from 'is mixing illegal' to 'does this transfer meet protocol-level disclosure rules.'
-
When would EIP-8182 ship?
It has entered Proposed for Inclusion in the Hegotá hard fork. It still needs All Core Developers sign-off on the fork scope and can be deferred to a later upgrade if reviewers push back.
-
Why does native privacy matter for institutions?
Banks and asset managers have repeatedly cited the lack of a compliant on-chain privacy layer as the reason they settle on private chains and consortium L2s. A protocol-level primitive removes that constraint at the base layer.
-
Who is behind EIP-8182?
Developer Tom Lehman authored the spec and announced the PFI milestone on X. The proposal is now in core-developer review ahead of the Hegotá fork scope decision.
CoinTelegraph
CryptoSlate
Benjamin Cowen
CoinDesk
TheBlock