Chia VDF competition and implementation
In an attempt to create a secure, open and decentralized consensus algorithm, Chia is hosting a 3 month long competition, with a total of around $100,000 in prizes, for the implementation of fast and secure verifiable delay functions using class groups.
This is an in-development version of the Chia Network proof-of-time verifiable delay function "inkfish". Below, you can also find a summary of the rules, a link to the rules and disclosures, relevant research papers.
The verifiable delay function used is the iterated squarings / RSA timelock construction. The code implements this verifiable delay function using class groups.
Furthermore, there are two proof approaches implemented here
- The first one by Krzysztof Pietrzak, that is fast to create, but large and slow to verify.
- The second one by Benjamin Wesolowski which is slower to create (but parallelizable), but small, and quick to verify. There is also a variation of wesolowski called n-wesolowski, that allows computing the proof faster, with some added parallelism, proof size, and verification time.
A sample submission with a C++ implementation can be found here.
By providing your legal first and last names, street address, city, zip code, daytime and home phone number, email address, and agreement to the VDF Contest Challenge Rules and Disclosures agreement, and along with the source code and documentation meeting the Entry Specifications described in the VDF Contest Challenge Rules and Disclosures agreement above (specifically the “Technical Submission”) to Chia's public Keybase group. The judges will communicate with your team using a keybase shared git repo.
The Entry Form and Technical Submission together are considered the entry (“Entry”). An Entry is not complete and will not be considered if either portion is missing.
Entry Form Requirements
An Entry may be submitted by a team of individuals working collaboratively (a “Team Contestant”), in which case, each individual member of the team must complete the Entry Form as described above and all members of the Team Contestant must designate the same point of contact to receive official Challenge correspondence.
Completed version of the Entry Form.
Signed version of the VDF Contest Challenge Rules and Disclosures agreement
Source code and documentation meeting the Entry Specifications described in the VDF Contest Challenge Rules and Disclosures agreement specific to the “Technical Submission” guidelines (outlined below).
All source code and documentation in an Entry must be made and submitted pursuant to the terms of the Apache or MIT License. The Apache Licence and instructions for applying it can be found here. The MIT License and instructions for applying it can be found here.
In the Fastest VDF Implementation category, code must be produced that will solve a VDF at a given number of iterations and security difficulty on the reference hardware. The repeated squarings VDF should be used, but we do not require computation of a proof, and only the speed of computation of the output will be judged. The VDF should be computed in the class group setting, and should output the same as our sample code above (see classgroup.py for naive implementation of class groups). The number of iterations and security difficulty will be provided at least 2 months before the end of the contest, and will be announced on the reddit and the keybase channel.
In the Best Discriminant Break category, the judging criteria is the file which gives the best number output from judge_entry.py. The entry needs to have three values each specifying which of our allowed discriminants it's on, and giving an element of the group and its order for each. The smallest of the three discriminants is the quality, and the greatest quality entry wins. The discriminants now are ones which have a four-byte challenge to create_discriminant().
The Contestant, or each member of a Team Contestant, must certify that the entire contents of the Technical Submission is the sole work of the Contestant, or collective work of the members of the Team Contestant, except to the extent that the Entry incorporates content that is publicly available or covered by an Apache or MIT license and is properly identified as such and that the Contestant has all legal rights necessary to grant the license granted in subsection (a) above.
Each Entry must be submitted with a Readme file that completes the entry form and describes in english the methods used in the software.
VDF Python implementation
An optional install is
gmpy2 to potentially speed up primality testing.
On a Mac, run
$ brew install gmp libmpc
Set up your virtual environments:
$ python3 -m venv env $ ln -s env/bin/activate $ . ./activate $ pip install -e .
Check out the command-line tools:
$ pot -h
Generate a wesolowski proof of time.
$ pot deadbeef 1000
Generate an n-wesolowski proof of time, with verbose logging.
$ pot -t n-wesolowski --depth 2 deadbeef --verbose 1000
Verify an n-wesolowski proof of time.
$ pot -t n-wesolowski deadbeef 1000 <proof>
To see some benchmarks, run
$ python3 benchmarks/benchmarks.py
Some sample benchmarks on dual core 3.5GHz i7. For the first part of the competition, the relevant benchmarks are the class group squaring times.
Classgroup 512 bit multiply 0.16 ms Classgroup 512 bit square 0.17 ms Classgroup 1024 bit multiply 0.34 ms Classgroup 1024 bit square 0.35 ms Classgroup 2048 bit multiply 0.83 ms Classgroup 2048 bit square 0.82 ms Generate 512 bit discriminant 17.56 ms Generate 1024 bit discriminant 28.33 ms Generate 2048 bit discriminant 216.82 ms VDF 10000 iterations, 512bit classgroup 1576.67 ms VDF 10000 iterations, 1024bit classgroup 3383.61 ms VDF 10000 iterations, 2048bit classgroup 8320.66 ms VDF 10000 iterations, 2048bit RSA modulus 115.71 ms VDF 10000 iterations, 4096bit RSA modulus 369.17 ms Wesolowski 512b class group, 10000 iterations, proof 287.43 ms - Percentage of VDF time: 18.2453909726637 % Wesolowski 512b class group, 10000 iterations, verification 62.54 ms n-wesolowski depth 2 512b class group, 10000 iterations, proof 1630.58 ms - Percentage of VDF time: 3.707000699434091 % n-wesolowski depth 2 512b class group, 10000 iterations, verification 172.94 ms Pietrzak 512b class group, 10000 iterations, proof 382.78 ms - Percentage of VDF time: 24.379376193507323 % Pietrzak 512b class group, 10000 iterations, verification 434.43 ms
C Classgroup 2048 bit multiply 0.09 ms C Classgroup 2048 bit square 0.075 ms