chore: bump qp-poseidon-core to 3.1.0 - #2
Merged
Conversation
Align address hashing with latest poseidon-core (sponge wipe hardening).
illuzen
approved these changes
Aug 8, 2026
npm@latest now requires Node >=22; the npm bundled with Node 20 already supports lockfileVersion 3, so the upgrade step is unnecessary.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Bump
qp-poseidon-corefrom2.1.0→3.1.0so WASM address derivation tracks the latest Poseidon2 core.Transitive deps (
qp-rusty-crystals-hdwallet2.4.0 /qp-dilithium-crypto0.4.0) may still pull2.1.0until those crates are upgraded separately.