New Contribution Request

[mztacat]

Contributor: Mztacat
SSH Public key: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKnDLoOVLB7A+f3uYevkbt6IcvolRSyCzCyEQgvo86Qw
Attestation: I, Mztacat, confirm that I have generated this SSH key and am submitting it for the contribution ceremony.

[github-actions]

Thank you for your interest in contributing to the Zircuit Ceremony!

Begin the following process only after receiving notification that it is your turn to contribute through a message in this issue. Please follow instructions only from the issue's assignee.

Once notified, you have 15 minutes to confirm by posting a message in this issue that you have started your contribution. If you do not confirm within 15 minutes, your contribution slot might be suspended.

Prerequisites

Get sources

git clone https://github.com/zircuit-labs/ceremony.git
cd ceremony

Generate an SSH Key - Optional

Contributors are required to provide an SSH public key to upload their contributions to our servers.

If you don't have one, you can generate a new SSH public key as:

ssh-keygen -t ed25519 -b 256 -f ./id_ceremony -N "" -C ""

Next, edit the issue description and report as SSH Public key the output of the command:

cat ./id_ceremony.pub

Please note that if you use Docker to compute your contribution, the key will be automatically added to the Docker image during the build process and available in the working directory. If you already have an SSH key and prefer not to generate a new one, you will need to import your existing key manually.

Build

To contribute, you will need a total of at least 33 GiB of combined RAM and SWAP memory available. If you are using Docker, ensure that sufficient resources are allocated when running images.

From sources

cargo install --locked --path . --root .
export PATH="./bin:${PATH}"
chmod +x download.sh

With Docker

docker build . -t "ceremony"

Contribute

Before proceeding, please post a comment on this issue to notify us that you have started your contribution.

Only in the case you are using Docker, you need to first run the built image:

docker run -it "ceremony"

Download the latest contribution:

./download.sh

and verify that the hash of the downloaded contribution matches the one reported here.

Then, compute your contribution:

export RUST_LOG=info
contribute -c ./contributions

The last command will create a contribution using the default settings. For additional options and configurations, please refer to instructions.

If you don't plan to actively use your computer during the contribution phase, please read this section to avoid performance degradation due to power-saving settings.

Upload Contribution

After completing your contribution, upload it to our server using your SSH key:

sftp -i ./id_ceremony [email protected]
put ./contributions/[YOUR_CONTRIBUTION_ID].csrs
quit

If your upload is interrupted, you can use reput in place of put to resume it.

Once the upload is complete, post a comment on this issue to notify us that your contribution has been uploaded.

[mztacat]

Contribution has started

[mztacat]

Contribution is done

[mztacat]

Contribution has started

You should not start the contribution before getting approval from zircuit team. Current active issue number in participation is approx 150 approx ;)

oh, never knew, i actually followed the instruction here to begin in 15 minutes

[mztacat]

hi @zvorcuit, i just concluded my contribution

root@root:/ceremony# export RUST_LOG=info
contribute -c ./contributions
[2024-06-16T18:36:58Z INFO ceremony::contribution] Reading contribution from "./contributions/0000000032.csrs"
[2024-06-16T18:38:18Z INFO ceremony::check] Checking contribution with id 32
[2024-06-16T18:38:18Z INFO ceremony::check] Contribution's k and n are correct
[2024-06-16T18:38:18Z INFO ceremony::check] > SRS Check #1 Succeded: srs uses hardcoded group generators
[2024-06-16T18:38:18Z INFO ceremony::check] > SRS Check #2 Succeded: g2 and s_g2 have order r
[2024-06-16T18:38:18Z INFO ceremony::check] > SRS Check #3 Succeded: the g vector has expected size
memory allocation of 8589934592 bytes failed
Aborted
root@root:/ceremony# contribute -c ./contributions
[2024-06-16T18:40:14Z INFO ceremony::contribution] Reading contribution from "./contributions/0000000032.csrs"
[2024-06-16T18:41:31Z INFO ceremony::check] Checking contribution with id 32
[2024-06-16T18:41:31Z INFO ceremony::check] Contribution's k and n are correct
[2024-06-16T18:41:31Z INFO ceremony::check] > SRS Check #1 Succeded: srs uses hardcoded group generators
[2024-06-16T18:41:31Z INFO ceremony::check] > SRS Check #2 Succeded: g2 and s_g2 have order r
[2024-06-16T18:41:31Z INFO ceremony::check] > SRS Check #3 Succeded: the g vector has expected size

[2024-06-16T18:56:28Z INFO ceremony::check] > SRS Check #4 Succeded: srs is well-formed
[2024-06-16T18:56:28Z INFO ceremony::check] > SRS Check #5 Succeded: srs is non-degenerative
[2024-06-16T18:56:29Z INFO ceremony::check] SRS is valid
[2024-06-16T18:56:29Z INFO ceremony::check] Contribution with id 32 is valid
[2024-06-16T18:56:29Z INFO ceremony::secrets] Generating secrets ..
[2024-06-16T18:56:29Z INFO ceremony::secrets] Generating and hashing 1073741824 random bytes
[2024-06-16T18:56:37Z INFO ceremony::secrets] Hashing hasher's state 1048576 times
[2024-06-16T18:56:37Z INFO ceremony::secrets] Extracting secrets
[2024-06-16T18:56:37Z INFO ceremony::contribute] Rescaling powers of tau..

[2024-06-17T00:34:41Z INFO ceremony::contribute] Computing contribution proof..
[2024-06-17T00:35:11Z INFO ceremony::contribution] Contribution written to "./contributions/0000000033.csrs"