Skip to content

Latest commit

 

History

History
147 lines (95 loc) · 5.33 KB

CONTRIBUTE.md

File metadata and controls

147 lines (95 loc) · 5.33 KB
Raw

How to Contribute Guide

First of all, register yourself in this form. We will add you to the #trusted-setup-phase2-ceremony channel in the Hermez Discord.

You can also reach us in the Hermez Telegram group.

Requirements

A machine with 4 cores and 16Gb would do the work, but we recommend a bigger machine to process the ceremony faster.

In this tutorial I'll describe all the steps required to run them in a new m5a.4xlarge AWS instance with ubuntu 20.04. The actual cost of this instance at the moment of writing is 0.644$/h But this is just for reference. Actually, it's better if you run your own hardware.

You can use any machine to run the ceremony. The important part of the ceremony is that the toxic value is not leaked and it's deleted after the completion of the ceremony.

This toxic value is in the memory while the ceremony is running. This toxic value is not displayed anywhere and it's not stored anywhere. It's recomended to restart the machine after the ceremony is completed to be sure this toxic value is not accessible any more.

You can check the Phase1 Perpetual Powers of Tau Ceremony used by Hermez for geting ideas of what to do to be sure the toxic value is deleted.

Preparation of the Machine.

You will need node version at least v14. For reference we are using v14.8.0

Quick instructions to install node if you don't have it:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash
source ~/.bashrc
nvm install v14.8.0
node --version

Install snarkjs:

npm install -g snarkjs

At the begining of the contribution you will receive 3 files:

  • circuit-2048-32-256-64_hez4_xxxx.zkey (60GB)
  • circuit-400-32-256-64_hez4_xxxx.zkey (15GB)
  • withdraw_hez4_xxxx.zkey (50MB)

Where xxxx is the contribution of the last participant.

wget --compression=none https://hermez.s3-eu-west-1.amazonaws.com/withdraw_hez4_xxxx.zkey
wget --compression=none https://hermez.s3-eu-west-1.amazonaws.com/circuit-400-32-256-64_hez4_xxxx.zkey
wget --compression=none https://hermez.s3-eu-west-1.amazonaws.com/circuit-2048-32-256-64_hez4_xxxx.zkey

Take note of the blake2b of the inputs and check with the ceremony coordinator the integrity of the files:

b2sum circuit-2048-32-256-64_hez4_xxxx.zkey
b2sum circuit-400-32-256-64_hez4_xxxx.zkey
b2sum withdraw_hez4_xxxx.zkey

To run the ceremony you need to run:

snarkjs zkey contribute circuit-2048-32-256-64_hez4_xxxx.zkey circuit-2048-32-256-64_hez4_yyyy.zkey -v -n=yourName

Substitute yourName for the name you want to appear in the file. Please do not uses spaces or special characters so we don't have problems. This name is important because this is what will be displayed, together with the contribution hash when all the contributions are listed in the final zkey file verification.

Substitute also yyyy by the actual contrubution. This should be xxxx + 1.

Write down the Circuit Hash and The Contribution Hash printed at the end.

The circuit hash for the 2048Txs circuit should be:

TODO

This Hash is computed at the phase two preparation, and depends on the r1cs file and the Powers of Tau result ceremony.

Do the same for the other two circuits:

snarkjs zkey contribute circuit-400-32-256-64_hez4_xxxx.zkey circuit-400-32-256-64_hez4_yyyy.zkey -v -n=yourName
snarkjs zkey contribute withdraw_hez4_xxxx.zkey withdraw_hez4_yyyy.zkey -v -n=yourName

The circuit hash for circuit-344-32-256-64 should be:

TODO

And the circuit hash of the withdraw circuit should be:

TODO

Write down the contribution hash for both circuits.

Now you can compute the checksum of your contribution results.

b2sum circuit-2048-32-256-64_hez4_yyyy.zkey
b2sum circuit-400-32-256-64_hez4_yyyy.zkey
b2sum withdraw_hez4_yyyy.zkey

With this, you will have all the information to fill the attestation template.

Create a copy of the template_attestation.md with name yyyy_yourName_attestation.txt

Fill all the fields of the template.

Sign the template with a PGP key or Keybase.

And generate a signed attestation with name: yyyy_yourName_attestation_signed.txt

Send the 3 responses plus the signed attestation to the coordinator.

You will be asked to do so by first creating a ssh-key if you don't have it.

ssh-keygen -t rsa -q -f "$HOME/.ssh/id_rsa" -N ""

Send the public key to the ceremony coordinator. You can see your public key by typing:

cat ~/.ssh/id_rsa.pub

Once the ceremony coordinator authorizes your key, you can upload the generated files and the signed attestation by doing:

sftp contributor_yyyy@s-628cadcefdfd40e39.server.transfer.us-east-1.amazonaws.com <<< $'put circuit-2048-32-256-64_hez4_yyyy.zkey'
sftp contributor_yyyy@s-628cadcefdfd40e39.server.transfer.us-east-1.amazonaws.com <<< $'put circuit-400-32-256-64_hez4_yyyy.zkey'
sftp contributor_yyyy@s-628cadcefdfd40e39.server.transfer.us-east-1.amazonaws.com <<< $'put withdraw_hez4_yyyy.zkey'
sftp contributor_yyyy@s-628cadcefdfd40e39.server.transfer.us-east-1.amazonaws.com <<< $'put yyyy_YourName_attestation_signed.txt'

Send also your public PGP Key or a link to yout PGP keybase to the coordinator.

Thank you very much for contributing!