LibraryPrivacy2019Design paperCorpus record
Sonic: Zero-Knowledge SNARKs from Linear-Size Universal and Updatable Structured Reference Strings
Sonic. Mary Maller, Sean Bowe, Markulf Kohlweiss and Sarah Meiklejohn.
Sonic uses a structured reference string that is universal: one setup can serve many circuits, and it can be updated so the toxic waste is harder to keep.
A reading of the public document. Not a copy of it, and not a claim about a later network that reused the name.
If a project says the setup is universal, ask whether a new circuit needs a new ceremony.
The five-minute read
The defect
Groth16 needs a new trusted setup for every circuit. A chain that wants many programs cannot hold a ceremony for each one.
The rule
Sonic uses a structured reference string that is universal: one setup can serve many circuits, and it can be updated so the toxic waste is harder to keep.
How it is put together
The reference string is not tied to one program. Updates let a new participant destroy the previous trapdoor if they are honest. Proofs are larger and slower than Groth16. That is the trade.
Where the claim stops
Universal does not mean no setup.
One action, walked through
- Run one setup.
- Compile a new circuit against that string.
- Update the string when a new party joins, if the protocol says so.
- Does a new program need a new setup?
The argument, unpacked
Why it is still on the desk
If a project says the setup is universal, ask whether a new circuit needs a new ceremony.
After the text
PLONK and later universal SNARKs cite this line. The ceremony design of a particular chain is a separate document.
What has to be true
- Universal does not mean no setup.
- Sonic is not PLONK. PLONK came after and changed the polynomial protocol.
- An update helps only if the new participant was honest and deleted their randomness.
What happened after the paper
PLONK and later universal SNARKs cite this line. The ceremony design of a particular chain is a separate document.
What to check before you use the idea
- Does a new program need a new setup?
- Can the reference string be updated?
- What is the proof size relative to Groth16?
Terms
- Universal SRS
- A setup string that many circuits can share.
- Update
- A new contribution that should destroy the old trapdoor.
The problem the paper names
Groth16 needs a new trusted setup for every circuit. A chain that wants many programs cannot hold a ceremony for each one.
What the design proposes
- The reference string is not tied to one program.
- Updates let a new participant destroy the previous trapdoor if they are honest.
- Proofs are larger and slower than Groth16. That is the trade.
How the mechanism is specified
- Run one setup.
- Compile a new circuit against that string.
- Update the string when a new party joins, if the protocol says so.
What this page does not treat as proven
- Universal does not mean no setup.
- Sonic is not PLONK. PLONK came after and changed the polynomial protocol.
- An update helps only if the new participant was honest and deleted their randomness.
Why a venture studio still reads it
If a project says the setup is universal, ask whether a new circuit needs a new ceremony.
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.
