-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Contribution #685
Comments
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. PrerequisitesGet sourcesgit clone https://github.com/zircuit-labs/ceremony.git
cd ceremony Generate an SSH Key - OptionalContributors 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. BuildTo 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 sourcescargo install --locked --path . --root .
export PATH="./bin:${PATH}"
chmod +x download.sh With Dockerdocker build . -t "ceremony" ContributeBefore proceeding, please post a comment on this issue to notify us that you have started your contribution.
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 ContributionAfter 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 Once the upload is complete, post a comment on this issue to notify us that your contribution has been uploaded. |
start contribution |
Hello, contributions period will soon come to an end and we will not be able to process your contribution in time. The content of your comment will be used as part of input to verifiable contribution. |
The ceremony ended! Thank you for your interest in being a part of it! |
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]
The text was updated successfully, but these errors were encountered: