PLONK and the PLONKish family
Pairing-based SNARK, universal SRS
PLONK and the PLONKish family: Pairing-based SNARK, universal SRS. Setup: Universal, updatable. Proof size: Sub-kilobyte. On-chain verification: Practical; above Groth16. PQ: No. Recursion: Well-exercised. Maturity: Production; most common deployed family. Prover cost profile: 256-bit-field FFTs dominate; custom gates and lookups trade prover work for constraint count. Peak prover memory: SRS and witness polynomials resident; comparable to Groth16 at equal size. Off-chain verifier: Milliseconds. Implementations and maintainers: Barretenberg / UltraHonk (Aztec), gnark (Consensys), plonky2 (Polygon Zero lineage), Kimchi (o1Labs), Halo2 forks. Where it is measured: Vendor-published only; no neutral cross-implementation suite. Choose it when: General-purpose circuits where churn is expected and a per-circuit ceremony would be painful, and where on-chain verification is required but need not be absolutely minimal.
What it is
A permutation-argument-based universal SNARK over a custom-gate arithmetisation — selector columns, copy constraints, optional lookup columns. One SRS serves all circuits up to a size bound. The most frequently occurring family among deployed on-chain verifiers.
Strengths and tradeoffs
- Universal, updatable SRS — one ceremony, many circuits, no per-circuit phase two
- Flexible arithmetisation: custom gates and lookups express non-arithmetic operations efficiently
- Verifier cost close to Groth16 and still practical on-chain
- Very large ecosystem with many independent implementations
- Larger proofs and higher gas than Groth16
- Not post-quantum
- Prover requires large-field FFTs, the main bottleneck at scale
- Arithmetisation flexibility is also a footgun — custom gates and lookup tables are a common source of underconstrained circuits
- 'PLONK' names a family, not one artefact: two implementations may share little
Choose it whenGeneral-purpose circuits where churn is expected and a per-circuit ceremony would be painful, and where on-chain verification is required but need not be absolutely minimal.
Related pages
Sources cited on this page · 4
All 40 sources for §01 are listed on the section page →
Cite this page
MarketComp (2026). PLONK and the PLONKish family. The ZK Field Manual (Version 1.3). MarketComp. https://zkpick.com/proof-systems/plonk/
@misc{zkfieldmanual-plonk-and-the-plonkish-family,
title = {PLONK and the PLONKish family — The ZK Field Manual},
author = {MarketComp},
year = {2026},
version = {1.3},
howpublished = {\url{https://zkpick.com/proof-systems/plonk/}},
note = {Accessed: YYYY-MM-DD}
}