forked from AleoNet/aleo-setup
-
Notifications
You must be signed in to change notification settings - Fork 0
/
e2e_outer.sh
executable file
·41 lines (29 loc) · 1.51 KB
/
e2e_outer.sh
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
#!/bin/bash -e
rm -f challenge* response* new_challenge* processed*
POWER=20
BATCH=10000
CURVE="bw6"
SEED=`tr -dc 'A-F0-9' < /dev/urandom | head -c32`
echo $SEED > seed1
phase1="cargo run --release --bin phase1 --features cli -- --curve-kind $CURVE --batch-size $BATCH --contribution-mode full --power $POWER --seed seed1 --proving-system groth16"
phase2="cargo run --release --bin prepare_phase2 --features cli -- --curve-kind $CURVE --batch-size $BATCH --power $POWER --phase2-size $POWER"
snark="cargo run --release --bin setup2 --features cli --"
####### Phase 1
$phase1 new --challenge-fname challenge
yes | $phase1 contribute --challenge-fname challenge --response-fname response
$phase1 verify-and-transform-pok-and-correctness --challenge-fname challenge --response-fname response --new-challenge-fname new_challenge
rm challenge new_challenge # no longer needed
###### Prepare Phase 2
$phase2 --response-fname response --phase2-fname processed --phase2-size $POWER
###### Phase 2
$snark new --phase1 processed --output initial_ceremony --phase1-size $POWER
cp initial_ceremony contribution1
yes | $snark contribute --data contribution1
$snark verify --before initial_ceremony --after contribution1
# a new contributor contributes
cp contribution1 contribution2
yes | $snark contribute --data contribution2
$snark verify --before contribution1 --after contribution2
$snark verify --before initial_ceremony --after contribution2
# done! since `verify` passed, you can be sure that this will work
# as shown in the `mpc.rs` example