ERC-8065 Zero-knowledge token privacy wrapper (Zero Knowledge Token Wrapper)

Draft · Tokens · created 2025-10-18

This standard lets anyone wrap existing tokens such as ERC-20, ERC-721, ERC-1155, and ERC-6909 to add privacy features. This function breaks traceability through provable burn-and-remint.

Why it is needed

Most tokens lack privacy features due to regulation, technical limitations, or issuer indifference. Users who want privacy must rely on dedicated privacy blockchains or privacy-specific dApps, which reduces the token's usability and harms composability with the existing ecosystem. In addition, the range of supported token types is often limited, and whitelisting is frequently enforced or the privacy method itself is constrained. In the end, users have no way to add privacy while continuing to use the tokens they already hold, and their fund flows and holdings remain traceable by anyone.

What to implement

In depth

Wrapping and commitment-based privacy layer

ZWToken adds a commitment-based privacy layer on top of the original token standard without modifying it. The commitment mechanism can be implemented with Merkle trees, cryptographic accumulators, or other verifiable cryptographic structures. ZWToken preserves the original token's properties such as transferability, tradability, and composability while maintaining interoperability with existing Ethereum infrastructure.

Provably burned address

The burn address to which ZWToken is sent must be provably unmanipulable by any user and must be provably unrelated to any externally owned account (EOA) or smart contract. This address can only be derived by its originator, for example through a signature-based or deterministic generation method. Once ZWToken is sent to such an address, it becomes eligible to be reminted via the remint interface, and in this process the traceability of the fund flow is broken.

Privacy differences between FTs and NFTs

Fungible tokens (FTs) such as ERC-20 can break fund-flow traceability through the burn-and-remint process. Non-fungible tokens (NFTs) such as ERC-721, on the other hand, are each unique and cannot participate in coin mixing, so the traceability of the fund flow itself cannot be broken. However, using a provably burned address can still hide the actual owner until the holder performs a withdrawal.

deposit and withdraw

deposit has the caller transfer the original token (or ETH) to the contract and then mints ZWToken to the specified address; the minted amount may be reduced by fees, and a Deposited event must be emitted on success. withdraw does the reverse, burning ZWToken and returning the original token while emitting a Withdrawn event. For tokens without an id, such as ERC-20, the id value must always be set to 0.

remint and nullifiers

remint takes a RemintData struct (commitment, nullifiers, proverData, relayerData, redeem, proof) and uses a zero-knowledge proof to verify ownership of the burn address and the correctness of public inputs such as to, id, and amount. The provided commitment must exist, and the nullifiers must not have been used before; the transaction must revert if they are reused. Multiple nullifiers can be included in a single proof to enable batch remints. If redeem is false, ZWToken is minted; if true, the original token is withdrawn directly; in both cases a Reminted event is emitted.

Two commitment schemes

Contract-level commitments have the contract directly manage the Merkle root and similar data, which simplifies the proof circuit and makes proof generation possible even in a browser or on mobile, but costs more gas per transfer. Protocol-level commitments use Ethereum's native MPT state root or block hash directly, which carries no on-chain maintenance cost, but makes off-chain proof generation more complex.

Reissuance via relayer

remint supports a structure in which a third-party relayer submits the transaction on the user's behalf and receives a fee. This is designed to mitigate the privacy leak that occurs when paying gas directly, which exposes the original sender's address. The fee structure and the encoding of proverData and relayerData are both implementation-dependent and are not defined directly by this standard.

Proposal status

This ERC is currently in Draft status, not yet finalized, and its contents may change or the proposal may be discontinued.

Things to watch out for

Original ERC · ← ERCs