Skip to content

feat(zcash): forward Ironwood PCZT metadata - #57

Closed
BitHighlander wants to merge 1 commit into
masterfrom
agent/zcash-ironwood
Closed

feat(zcash): forward Ironwood PCZT metadata#57
BitHighlander wants to merge 1 commit into
masterfrom
agent/zcash-ironwood

Conversation

@BitHighlander

Copy link
Copy Markdown
Collaborator

Why

The device must receive the selected Orchard-family pool and all five transaction-v6 component digests. Without these fields, firmware cannot safely authorize an Ironwood transaction.

What changed

  • forward pool as the protocol shielded-pool selector
  • forward digests.ironwood
  • handle the new enum export in the message registry
  • update shield/deshield fixtures to NU6.3 transaction v6 and assert exact wire fields
  • stage the device-protocol 7.17.0 dependency

Validation

  • yarn tsc --build packages/hdwallet-keepkey/tsconfig.json — passed against the generated 7.17.0 protocol
  • focused Zcash Jest suite — 5/5 passed

Dependency

@vercel

vercel Bot commented Jul 30, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
hdwallet-sandbox Error Error Jul 30, 2026 7:13pm

Request Review

@BitHighlander

Copy link
Copy Markdown
Collaborator Author

Closing this staging attempt because it depended on an unpublished fork-scoped protocol package. The Ironwood firmware release is following the upstream-first SOP with keepkey/device-protocol#113 and keepkey/python-keepkey#200 at the canonical protocol pin f2246cebea8f96fcd7ec2883588a784a60b430ae. Any JS consumer follow-up will be rebuilt against the canonical upstream package, not a fork pin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant