-
Notifications
You must be signed in to change notification settings - Fork 9
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
Current limitations of Plonky3 support for circuits3 #927
Comments
codeblooded1729
added a commit
that referenced
this issue
Nov 27, 2023
The PR marks the beginning of rewriting our circuits in plonky3. We are experimenting with `uni_stark` crate for now. Current limitations: #927 --------- Co-authored-by: Matthias Görgens <[email protected]>
Who is working on this one? @phildimes @codeblooded1729 |
Is recursion still open? What about verification? |
@codeblooded1729 I assigned this to you. That doesn't mean you need to fix all the problems, just to keep this list up to date. Thanks! |
We need to see about using multiple limbs for our 32 bit values? |
This comment was marked as duplicate.
This comment was marked as duplicate.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yet to figure out the analogue of
constraint_degree
in context of plonky3'suni_stark
Current verifer of
uni_stark
in plonky3 repo uses some hardcoded values. I have create a branch with temporary hack to solve this issue in our fork of plonky3, and using that branch in circuit3.We would be using valida prover as an example for our vm. The functionalities which are yet to be implemented in valida as on 22 Jan 2024 are
The text was updated successfully, but these errors were encountered: