feat(zcash): add Ironwood signing metadata - #113
Merged
Conversation
This was referenced Jul 30, 2026
BitHighlander
force-pushed
the
agent/zcash-ironwood-develop
branch
from
July 30, 2026 19:26
16f1e5d to
f2246ce
Compare
BitHighlander
marked this pull request as ready for review
July 30, 2026 19:42
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
1 participant
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.
Why
NU6.3 activates transaction v6 and the Ironwood pool. Hosts must tell firmware which Orchard-family pool is being signed and provide the fifth ZIP-229 component digest.
What changed
shielded_poolandironwood_digesttoZcashSignPCZTThe new tags are additive (
19and20); existing v5 Orchard messages remain wire-compatible.Validation