Verification circuit (compute_b part) #96
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements one part of the verification circuit: the
compute_bpart (see here).The circuit computes$\prod_i (1+u_{k-1-i} x^{2^i})$ but for 32 challenges $u_i$ , it runs out of memory when it computes the $x^{2^i}$ (in the
Expressionpart)...The implementation works for 16 challenges$u_i$ .
@joebebel @XuyangSong any idea? IIRC, we face the similar problem as for the hash_to_curve function but I don't know how to get rid of it in this context.