-
Notifications
You must be signed in to change notification settings - Fork 217
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
R1CS -> BP without using matrices [WIP] #131
Conversation
src/circuit_proof/examples.rs
Outdated
val_in_1: Scalar, | ||
val_out_0: Scalar, | ||
val_out_1: Scalar, | ||
) -> (ConstraintSystem, Scalar) { |
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.
If the merge block is a circuit gadget, shouldn't it take a &mut ConstraintSystem
as an input rather than returning one that it created? Since we don't have a way to combine constraint systems (and I don't think there's a good way to do that), doesn't constructing internally and returning the ConstraintSystem
prevent joining two merge gadgets?
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.
yeah that definitely makes more sense - fixed!
Closing: moving work to this PR: |
TODO: update
LinearConstraint
so it uses a commitment to 1 instead of requiring a separate scalar?