Why are we doing this
As part of the implementation path and timeline for SnapDeal, we need to carefully plan and execute the trusted setup.
The entire nature of a zero-knowledge protocol depends on there being secret values that the prover has full knowledge about them.
Circuits are basically there to create inputs we need to run the trusted setup.
Trusted setup - the challenge of doing this:
Key principle: Coordination and Logistics are a big part of making this successful:
Stages we need to execute are:
- Pre Ceremony Checklist / Todos:
- A Blog post that contains:
- Requires:
- What circuits are we running?
- What specs do we need for the machines that are running?
- Ensure a link to the google form
The Main goal is to get a call to arms
- Github repo setup
- The github repo should at least contain
- A sketch of the ceremony (for those who are curious)
- A write up of the pre-req steps (dependencies etc) that should have been completed prior
- Minimum hardware requirements for the circuits
- Note you’ll want to know and share this information:
- Specs for the machine that needs to be used
- Specs for the space on the computer required
- Size of the files (to estimate the upload/download speed)
Team formation:
| Position we need | Ideal Candidate | Why |
|---|---|---|
@jake | support, answering technical questions, troubleshooting | |
@Kubuxu | support, answering technical questions, troubleshooting | |
@jennijuju | respond to open questions, engage with people running the trusted setup in different timezones | |
@Dragan Zurzin | Organise and run the trusted setup pipeline, figure out who and when will run the trusted setup, communicate with external team on troubleshooting and raising relevant issues to an appropriate priorrity level |
Implementation timeline and dates:
Learnings from the previous run:
Sort out getting the parameters into China before starting
- Cloud for verification
- Cloud credits in China to not worry about storage
- Recharging this can take more than 1 business week, so verify its topped up
- Aim to make as few traversals in / out of China as possible
- Pack Chinese participants to avoid having to make ingress requests
- Egress is less bad (worst case you can have a participant upload to JDCloud and ship a copy to EU to verify)
- Ingress will require someone paying for a VPN to accelerate (v pricey -> one 60 gb file could take more than a month without)
- Circuit tracker is probably better for actually logistically managing things with many colorful states.
- Calendar/Calendly is useful getting the initial state
- Make sure to get emails / slack handles so we can communicate with folks
- Blog post for Phase 2
- Include beacon for randomness at the end of Phase 1 in the blogpost
- Include the last contribution in the Phase 1 in the blogpost
Trusted setup runbook:
Read more: