AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 27 Bitcoin

Bump Zcash deps to Ironwood revisions + mechanical API migrations

Public commit record

What the developer wrote

Authored by Adam Tucker

83/100 · Strong
Bump Zcash deps to Ironwood revisions + mechanical API migrations

Pin the Zcash crates to the Ironwood fork revisions (orchard via
zcash/orchard, the zcash_*/pczt crates via the valargroup fork) using
[patch.crates-io], enable the zcash_unstable="nu6.3" cfg, and apply the
mechanical API migrations the bump forces:

- TransparentAddress::from_script_from_chain / from_script_pubkey
- Note::from_parts note-version argument, SignableInput::from_parts
- pczt_ext ZIP-244 sighash digest adjustments

Tests embedding the old PCZT wire format or the pre-bump builder API are
dropped here (they no longer parse/compile); equivalents against the new
API are restored with the Ironwood feature in the following commit.

NOTE: this commit does not build in isolation. The parse.rs/sign.rs API
migrations are interleaved with the Ironwood parsing/signing changes and
land together in the next commit; this is split out purely to isolate
the dependency bump for review.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit updates the Zcash-related Rust libraries inside the Keystone 3 firmware to newer versions. It also makes small code changes so the firmware keeps compiling with the new library APIs, removes some old tests that no longer work with the new wire format, and adjusts how transaction hashes are computed. The commit itself is described by its author as not building in isolation; the remaining matching changes are in the next commit. There is no direct evidence in the commit that this fixes or introduces a security vulnerability.

Recommended action

Review this commit together with the following commit that completes the Ironwood parsing/signing changes, because this commit does not build or pass tests in isolation. Verify that the ZIP-244 sighash changes and transparent address handling remain semantically equivalent, and that the removed anti-spoofing and malformed-bundle tests are restored against the new PCZT API. Confirm the Git-pinned Zcash forks match expected upstream revisions and have not introduced unexpected changes.

Security signals we found

01

Dependency bump to major new revisions of Zcash cryptographic crates

02

Switch from crates.io releases to Git-pinned forks (valargroup/librustzcash and zcash/orchard)

03

ZIP-244 sighash digest code changes in pczt_ext.rs

04

Removal of existing unit tests covering PCZT parsing, signing, and anti-spoofing checks

05

Commit explicitly does not build in isolation

Risk score

Why this scored 27/100

Our methodology →
Potential impact 5/30
Exploitability 5/25
Stealth signal 5/15
Affected reach 5/15
Confidence 4/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.