Skip to main content
Important: We do not provide financial advice or custody funds. All transactions occur on third-party platforms.
CryptoBipto
Log in

ZK-Proof Primer for Users

A user-facing primer on zero-knowledge proofs: what they actually are, the three properties, the SNARK vs STARK distinction, the ZK-EVM Type 1-4 framework, and where you will encounter ZK in everyday crypto use.

20 min · expert · part of Advanced Concepts

What Is a Zero-Knowledge Proof, In Plain Language?

A zero-knowledge proof is a mathematical procedure where one party (the "prover") convinces another party (the "verifier") that a statement is true, without revealing why it is true. The verifier learns only the truth of the statement; the prover keeps the underlying information secret. A favorite illustrative example is the "Where's Waldo" problem. Suppose you want to prove to a friend that you can find Waldo on a crowded page without revealing his location. You take a large piece of cardboard with a tiny hole in it, place it over the page, and align the hole over Waldo. Your friend sees Waldo through the hole and is convinced you found him, but does not know where on the page he was. You proved knowledge without leaking it. This is exactly what cryptographic ZK proofs do, generalized to arbitrary computations. Instead of proving "I know where Waldo is," you can prove "I know the inputs to a computation that produced this output," "I know a private key that signs this message," "I correctly executed this batch of 1,000 transactions," or "I am over 18 years old without revealing my date of birth." The prover holds private information; the verifier learns only that the claim is true. For users, ZK proofs matter because they enable two large categories of capabilities. First, scalability: rollups can prove that thousands of transactions executed correctly with a single small proof, dramatically increasing blockchain throughput. Second, privacy: you can prove things about yourself or your transactions without revealing the underlying data. The rest of this lesson explains how these capabilities work in practice.

Also in this lesson

  • The Three Properties: Completeness, Soundness, Zero-Knowledge
  • ZK Rollups: zkSync, StarkNet, Linea, Scroll
  • ZK-EVM Type 1-4: Vitalik's Framework
  • zk-SNARKs vs zk-STARKs and Trusted Setup
  • Where Users Encounter ZK in Everyday Crypto
  • The Future: ZK Verification, Identity, AI
  • For Deeper Reading

Key terms

Zero-Knowledge Proof
A cryptographic procedure where a prover convinces a verifier that a statement is true without revealing the underlying information. Three properties: completeness, soundness, zero-knowledge.
Completeness, Soundness, Zero-Knowledge
The three properties defining a valid ZK proof. Completeness: honest provers always succeed. Soundness: cheating provers fail with overwhelming probability. Zero-knowledge: verifiers learn nothing beyond the truth.
zk-SNARK
Succinct Non-Interactive Argument of Knowledge. Small proofs (~few hundred bytes), fast verification (~milliseconds). Often requires trusted setup; not post-quantum secure. Constructions: Groth16, Plonk, Halo 2, Plonky2.
zk-STARK
Scalable Transparent Argument of Knowledge. Larger proofs (tens of KB) but no trusted setup and post-quantum secure. Used by StarkNet via Cairo. Original construction by Eli Ben-Sasson et al. 2018.
Trusted Setup
A one-time cryptographic ceremony to generate parameters for some SNARK constructions. Powers of Tau is the canonical multi-party version. Halo 2 (Zcash 2022) eliminated trusted setup for SNARKs.
ZK-EVM Type 1
Fully Ethereum-equivalent zkEVM — proves the exact EVM with no modifications. Maximum compatibility, highest proving cost. Taiko is closest to Type 1 in 2026; Linea has roadmapped it.
ZK-EVM Type 2
EVM-equivalent zkEVM with internal modifications for proving efficiency. Every existing contract works without changes. Scroll is the canonical Type 2; Linea launched as Type 2.
ZK-EVM Type 3
Almost-EVM-equivalent zkEVM with targeted compromises on hard-to-prove opcodes. Most contracts work; some need adjustments. Polygon zkEVM was Type 3.
ZK-EVM Type 4
High-level-language equivalent zkEVM — Solidity is compiled to ZK-friendly representation, not running EVM bytecode. zkSync Era and StarkNet (via Cairo) exemplify this.
Cairo
StarkWare's programming language for STARK-friendly computation. StarkNet uses Cairo natively. Solidity-to-Cairo transpilation via warp tooling enables EVM-style code on StarkNet.
Halo 2 (Zcash 2022)
SNARK construction that eliminates trusted setup by using a different polynomial commitment scheme. Adopted by Zcash and Aztec. Major advance in SNARK efficiency without setup ceremony.
ZK Hardware Acceleration
ASIC ZK provers (Cysic, Ingonyama, Ulvetanna) achieve 10x-100x speedup over CPU/GPU. Rapidly maturing in 2024-2026. Lowers proof costs and improves rollup finality.

Continue this lesson — 7 more sections in the CryptoBipto app.

Open lesson

Educational only — not financial advice.