-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the 3x GPU prover #356
Conversation
This reverts commit 52dccc9.
Updated to compute the FFT domains properly and to add a GPU example (run with |
This comment was supposed to be posted before, but I forgot to press the comment button 😑 Updated. This now includes a conditional module in snarky that extends a normal The basic structure now is:
|
assert (Snarky.Libsnark.Mnt6753.Default.Proof.verify proof key public_input) ; | ||
ignore proof | ||
|
||
(* Test for the original gpu prover competition output. Disabled. *) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be deleted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was keeping this around in case Hamish wanted to keep testing using his old set-up. Very happy to remove this if we think he should just be interfacing with the OCaml code (or something else) instead.
This PR
#include
pathsCMakeLists.txt
s,dune
files and.ml
files were changed to make things buildsrc/camlsnark_c/libsnark-caml
./snarky_cuda
, can be installed withopam pin ./snarky_cuda
from the project rootThere is a test that can be run with
dune exec src/camlsnark_c/groth16_gpu_prover/test/test.exe
.NOTE: This PR doesn't integrate the prover with the snarky API yet, but it should be possible to test it usinggenerate_witness
(from #322) to get the input and using the preprocessing and proving functions inGroth16_gpu_prover
.Update: This is no longer true, see the comment below.