0000000002.csrs

[hoasen1]

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 1 hour 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 [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.

[zvorcuit]

Hello @hoasen1 thank you for your interest.

Please add public key in your first comment, or in the new comment, to be able to proceed with contribution.

[hoasen1]

AAAAC3NzaC1lZDI1NTE5AAAAIM2nIcNjNsuAhj7vPpiNv7PF3SSRJKJO/3rFO8qqln5Z

[hoasen1]

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIM2nIcNjNsuAhj7vPpiNv7PF3SSRJKJO/3rFO8qqln5Z

[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 one hour, your contribution slot will be suspended.

[hoasen1]

contribution process begins

[hoasen1]

root@localhost:~/ceremony# export RUST_LOG=info
contribute -c ./contributions
[2024-06-07T16:41:59Z INFO ceremony::contribution] Reading contribution from "./contributions/0000000001.csrs"
[2024-06-07T16:45:27Z INFO ceremony::check] Checking contribution with id 1
[2024-06-07T16:45:27Z INFO ceremony::check] Contribution's k and n are correct
[2024-06-07T16:45:27Z INFO ceremony::check] > SRS Check #1 Succeded: srs uses hardcoded group generators
[2024-06-07T16:45:27Z INFO ceremony::check] > SRS Check #2 Succeded: g2 and s_g2 have order r
[2024-06-07T16:45:27Z INFO ceremony::check] > SRS Check #3 Succeded: the g vector has expected size
[2024-06-07T16:50:03Z INFO ceremony::check] > SRS Check #4 Succeded: srs is well-formed
[2024-06-07T16:50:03Z INFO ceremony::check] > SRS Check #5 Succeded: srs is non-degenerative
[2024-06-07T16:50:04Z INFO ceremony::check] SRS is valid
[2024-06-07T16:50:04Z INFO ceremony::check] Contribution with id 1 is valid
[2024-06-07T16:50:04Z INFO ceremony::secrets] Generating secrets ..
[2024-06-07T16:50:04Z INFO ceremony::secrets] Generating and hashing 1073741824 random bytes
[2024-06-07T16:50:08Z INFO ceremony::secrets] Hashing hasher's state 1048576 times
[2024-06-07T16:50:09Z INFO ceremony::secrets] Extracting secrets
[2024-06-07T16:50:09Z INFO ceremony::contribute] Rescaling powers of tau..

[zvorcuit]

Dear @hoasen1, is it still running or you just finished computing your contribution?

Note that computing a contribution can take several hours to complete (approximately 1 hour and 15 minutes on an Apple Macbook Pro M2 with 32GiB of RAM).

[hoasen1]

it is still running

[hoasen1]

Welcome to Zircuit Mainnet Ceremony
Connected to sftp.ceremony.zircuit.com.
sftp> put ./contributions/0000000002.csrs
Uploading ./contributions/0000000002.csrs to /0000000002.csrs
0000000002.csrs 100% 16GB 78.3MB/s 03:29

[hoasen1]

my upload has finished

[zvorcuit]

Contribution has been successfully verified.

The hash of contribution is 4f3065f68d7e4291050ecc6e6323cba8c1705a30f320fbbfcece3d1cb1f85dca.

Added to the contribution list with ID 0000000002.csrs.

Thanks for your contribution!

[zvorcuit]

Dear @hoasen1,

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!

[hoasen1]

Hello @zvorcuit ,

Thank you very much!

This is my Ethereum address: 0x0B9B6ff6c5caB298B5365a1A6dA2AED01a9FA2aa

Best regards,
@hoasen1