Acir format failing for certain range constraints#267
Closed
vezenovm wants to merge 40 commits into
Closed
Conversation
…nge constraint < 8 bits.
…nberg into mv/ultra-range-dbg
pedersen hash test now checks y coordinate
wasm code path was not correctly storing fft outputs in proving key
stdlib method is utility method to provide Composer-agnostic interface due to the use of plookup tables if enabled
Updated ReadMe to include wasm example that supports gtest filtering
…nberg into mv/ultra-range-dbg
11 tasks
This file contains hidden or 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.
Description
Debug PR to show how acir_format creates unsatisfiable circuits when dealing with witnesses that are not used in any arithmetic constraints but need to be range constrained.
Checklist:
/markdown/specshave been updated.@briefdescribing the intended functionality.