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

include unconfirmed wallet descendant fees when increasing a transaction fee, advise the replaced fees plus relay cost on rejection, and allow a cpfp child to be replaced

Public commit record

What the developer wrote

Authored by Craig Raw

50/100 · Thin
include unconfirmed wallet descendant fees when increasing a transaction fee, advise the replaced fees plus relay cost on rejection, and allow a cpfp child to be replaced
✓ 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 how Sparrow Wallet calculates fees when you speed up or replace a Bitcoin transaction. Previously, if your wallet had unconfirmed follow-up transactions (like a CPFP child) that depended on the transaction being replaced, the wallet did not count their fees toward the replacement cost. That could cause the replacement to be rejected by the network for paying too little. The fix also improves the error message so users are told the correct minimum fee to use next time, and it allows a CPFP child that pays to a change address to be treated as a consolidation output when bumping fees.

Recommended action

Users who perform RBF fee bumps on transactions with unconfirmed child transactions should upgrade. The change is defensive and improves reliability rather than fixing a remote exploit, but it prevents stuck or rejected replacements and misleading fee guidance.

Security signals we found

01

RBF fee-bumping calculation omitted unconfirmed descendant fees, risking insufficient-fee rejection

02

User-facing error message previously could understate the fee required to successfully replace a transaction

03

CPFP child output to change address was not treated as consolidation, potentially affecting input selection during fee bump

04

Fee parsing changed from truncation to rounding, reducing small under-advisement errors

Risk score

Why this scored 33/100

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