test: add test vectors for R1CS to detect circuit breakage #66
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 was created for debugging why tests are failing against mainnet proving and verification keys in penumbra-zone/penumbra#4927
Similar to penumbra-zone/decaf377#110
This PR:
parameter-setuptool in the penumbra monorepo)The benefit of this is that if a dependency is updated that changes the circuits, we'll detect it with these tests. We have similar tests in the penumbra monorepo but it would be nice to have them in all the crypto dependencies with R1CS gadgets so we can more easily identify which changes are causing the breakage.