deps: use constantine sha256 for codex tree hashing #1168
Merged
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
dryajov
approved these changes
Mar 21, 2025
munna0908
force-pushed
the
feat/codexTree-hasher
branch
from
7a42c8c to
70fd441
Compare
munna0908
force-pushed
the
feat/codexTree-hasher
branch
from
70fd441 to
d4db500
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.
Based on the latest benchmarks, Constantine SHA256 demonstrates excellent performance for hashing 32-byte payloads. This PR updates the CodexTree hashing algorithm by replacing mhash 256 with Constantine SHA256.