-
Notifications
You must be signed in to change notification settings - Fork 2
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
bounty: determine/fix underconstrained variables in two templates #79
Comments
@brunny-eth |
I'm on it :) |
all yours @aybanda. let us know when its ready for a review, we'll check back in a few days to see if you've made some progress 😄 |
Working my way through will update you on the progress as early as possible |
hey @aybanda, make any progress here? if not, we'll open it up to others that might be interested. let me know what you're thinking |
Bounty description
Address, explain, and, if necessary, fix underconstrained variables in the
parser-attestor
repo's circuits, specifically in theContains
operator,IsEqualArray
, and the statesum
variable.Implementation requirements
For each of the following, you must provide an example of malicious proof is before making any changes in the code!
accum
inContains
operator #34accum
inIsEqualArray
#35Resources
Circom Documentation
Comments on underconstrained variables
Criteria
Bounties will be rewarded based on the following criteria:
The text was updated successfully, but these errors were encountered: