fix: poseidon2 compression didn't include feed-forward #1457
+63
−7
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
The compression function of Poseidon2 permutation differs between gnark and gnark-crypto. gnark-crypto includes right side feed-forward in the result but gnark not. This made the results differ.
Also added example test for non-default parameters to see that instance generation matches between gnark and gnark-crypto
Strangely - this was tested before but CI didn't fail? I don't see any obvious reasons, @gbotrel maybe you have ideas? I think it is somehow related which curves we test - currently the test was only for BLS12-377 as we don't have default parameters for other curves yet, but I think that for some test configuration it completely discarded testing.
Type of change
How has this been tested?
Added new test. Current test works locally. Strangely the test should have had failed in CI before, but didn't?
Checklist:
golangci-lint
does not output errors locally