Real-World Use Cases

Where ZK is shipping today:

1. Private Cryptocurrencies:

• Zcash: shield transactions hide sender, receiver, amount. Built on Groth16.
• Monero: ring signatures + Bulletproofs.
• Tornado Cash: mixer (now sanctioned, but technical influence remains).

2. Layer-2 Scaling (zkRollups):

• Roll up thousands of transactions, post one proof + state diff to L1.
• StarkNet, zkSync, Scroll, Polygon zkEVM, Aztec.
• Cheaper L2 transactions; same security as L1.
• Proofs verify in ~5ms; rollup batches generated in minutes.

3. Identity & Credentials:

• "Prove I'm 18+" without revealing DOB.
• "Prove I have valid degree from this list" without revealing university.
• Zero-knowledge KYC: one-time KYC, then prove "yes I'm KYC'd" repeatedly.

4. Voting:

• Prove your vote is valid + counted, without revealing your vote.
• MACI (Minimal Anti-Collusion Infrastructure): bribery-resistant voting.

5. Compliance Without Surveillance:

• "Prove no transaction violates sanctions" without revealing transaction details.
• Proof of solvency for exchanges (Mt. Gox aftermath spawned interest).

6. Authentication:

• Password proof of knowledge (no password sent).
• Biometric matching without sending biometrics.

7. Computation Outsourcing:

• Pay a server to compute X; verify with a tiny proof instead of re-running.
• Verifiable computation (vSQL, etc.).

8. Game Engines:

• "I rolled a 6" proven from committed RNG seed.
• Cheat-resistant on-chain games.

Cost still matters: prover time can be seconds to minutes. Verifier time is ms but throughput limited. Active research: faster provers (GKR, lookup tables, recursion).

ZK is becoming the default privacy + scalability tool for blockchain. Beyond blockchain: still a niche but growing.