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

fix psbtv2 and dst related transaction editor issues around tx version and locktime

Public commit record

What the developer wrote

Authored by Craig Raw

50/100 · Thin
fix psbtv2 and dst related transaction editor issues around tx version and locktime
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes UI bugs in Sparrow Wallet's transaction editor when working with PSBT v2 (a modern format for partially-signed Bitcoin transactions) and 'DST' (likely descriptor/transaction templates). Previously, when a user changed transaction version, locktime, or input sequence numbers in the editor, the underlying PSBT object was not updated to match. This could cause the displayed/edited transaction to disagree with the actual PSBT being signed or exported, potentially leading to unexpected transaction behavior or failed signing. The patch makes the editor keep the PSBT in sync and also disables locktime controls when the form is read-only.

Recommended action

Treat as a bug-fix commit with possible security side effects. Review the corresponding drongo submodule update for any related PSBT parsing/serialization changes. Users relying on PSBT v2, locktime, or RBF/sequence editing should upgrade. No immediate exploit code is evident, but verify whether inconsistent PSBT state could be induced by editing and then signing/exporting.

Security signals we found

01

PSBT field desynchronization between UI model and serialized PSBT

02

Incorrect locktime timestamp conversion using current offset instead of zone-aware conversion

03

Locktime controls enabled on read-only transaction forms

04

Missing propagation of transaction version to PSBTv2 txVersion field

05

Missing propagation of input sequence number to PSBTv2 input sequence field

Risk score

Why this scored 35/100

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