KZG-Ceremony Call #6

[tvanepps]

Meeting Info

• Aug 18, 2022, 11:30 UTC
• Duration: 60 minutes
• Youtube Recording: Ethereum Cat Herders channel
• Zoom Join Link

📆 Subscribe to the Ethereum Protocol Call calendar for future calls
💻 Join the Ethereum R&D Discord for continued discussion

⭐ KZG Ceremony Specs Repo
⭐ Ceremony Resources

Notes from Kev:

1. Landing page should focus on the value of the ceremony and less on the cryptography behind it
2. POAP should be given after the user has verified that they were included in the final ceremony.
3. Remove usage of cookies for returning users who did not contribute
4. Start an MVP frontend for DevCon which will have the same theme as the final designs

Expanding:

1. As a regular user, we want to feel like the activity we are doing is important and explaining the cryptography doesn’t convey this. Instead, we can explain to the user, what impact they will have on the Ethereum ecosystem, if they contribute honestly.

2. There are two attestations for the ceremony that a contributor can make. The first is that they participated in a trusted setup and can be done once they’ve contributed (in the middle of the ceremony). The second is that their participation was included in the final output of the ceremony. This can only be done once the ceremony has completed. We want to incentivise users to come back and share the second attestation and we do this by only giving them the POAP at this stage.

3. Currently in the designs a user can sign in with github/Ethereum and they will need to sign some message in the case of Ethereum. If they do not contribute, and come back again, we use cookies to ensure that they don’t need to sign some message again. We can remove cookies by changing the workflow such that when a user signs in, they should be aware that they will immediately be placed into the queue to contribute. We can check if a user has contributed before by checking their ID in the “global” transcript. Noting from the last meeting about the transcript now including oAUTH IDs such as github/Ethereum.

4. With DevCon fast approaching, we want an MVP design and not the final product that we are viewing on figma which will take a considerable amount of time. This MVP should include the ability for users to add their own randomness by keyboard smashing or (if possible) recording mouse movements. Ideally, we want this MVP to have the same theme as the final figma drawings that we are currently seeing, so its not a shock when we iteratively change ot the final version.

Action steps from meeting:

• Finalise responsibility for the MVP regarding frontend (HTML/CSS/JS)
• Explore the possibility of having a darker vibe(theme) for the ceremony

[poojaranjan]

Recording: https://www.youtube.com/watch?v=6LsVjf9qARI