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

give the transaction tab a copy of a wallet transaction, and leave locktimes and input sequences unchanged as the tab opens

Public commit record

What the developer wrote

Authored by Craig Raw

50/100 · Thin
give the transaction tab a copy of a wallet transaction, and leave locktimes and input sequences unchanged as the tab opens
✓ 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 a bug in the Sparrow Wallet desktop app where merely opening a transaction to view it could silently alter the wallet's stored copy of that transaction. Previously, the transaction tab shared the same in-memory object as the wallet, and the tab's user-interface setup code would overwrite locktime and input sequence values with defaults. The fix makes a defensive copy before opening the tab and only writes changes when the user actually interacts with the controls.

Recommended action

Users should upgrade to a Sparrow Wallet release that includes this commit. Until then, avoid opening the transaction tab for transactions whose locktime or sequence settings must remain unchanged, and verify transaction details before signing or broadcasting. Developers should audit other controllers for similar shared-object mutation patterns during view initialization.

Security signals we found

01

UI initialization code mutates shared transaction object before user interaction

02

Wallet transaction object and transaction-tab object were the same reference

03

Locktime and input sequence defaults could overwrite user/wallet-defined values on tab open

04

Defensive deep copy added to separate wallet state from UI state

05

Regression test added to enforce isolation between viewed and wallet transaction copies

Risk score

Why this scored 61/100

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