The participants discussed the final changes to the contests on the ZKP-system, the criteria of the contests, judging, and also touched on the topic of awards to contest organizers — whether it is necessary to do it at all.
Final Approval Of Two ZKP Contests
It’s time to launch two contests: Groth16 zkSNARK Proof Verification Use Cases and Solidity to TVM Compiler Groth16 zkSNARK Proof Verification Instruction Support Introduction. The most important thing, according to Pavel P, is that the use cases are tested and get proof they work. And there is no need to make any additional complex restrictions in the proposals because it is already quite difficult to find 2-3 people who will judge and not participate in the same contest.
Alexei Novikov advised to finally discuss the issue in advance, before launching the contests, so that there would be no misunderstandings when making decisions by the judges because the awards are quite high. He gave his reasons: “There will be two submissions: one very impressive and of high quality, and the other beautiful. The first is from a well-known company, and the second is from newcomers. One of them will take first place, the other will take third place… And what is a contest — it is a desire to achieve some goal. And the one who is closer to this goal gets more points”.
He also noted that the jury should evaluate the innovation of ideas, complexity, suitability (quality) of the application, as well as it is desirable to list the areas of application of this or that use case.
Pavel P believes: “The main goal, in this case, is to get interesting use cases using testnet primitives for the ZKP test. And an interesting use case is, by definition, a subjective criterion.” According to Pavel P, it is very important to keep in mind that there will be fairly simple sentences in the finished works since it is quite difficult for people who have not previously faced such tasks to understand everything right away. That’s why these contests are a kind of training, a verification, and a test.
Pavel P also announced that until May 20, it is planned to hold an AMA session for potential participants and judges within the framework of DevEx SG, where everything will be discussed in more detail.
TON Cash Specification
According to Pavel P, one good TON Cash specification is needed, which will then be implemented. Therefore, it is necessary to declare a few large rewards and to offer consolation prizes to the rest.
“This will be a big full-fledged technical article,” Pavel P explained, “that will describe how to crossover tech preview with working with this primitive in TON. And by and large, according to the feedback, this is considered as fairly time-consuming work.”
Alexei Novikov is categorically against equal consolation prizes because there can be a huge difference in the work done between places. Pavel P stressed that there should be simplicity and efficiency and there is no need to complicate anything:
You can do the scheme in different ways and in the documentation there may be the different speed of preparing the proof and therefore the efficiency (speed) of execution.
Compiler Contest From Groth16 To Solidity
The message of the contest is as straightforward as possible: so that those who wish, including in this contest, can use Solidity. The task is simple, according to Pavel P, and it will take only a few days to prepare the work: “The use case itself can be done in a week — simple scheme, prove it and create the submission. All this is needed so that more people can practice and participate in contests.”
Sergei Tyurin proposed to run all three ZKP contests in sequence, with the compiler contest being run first, and the remaining two contests only afterward.
They decided that, with all the edits and additional criteria, the contests could be launched.
Rewards To Initiators
According to Pavel P, everyone who writes contests can put up some percentage of the reward in the proposal: “After all, all preparation is actual work. It’s a floating practice, and you can put 1-2%. Ideally, it should be obligatory to specify the rewards to those who write, because it encourages the creation of contests. It’s not just that we wait for someone to write, and then we’ll do it. There is a lot of what the system needs. Think it up, write it down, and get a reward”.