Add Poseidon31 hasher #971
Open
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
|
This change is |
|
A potential issue with this PR is that the PR is from an organization (Bitcoin-Wildlife-Sanctuary) instead of a personal account. If it would be easy for me to resubmit this PR from a personal account (and allow edits from maintainers), please let me know and I can close this PR and open a new one. |
|
This is the accompanying Sage script for the parameters: and can be cross-checked in SageCell https://sagecell.sagemath.org/ |
weikengchen
force-pushed
the
poseidon31
branch
from
8386aa2 to
2db1f86
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 adds the Poseidon31 hasher, which is useful for recursive proof verification of a M31 proof over the M31 field.
Benchmark for proof generation suggests that the proof time is doubled when using Poseidon31 instead of Blake2s.
The Poseidon31 implementation resembles the one for Poseidon252, in that we do not use Poseidon sponge, but shapes it as a cryptographically secure hash function for compression and derivation.