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

verify scanned or loaded transactions match the originating psbt

Public commit record

What the developer wrote

Authored by Craig Raw

60/100 · Adequate
verify scanned or loaded transactions match the originating psbt
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
The short version

What changed, and why it matters

This commit adds a safety check in the Sparrow Wallet desktop app to make sure a transaction loaded from a file or scanned from a QR code actually matches the PSBT (a partially-signed Bitcoin transaction) that was already open. Before this change, the app would accept any transaction or PSBT from a file/scan and display it, which could mislead a user into thinking a different transaction was the one they intended to sign. The fix shows an error dialog when the loaded or scanned data does not match the original PSBT, and includes a special message for silent-payment transactions that cannot be verified from a final transaction alone.

Recommended action

Review the PSBT.matches() and possibleUnverifiableSilentPaymentsTransaction() implementations in drongo to confirm they compare all security-relevant fields (inputs, outputs, locktime, version, witness data) and cannot be bypassed by malleable fields. Also verify that the context PSBT cannot be null in security-critical flows and that the error dialogs block further action on the mismatched data.

Security signals we found

01

New integrity/matching validation between an originating PSBT and subsequently loaded or scanned transactions/PSBTs

02

User-facing error dialogs for mismatched transactions and silent-payment transactions

03

Prevention of displaying a substituted transaction as if it were the intended one

04

Special handling for silent payments where the final transaction cannot be verified against the PSBT

Risk score

Why this scored 59/100

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