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

Scope Zcash shielded signing to selected account

Public commit record

What the developer wrote

Authored by Adam Tucker

45/100 · Thin
Scope Zcash shielded signing to selected account
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes a bug in the Keystone 3 hardware wallet's Zcash shielded transaction signing. Previously, when a user reviewed and approved a transaction for one account, the device could accidentally authorize a spend from a different account controlled by the same seed. The patch now checks that every shielded spend belongs to the account the user actually selected, and rejects the transaction if any spend comes from another account. This prevents an attacker or buggy wallet software from tricking the user into signing a spend from an account they did not review.

Recommended action

Treat this as a security-relevant bug fix. Users should upgrade to the firmware version containing this commit. Wallet software interacting with Keystone should ensure it passes the correct reviewed account index to the signing path and does not rely on the unscoped raw `sign_pczt` API for user-facing transactions. Reviewers should verify that the new account checks cannot be bypassed via dummy notes or missing ZIP-32 derivation data.

Security signals we found

01

Account-scoping enforcement added to shielded spend authorization

02

Prevents cross-account signing under same seed

03

New validation in PCZT check path before signing

04

New validation in PCZT sign path during spend authorization

05

Test coverage added for rejected unselected-account spends and accepted selected-account spends

06

Changelog describes bug fix for shielded signing using non-selected account

Risk score

Why this scored 64/100

Our methodology →
Potential impact 22/30
Exploitability 12/25
Stealth signal 10/15
Affected reach 8/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.