chore: bump verifiable to 1f9f6752 to match the chain rev - #29
Merged
Merged
Conversation
Aligns the pinned verifiable crate with the rev used by the Individuality runtime. Adapts the batch_validate binding to the new per-item config/members BatchProofItem API (JS signature unchanged) and updates docs/tests for the MembersCommitment size change (768 -> 288 bytes, commitment-only storage).
ryanleecode
approved these changes
Aug 3, 2026
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.
Aligns the pinned
verifiablecrate with rev1f9f6752— the rev the Individuality runtime currently builds against.Why: the client and the chain must be on the same
verifiablerev so members, aliases, proofs and ring roots stay byte-compatible; the runtime moved ahead of us.How: rev bump in
Cargo.toml/Cargo.lock, plus adapting to two upstream changes:MembersCommitmentshrinks from 768 to 288 bytes; docs and the size assertion updated. Old 768-byte roots no longer decode invalidate_with_commitment.batch_validatenow takes per-itemconfig/members. The JS-facing signature is deliberately kept one-ring-per-batch; the shared commitment is filled in per item internally.Flagged the 288-byte commitment change in the changeset (kept it
minorto match the previous rev-bump; shout if you'd rather cut a major).wasm-pack test --node: 26/26 passing.