You can see an E2E demo with 3 participants and the beacon at the end by running test.sh.
Coordinators run:
newto create a new accumulatorverify-and-transformafter receiving a contribution to the previous challenge, to produce a new challenge for the next contributionbeaconat the end of the ceremony (optional, as the security proof does not require it)
Users should only care about the contribute option.
$ ./phase1 --help
Usage: ./phase1 [OPTIONS]
Optional arguments:
-h, --help
-c, --curve-kind CURVE-KIND
the elliptic curve to use (default: bls12_381)
-p, --proving-system PROVING-SYSTEM
the proving system to use (default: groth16)
-b, --batch-size BATCH-SIZE
the size of batches to process (default: 256)
-P, --power POWER the circuit power (circuit size will be 2^{power}) (default: 21)
Available commands:
new creates a new challenge for the ceremony
contribute contribute to ceremony by producing a response to a challenge (or create a new challenge if this is the first contribution)
beacon contribute randomness via a random beacon (e.g. a bitcoin block header hash)
verify-and-transform verify the contributions so far and generate a new challenge
This binary will only be run by the coordinator after Phase 1 has been executed. Note that the parameters produced are only for the Groth16 SNARK.
./prepare_phase2 --help
Usage: ./prepare_phase2 [OPTIONS]
Optional arguments:
-h, --help
-p, --phase2-fname PHASE2-FNAME
the file which will contain the FFT coefficients processed for Phase 2 of the setup
-r, --response-fname RESPONSE-FNAME
the response file which will be processed for the specialization (phase 2) of the setup
-c, --curve-kind CURVE-KIND
the elliptic curve to use (default: bls12_377)
-P, --proving-system PROVING-SYSTEM
the proving system to use (default: groth16)
-b, --batch-size BATCH-SIZE
the size of batches to process (default: 256)
--power POWER the number of powers used for phase 1 (circuit size will be 2^{power}) (default: 21)
--phase2-size PHASE2-SIZE the size of the phase 2 circuit (default: 21
This work is licensed under either of the following licenses, at your discretion.
- Apache License Version 2.0 (LICENSE-APACHE or https://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or https://opensource.org/licenses/MIT)
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.