Repository navigation
Conversation
The contingency registry_script.hash was 27.5 bytes (missing a trailing 8). The on-chain hash is the correct 28-byte value; intent.json builders comparing the two abort with AnchorMismatch "registry_script.hash" (Just Contingency), blocking every contingency-flavoured operation on a fresh clone.
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
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.
One-character JSON fix in
journal/2026/metadata.json.The contingency scope's
registry_script.hashwas 27.5 bytes(missing the trailing
8):Intent builders that verify metadata against chain anchors
(amaru-treasury-tx contingency-disburse-wizard) abort with
AnchorMismatch "registry_script.hash" (Just Contingency)onevery fresh clone, blocking contingency-flavoured operations.
Verified against the live deployment ref
e7b395a93d49a17994d66df0e4778a01dee05e7711e6612f28d97b63e4e6311c#04.Related: #19.