Reference Document Comments and Contributions

[ZKProof Standards]

Dear ZKProof Community,

We wanted to share with you the recordings of the talks from the 2nd ZKProof Workshop, as well as some pictures of the event.

After a successful workshop, we are working on the new ZKProof Reference Document (the first version is a combination of the previously existing documents). We have established an editorial process in order to maintain the document and add improvements that derive from each workshop. Shortly the process is composed of the followingp phases:

• Workshop Notes: the notes taken from each of the breakout sessions at the workshop are published on the forum. 
• Discussion and Comments: anyone can comment and suggest specific improvements to the documents and discussion. 
• Contributions: volunteers will write their contributions and submit them to the editors of the respective documents (Proposals and Reference Document). 
• Editing: the editors will then collect all the contributions and add them to the ZKProof Community Reference document (note that for the proposals, the authors will be in charge of this step). 
• Call for Comments: we will have a call for comments on the new version of the Community Reference document.

Here are the next actions points:

1. You now have until Sunday 26th to comment and suggest new contributions. On this day we will collect and publish all the comments and suggested contributions.
   
2. We are adding all contributors to the mailing list contri...@zkproof.org to coordinate (if you want to join, see here).
   
3. In order to be in touch with the editors and submit your contributions or comment, please write to edi...@zkproof.org.

Here is the list of links to each topic and discussion. We encourage everyone to be part of the conversation and suggest improvements and contributions!

• Discussion on ZKProof Community Reference
• ZK Recursive Composition
• Structured Reference String Generation
• Formal Verification for ZK
• Security Assumptions Underpinning Zero-Knowledge Proofs
• Commit-and-Prove Zero-Knowledge Proofs
• Elliptic Curve Generation for ZK Systems
• Interoperability of ZK Systems (and JR1CS proposal)
• Domain-Specific Languages for ZK
• Interactive Zero Knowledge 
  
• ZK Protocol Security Analysis and Correctness

PS: if you are receiving this email but are not part of the mailing list, we encourage you to join in order to stay up-to-date with the effort and standards process (join the community mailing list here)

Best Regards,

Daniel Benarroch