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

verify payjoin receiver input signatures against their declared utxos before checking the proposal fee

Public commit record

What the developer wrote

Authored by Craig Raw

60/100 · Adequate
verify payjoin receiver input signatures against their declared utxos before checking the proposal fee
✓ 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 fixes a security gap in Sparrow Wallet's Payjoin handling. Payjoin lets a receiver add their own bitcoin inputs to a transaction you are sending. Before this change, Sparrow could be tricked into accepting a Payjoin proposal where the receiver's claimed coins were not properly signed, or where the receiver hid the real previous transaction for old-style (non-Segwit) inputs. The change makes Sparrow verify the receiver's signatures against the exact coins they declared, and it rejects proposals that omit required data for non-Segwit inputs. This closes a path where a malicious or buggy payjoin server could make the sender pay more fees or include invalid inputs.

Recommended action

Treat this as a security fix and include it in the next release. Users who initiate Payjoin transactions should upgrade. Review the drongo submodule changelog for related PSBT verification changes. Consider whether any prior release allowed Payjoin proposals to bypass these checks and assess if a security advisory is warranted.

Security signals we found

01

Payjoin receiver input signature verification added before fee check

02

Mandatory non_witness_utxo enforcement for non-Segwit receiver inputs

03

New test: receiver input signed for different amount is rejected

04

New test: non-Segwit receiver input missing non_witness_utxo is rejected

05

New test: Taproot receiver input verified after original UTXOs filled

06

drongo submodule updated, likely providing signature verification primitives

Risk score

Why this scored 76/100

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