The proving system we use, Groth16, requires a per-circuit trusted setup: each circuit requires some public parameters, called a CRS (common reference string), and generating these public parameters involves the creation of private parameters. Knowing these private parameters would allow for forging proofs; ensuring their destruction is paramount.
To that end, systems don’t simply generate these parameters, but instead go through a setup ceremony, involving many participants, such that the setup is secure so long as at least one participant destroys the private parameters they’ve used to contribute to the ceremony.
This chapter describes the technical aspects of a ceremony setting up these parameters, based off of KMSV21 (Snarky Ceremonies), itself based off of BGM17. We organize the information herein as follows:
- The Groth16 Recap section provides a brief recap of how the formulas and CRS structure for Groth16 work.
- The Discrete Logarithm Proofs section describes a simple discrete logarithm proof we need for setup contributions.
- The Contributions section describes the crux of the ceremony: how users make contributions to the parameters.
We work with a triplet of groups , with an associated field of scalars , equipped with a pairing operation: We also have designated generator elements for each of the respective groups, with . In the case of Penumbra, the concrete groups used are from BLS12-377.
We take the convention that lowercase letters (e.g. ) are taken to be scalars in , and uppercase letters (e.g. ) are taken to be elements of , , or .
For , we use the shorthand: for scalar multiplication using one of the designated generators.
All of the groups we work with being commutative, we use additive notation consistently.
As an example of this use of additive notation, consider the following equation:
As a somewhat unfortunate conflict of notation, we use to denote the set , and to denote a list of elements, with ranging over a set .