LibraryPrivacy2016Design paperCorpus record
On the Size of Pairing-based Non-interactive Arguments
Groth16. Jens Groth.
A pairing-based argument in three group elements. The proofs are tiny and cheap to verify. Each circuit needs its own setup, and a leaked setup can forge proofs.
Groth16 proves an arithmetic circuit in three group elements. Verification is a handful of pairings. The structured reference string is specific to that circuit, and anyone who kept the trapdoor can forge.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 4
- Records linked
- 4
Code
Source, repository, and what is actually hosted
- ePrint 2016/260https://eprint.iacr.org/2016/260
- The source URL is not a GitHub repository. No code remote is invented.
- Full text is not mirrored. Public availability is not a licence to copy the file onto this site.
- Add to a reading list
01 Claim ledger
What the paper is allowed to say
Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.
Claim 01 · Paper model
Size is the result
The paper is about how small a pairing argument can be. Three group elements became the reference that later systems either beat for other reasons or deliberately gave up.
Claim 02 · Paper model
The string is the circuit
The setup bakes in the program. Change a constraint and the old ceremony does not apply. A team that says we upgraded the circuit and kept the setup has left the proof system.
Claim 03 · Paper model
Toxic waste is literal
The trapdoor can satisfy the verifier for a false statement. Multi-party ceremonies exist to make one honest deletion enough. A ceremony that nobody can audit is a trusted party with extra steps.
Claim 04 · Paper model
Zero knowledge is optional to the use
The same argument can prove a public computation. Privacy appears only if the witness stays secret and the circuit does not leak it. A public input can undo the slogan.
02 Three cuts
Observation, model, falsifier
A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.
01 Size is the result
Observation
What the study says
The paper is about how small a pairing argument can be. Three group elements became the reference that later systems either beat for other reasons or deliberately gave up.
Model
What has to hold
Knowledge-of-exponent type assumptions hold in the pairing groups.
Falsifier
What would retire it
Which circuit is bound to the reference string?
02 The string is the circuit
Observation
What the study says
The setup bakes in the program. Change a constraint and the old ceremony does not apply. A team that says we upgraded the circuit and kept the setup has left the proof system.
Model
What has to hold
The verifier uses the verification key that matches the circuit the users think is running.
Falsifier
What would retire it
Is a circuit change paired with a new setup?
03 Toxic waste is literal
Observation
What the study says
The trapdoor can satisfy the verifier for a false statement. Multi-party ceremonies exist to make one honest deletion enough. A ceremony that nobody can audit is a trusted party with extra steps.
Model
What has to hold
The trapdoor was destroyed. One party who kept it can forge.
Falsifier
What would retire it
What is a public input, and does it leak the witness?
04 Zero knowledge is optional to the use
Observation
What the study says
The same argument can prove a public computation. Privacy appears only if the witness stays secret and the circuit does not leak it. A public input can undo the slogan.
Model
What has to hold
Public inputs really are the statement. Moving a secret into the public input destroys the privacy claim without breaking the proof.
Falsifier
What would retire it
What is a public input, and does it leak the witness?
03 Sequence
One action, as an operating tape
- 01Someone writes the statement as an arithmetic circuit.
- 02A setup produces a proving key and a verification key, and is supposed to destroy the trapdoor.
- 03The prover, who knows the witness, produces three group elements.
- 04Anyone with the verification key checks a pairing equation.
- 05A new circuit requires a new setup before those steps mean anything.
04 Load-bearing
The argument, and where a pitch drops it
Tiny proofs moved the trust into the ceremony
The cut
The chain is easy to verify and hard to trust if the setup is opaque. PLONK later made the setup universal so one ceremony could serve many circuits. It did not make the ceremony optional. STARKs are the line that refuses the string.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
Do not call a Groth16 deployment trustless. The setup is a trust assumption.
A proof of the wrong circuit is a correct proof
The cut
Groth16 will happily prove that a weaker program accepted a bad state. Auditing the circuit is not the cryptography's job, and it is most of the actual risk.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
Do not call a Groth16 deployment trustless. The setup is a trust assumption.
05 Register
What has to be true
Model · Not re-measured
Knowledge-of-exponent type assumptions hold in the pairing groups.
Model · Not re-measured
The trapdoor was destroyed. One party who kept it can forge.
Cryptography · Not re-measured
The verifier uses the verification key that matches the circuit the users think is running.
Cryptography · Not re-measured
Public inputs really are the statement. Moving a secret into the public input destroys the privacy claim without breaking the proof.
06 Divergence
What happened after the paper
Zcash's Sapling era and many early rollup proofs used Groth16 because the proofs are small. Newer systems moved to PLONK-family or transparent proofs to escape per-circuit setups. A project still on Groth16 in 2026 has to name its ceremony and its circuit. The paper will not do that for them.
A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.
07 Pre-mortem
What to check before you use the idea
- 0 of 4 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.
08 Anatomy
The paper, in the order a builder needs
The problem it names
Earlier SNARKs were still large or costly. Groth16 is about the minimum size of a pairing argument for an arithmetic circuit, under a structured reference string.
What the design proposes
- A circuit-specific common reference string.
- A proof of three group elements.
- Verification with a small number of pairings.
How the mechanism is specified
- The setup encodes the circuit. A different program needs a different setup.
- Soundness fails if the trapdoor is known. The ceremony is the security assumption you can actually botch.
- Zero knowledge is a property of the proof, not a property of the system that feeds it secret data.
What this page does not treat as proven
- Do not call a Groth16 deployment trustless. The setup is a trust assumption.
- Universal setups are PLONK and its relatives, not this paper.
- A small proof is not a small prover. Proving cost still tracks the circuit.
Why the desk still reads it
Ask who ran the setup, who was supposed to delete the trapdoor, and what program the string is bound to. If those answers are missing, the three group elements are a costume.
09 Lexicon
Terms, opened into the record
- Common reference string
- The setup output both prover and verifier need. In Groth16 it is specific to one circuit.
- Trapdoor
- The secret from the setup that can forge proofs if it is kept.
10 Repository
Every linked record on this page
Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.
Concepts
Papers
This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.
Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.
