Contributor CLI and verification tools for the Privacy Boost trusted setup ceremony.
The ceremony uses Groth16 multi-party computation (MPC) via gnark. Each contributor generates local randomness, mixes it into the phase2 parameters, and submits the result. As long as at least one participant is honest and destroys their randomness, the final parameters are secure.
There have been two production ceremony rounds. Each one is recorded under rounds/, with its circuit shapes, release tags, config file and config checksum.
- First round,
prod-ceremony-2026-01. Complete. - Second round,
prod-ceremony-2026-02. Complete. This is the round the current production keys come from.
main always carries the current round's config. Past rounds stay reachable through their own record above and through the release tag they ran under.
Both rounds are complete. Each round's public bundle and derived keys are available for download.
Second round, prod-ceremony-2026-02, 21 circuits and 490 contributions:
- Public bundle: https://file.ceremony.privacyboost.io/prod-20260902-public.tar
- Keys: https://file.ceremony.privacyboost.io/prod-20260902-keys.tar
First round, prod-ceremony-2026-01, 18 circuits:
- Public bundle: https://file.ceremony.privacyboost.io/prod-20260401-public.tar.gz
- Keys: https://file.ceremony.privacyboost.io/prod-20260401-keys.tar.gz
Download and extract the public bundle, then run:
go build -o ./bin/ceremony ./cmd/ceremony
./bin/ceremony verify-public --bundle-dir <BUNDLE_DIR>Full verification of the second round took just under 8 hours on an M1 Pro MacBook, covering all 21 circuits and 490 contributions, and not counting the time to download the bundle. That run reused an already-converted powers-of-tau cache, so allow roughly 3 more hours on a first run, when the verifier fetches about 2.4 GB of powers-of-tau files and converts them. The first round's bundle is about three times larger and its full verification took under 30 hours on the same machine.
See Public Verification for a detailed explanation of how verification works.
No need to clone the repository — just download and run:
curl -fsSLO https://raw.githubusercontent.com/testinprod-io/privacy-boost-ceremony/main/circuit-setup/contribute.sh
bash contribute.shThe script will prompt for the coordinator URL (provided by the ceremony coordinator), then present options to download a pre-built binary, build with local Go, or build with Docker.
See Contributor Guide for detailed instructions.
See LICENSE.