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

feat(zcash): use raw firmware version in ZcashAccounts pairing QR

Public commit record

What the developer wrote

Authored by Adam Tucker

85/100 · Strong
feat(zcash): use raw firmware version in ZcashAccounts pairing QR

Switch from GetSoftWareVersionNumber() (display major, flavor suffix) to
the raw [MAJOR, MINOR, BUILD] formatted inline, so the pairing string
matches the byte-level stamp produced by the PCZT signer. Wallets can
now use a single minimum-version constant for both checks.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit changes how the Keystone hardware wallet reports its firmware version when pairing with Zcash wallets. Previously it used a function that returned a display-formatted version string (with a flavor suffix). Now it formats the raw major/minor/build numbers directly. The goal is to make the pairing QR code's version string match the version bytes stamped by the PCZT signer, so wallets can use one consistent minimum-version check. There is no direct security vulnerability in the diff itself; it is a compatibility/consistency fix.

Recommended action

Treat as a normal feature/compatibility commit. No security response required. If desired, verify that downstream Zcash wallets correctly parse the new raw version format and that the SOFTWARE_VERSION_* macros are consistently maintained.

Security signals we found

01

No buffer overflow: snprintf with sizeof(firmwareVersion) bounds output

02

No change to cryptographic material or key handling

03

No change to authorization or trust assumptions

04

Potential minor risk if version parsing on wallet side is sensitive to format, but commit explicitly aims to reduce format mismatch

05

No secrets, keys, or randomness introduced

Risk score

Why this scored 19/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 3/15
Confidence 8/10
Evidence quality 4/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.