Every transaction on a public blockchain is permanently recorded and visible to anyone. Wallet addresses are pseudonymous — they are strings of alphanumeric characters with no obligatory link to a real identity — but pseudonymity is not anonymity. Governments and blockchain analytics firms have developed increasingly sophisticated methods for tracing transaction chains and linking addresses to individuals. Mixers exist to complicate that process.

A mixer is an application that breaks the chain of custody between a sender’s wallet and a recipient’s. In a basic smart-contract-based mixer, a user deposits funds from one address into a contract pool, then withdraws the same amount to a different address. The connection between deposit and withdrawal is obscured — the output wallet has no traceable relationship to the input wallet. To improve effectiveness, mixers typically require deposits in standardized denominations and depend on a sufficient number of concurrent users to create a large enough pool that individual transactions cannot be easily disentangled.

The mathematics underlying zero-knowledge proofs has been understood since the 1980s. The computational cost of generating and verifying them was, for most of that period, prohibitive for practical applications at scale. What changed over the past several years was not the theory but the engineering: proof generation times dropped by orders of magnitude, hardware acceleration made ZK computation economically viable, and a generation of cryptographers trained in both theory and systems engineering turned their attention to making the technology work in production.

Every major blockchain application eventually collides with an identity problem. DeFi lending protocols that want to offer uncollateralized loans need to assess creditworthiness without holding custody of user data. DAO governance systems that want to prevent sybil attacks — one person controlling many wallets to accumulate disproportionate voting power — need to verify personhood without requiring real names. Regulatory compliance frameworks that require KYC create friction that is incompatible with the permissionless design of public blockchains.