TECHNOLOGIES

Zero-Knowledge

Zero-Knowledge Proof (ZK)

A cryptographic technique that proves a statement is true without revealing the data behind it.

Last reviewed: 2026-05-24 byKevin Riedl wiki β†—

A zero-knowledge proof lets one party (the prover) convince another (the verifier) that they know some piece of information, without disclosing the information itself. The canonical example: prove that you are over 18 without revealing your date of birth.

In production, ZK shows up in two flavors. ZK-SNARKs are smaller and faster to verify but require a trusted setup. ZK-STARKs are larger and slower but need no trusted setup and are post-quantum safe. Most chains now offer pre-built circuits for common proofs (identity, balance, voting eligibility) so you do not need a cryptographer on staff.

The business case is narrower than the hype: ZK is genuinely valuable when you need to prove a property on-chain (or to a counterparty) without leaking the data. It is overkill for most consumer apps.

// FAQ

FAQs

FAQs

When you need to prove a property to a counterparty (regulator, chain, partner) without leaking the underlying data: KYC status, balance threshold, voting eligibility, age, accreditation. If the proof can be replaced with a trusted database query, ZK is overkill.
SNARKs: smaller proofs, faster verification, trusted-setup requirement, more mature tooling. STARKs: larger proofs, slower verification, no trusted setup, post-quantum safe. For most production cases today, pick the one your target chain supports best, not the one with the better whitepaper.
Circuit bugs (the proof verifies correctly but proves the wrong thing), trusted-setup compromises, and prover-side performance walls when the input size grows. The cryptography is sound; the engineering around it is where most teams ship vulnerabilities.