-
Notifications
You must be signed in to change notification settings - Fork 68
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
Upgrade to ark-* 0.5.0
#3047
base: albatross
Are you sure you want to change the base?
Upgrade to ark-* 0.5.0
#3047
Conversation
c2547c7
to
806410e
Compare
This allows us to drop our local patches. :)
806410e
to
af57b19
Compare
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.
You removed ToBeBytesGadget
, did we not use that?
Apart from that, LGTM
Regarding the current check failures:
- The failing web-client looks a bit like the loop unrolling problem if I'm not mistaken, but it should be fixed in 0.5 through a conditional compilation flag.
- The tests fail in the check whether we have enough signers. I already looked into it but couldn't find an obvious issue.
Also, while reviewing the failing tests, I stumbled across the following code from Bruno ( // num_signers >= min_signers
num_signers.is_cmp(&min_signers, Ordering::Greater, true) It looks to me that there's a mismatch between the comment and the code. |
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.
Also, we need to check that the upgrade did not modify any constraints that invalidate our generated ZKP keys.
There's also this issue I created wrt. the test failure: arkworks-rs/r1cs-std#151. We can probably just copy that function to our codebase without the panic.
This feature was added by 0.5.0 with the same name and same functionality, so I could just remove our
Yup on both, but maybe another loop unrolling problem appeared since then. I'll look into it.
Does that mean we need to adjust the consensus code because we can't adjust the ZKP code anymore? |
This allows us to drop our local patches. :)