0000000009.csrs

[cuongnx42]

Contributor: [contributor information - Optional]
SSH Public key: [contributor SSH public key (if you don't have one, submit the issue to receive instructions)"- Required]
Attestation: [any form of attestation for contribution (e.g., signature) - Optional]

[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 one hour, 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 contributor@sftp.ceremony.zircuit.com
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.

[zvorcuit]

Hey @cuongnx42, please generate SSH public key and add to first comment.

[cuongnx42]

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKDxdvS0+hhapiUTElCKDyC1H0LkSQnMhsHQkEdx65D1

[cuongnx42]

I'm ready to contribute now.

[zvorcuit]

Hey @cuongnx42, the previous contributor is uploading their contribution. Please confirm that you're ready to start your contribution.

[cuongnx42]

Yes, I'm ready now

[zvorcuit]

You can now proceed with your contribution!

Please notify us with a comment on this issue after each of the following steps is completed:

• Your contribution process begins.
• Your upload is finished.

Please note that if you do not acknowledge the start of the contribution process within 15 minutes, your contribution slot will be suspended.

[cuongnx42]

Downloading contribution ./download.sh

[cuongnx42]

contribute -c ./contributions
[2024-06-09T18:02:18Z INFO ceremony::contribution] Reading contribution from "./contributions/0000000008.csrs"
[2024-06-09T18:03:40Z INFO ceremony::check] Checking contribution with id 8
[2024-06-09T18:03:40Z INFO ceremony::check] Contribution's k and n are correct
[2024-06-09T18:03:40Z INFO ceremony::check] > SRS Check #1 Succeded: srs uses hardcoded group generators
[2024-06-09T18:03:40Z INFO ceremony::check] > SRS Check #2 Succeded: g2 and s_g2 have order r
[2024-06-09T18:03:40Z INFO ceremony::check] > SRS Check #3 Succeded: the g vector has expected size
[2024-06-09T18:07:34Z INFO ceremony::check] > SRS Check #4 Succeded: srs is well-formed
[2024-06-09T18:07:34Z INFO ceremony::check] > SRS Check #5 Succeded: srs is non-degenerative
[2024-06-09T18:07:34Z INFO ceremony::check] SRS is valid
[2024-06-09T18:07:34Z INFO ceremony::check] Contribution with id 8 is valid
[2024-06-09T18:07:34Z INFO ceremony::secrets] Generating secrets ..
[2024-06-09T18:07:34Z INFO ceremony::secrets] Generating and hashing 1073741824 random bytes
[2024-06-09T18:07:39Z INFO ceremony::secrets] Hashing hasher's state 1048576 times
[2024-06-09T18:07:40Z INFO ceremony::secrets] Extracting secrets
[2024-06-09T18:07:40Z INFO ceremony::contribute] Rescaling powers of tau..

[cuongnx42]

Uploading ./contributions/0000000009.csrs to /0000000009.csrs

[cuongnx42]

Upload contribution finished

[zvorcuit]

Contribution has been successfully verified.

The hash of contribution is d8893b11610daba1f00f6974098d88b3100d469220bdeed9fbf057dde90c42c8.

Added to the contribution list with ID 0000000009.csrs.

Thanks for your contribution!

[zvorcuit]

Dear @cuongnx42,

We would like to reward your efforts in the ceremony by sending you Zircuit Points!

If you're interested, please provide an Ethereum address within 7 days. We will then transfer the Zircuit Points to the address you provide in the following days.

Thanks once more for your participation in the ceremony!

[cuongnx42]

Dear @zvorcuit,

I'm pleased to receive Zircuit Points. My Ethereum address is 0x88287444cE4f824f7B0b9F49fe68d9015d30D912

Best regards,
@cuongnx42