Include regression tests for Poseidon gadget #2753
Draft
+354
−1
Conversation
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
This was referenced Feb 2, 2026
querolita
force-pushed
the
tests/poseidon
branch
from
d947dda to
55b71af
Compare
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 PR includes regression tests for the Poseidon gadget to check that no future update would leave us in a situation where non-fixed hash inputs can lead to the same underlying circuit. That is, to check that the hash input length is still constrained by the Snarky circuit.
It also includes some tests of what Poseidon behaves like inside the mina-signer, for similar reasons. Always have a check that the gadget is being used as expected and no forge attacks happen.
proof-systems: o1-labs/proof-systems#3467
mina: MinaProtocol/mina#18395
o1js: #2753