Ethereum’s Privacy Revolution: How EIP-8182, pERC-20, and STRK20 Are Building a Compliant Confidentiality Layer

A key architectural choice is the shared anonymity set. Because the shielded pool is a single, protocol-wide system, every wallet that integrates the standard automatically strengthens the anonymity set for every other user . This contrasts sharply with the fragmented privacy landscape of the past, where isolated pools made anonymity much weaker. To prevent double-spending within the pool, the system employs a shared note tree and a nullifier set .

pERC-20 (ERC-7605): A Privacy-Native Token Standard

While EIP-8182 targets the transaction layer, the pERC-20 proposal—formally tracked as ERC-7605—redefines what a token is. The central idea is simple but radical: in a pERC-20 world, there is no public balanceOf or transferFrom function. Instead, balances exist as encrypted cryptographic notes, and the sender, receiver, and amount of every transfer are hidden by default .

The architecture draws heavily on Zcash’s Orchard protocol and ZK-UTXO model, with tokens minted directly into hidden balances that are never exposed in public state . The total supply remains publicly verifiable, creating a crucial audit anchor, but individual holdings and movements are kept private .

Crucially, the standard embeds compliance mechanisms that earlier privacy designs largely ignored. The proposal includes a blacklist capability, giving token issuers a tool to block specific addresses from interacting with the private token pool . This design acknowledges a practical reality: for privacy tooling to achieve mainstream adoption, especially among institutions, it must offer a path for regulatory intervention without collapsing the entire privacy set.

STRK20: Privacy Live on Starknet Today

While EIP-8182 and pERC-20 are in-progress proposals, Starknet’s STRK20 framework is already operational. Announced initially in March 2026 and fully launched on mainnet by June 9, it enables any ERC-20 asset on Starknet to be shielded, transferred, and used in DeFi privately .

The first asset to use the standard is strkBTC, a Bitcoin-backed wrapped token that operates in both a public and a shielded mode . Users can toggle between modes through compatible wallets like Ready X and Xverse . Once shielded, balances and transactions become invisible to external observers, but the token remains fully composable with existing decentralized exchanges and lending protocols like Ekubo and AVNU .

STRK20’s compliance architecture centers on viewing keys. Token holders can grant a viewing key to a specific third party—such as a regulator, auditor, or tax authority—which allows that party to decrypt transaction details while the rest of the world sees nothing . This selective disclosure model aims to resolve the tension that plagued tools like Tornado Cash, where full anonymity made any form of compliance assistance impossible .

A Shared Design Philosophy: Compliant Privacy

Despite operating at different layers of the stack, these three initiatives share a clear design philosophy.

First, privacy is being treated as infrastructure, not a feature. EIP-8182 embeds it at the consensus layer. pERC-20 embeds it at the token interface. STRK20 embeds it at the L2 token contract. In all three cases, privacy is not a wrapper around existing transparent systems—it is the default state.

Second, compliance is a first-class design goal, not an afterthought. pERC-20 includes a blacklist. STRK20 includes viewing keys. EIP-8182’s nullifier set prevents double-spending within a private pool, maintaining integrity without deanonymizing users. This marks a sharp evolution from earlier privacy projects, which often treated regulatory compatibility as optional or antithetical.

The convergence is striking. It suggests that the Ethereum developer community has largely settled on a new consensus: financial privacy is essential for the network’s long-term health, but it must be architected with controlled disclosure pathways. The goal is not lawless anonymity. It is confidentiality that respects the real-world obligations of institutions, issuers, and users.

Much of this work remains early. EIP-8182 is still a proposal, and its inclusion in Hegotá is not yet guaranteed. pERC-20 is in draft status and will require extensive review before any potential adoption. STRK20 is the most advanced, live today on Starknet, but its long-term adoption will depend on whether wallets, applications, and users embrace the model.

What is now clear is the direction of travel. The era of fully transparent ledgers as the only acceptable default is being challenged. In its place, a new architecture is taking shape: one where privacy is programmable, compliance is built-in, and confidentiality becomes a standard feature of the Ethereum ecosystem.