Core building blocks that add privacy to Ethereum. 🌀 Mixers 🕵️ Stealth Addresses 🛡️ Shielded Pools 🔒 Zero-Knowledge Proofs (ZKPs) 🧅 Mixnets 🧮 Private data & compute Mix for best results 🧑🍳
🌀 Anonymity pools A pool obscures links between senders and receivers. Observers can see who interacts with the pool but can't easily tell which deposit belongs to which withdrawal. Mixers break the link between a single deposit and withdrawal. Shielded pools let you keep a private balance and move funds inside the pool without the need to withdraw. Examples: @TornadoCash, @0xprivacypools, @RAILGUN_Project
🕵️ Stealth addresses Every payment you receive uses a fresh, one-time address. Observers can not see which addresses are connected, except you. You can see, and spend all those funds just like any other balance from your main wallet. Examples: @UmbraCash, @fluidkey (ERC-5564/6538)
🔒 Zero-knowledge proofs (ZKPs) Zero knowledge proofs let you prove a claim is true (e.g. "I am over 18") without revealing the underlying information (e.g. your birthday). They allow for selective disclosure that enables privacy-preserving facts about identity, credentials, compliance, or verifiable claims about execution. Examples: @ZKPassport, @zkemail, @EIP7503, @Rarimo_protocol (EIP-7812)
🧅 Mixnets Route traffic through multiple hops with layered encryption and packet mixing to hide who talks to whom and when. They reduce metadata leakage before a transaction hits the chain and make it harder to link your device to a specific transaction or RPC call. Examples: @nym, @hoprnet, @torproject @Waku_org
🧮 Private data & compute Private compute with public, verifiable outcomes. It lets apps run programs using private, sensitive information without exposing it, while the results stay publicly verifiable on chain. Examples: @aztecnetwork, @fhenix, @EnclaveE3, @ShutterNetwork