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

Filter prior contributions from SpliceFundingFailed events

Public commit record

What the developer wrote

Authored by Jeffrey Czyz

85/100 · Strong
Filter prior contributions from SpliceFundingFailed events

SpliceFundingFailed events return contributed inputs and outputs to the
user so they can unlock the associated UTXOs. When an RBF attempt is
in progress, inputs/outputs already consumed by prior contributions
must be excluded to avoid the user prematurely unlocking UTXOs that
are still needed by the active funding negotiation.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
The short version

What changed, and why it matters

This commit fixes a bug in the Lightning Dev Kit's splicing feature. When a user tries to resize a Lightning channel (a 'splice') and the attempt fails, the software tells the user which bitcoins (UTXOs) are no longer tied up so they can spend them again. The bug was that during a follow-up fee-bump attempt (RBF), the software could incorrectly tell the user that UTXOs from the original splice attempt were free to spend, even though they were still needed. This could lead a user to accidentally double-spend their own funds and lose money. The fix filters out any UTXOs that are still committed to an earlier splice attempt before reporting the failed ones.

Recommended action

Review the output filtering logic to confirm that script_pubkey equality is sufficient for distinguishing reusable change outputs across RBF rounds. Consider whether additional output metadata (e.g., value, position, or a unique contribution identifier) should be included to avoid over-filtering or under-filtering. Users running nodes with splicing enabled should upgrade to include this fix to avoid accidental premature UTXO unlocking.

Security signals we found

01

Incorrect UTXO unlock reporting could lead to user double-spending funds still committed to an active funding transaction

02

Fix specifically targets RBF splice scenarios where prior contributions remain pending

03

Filtering logic relies on script_pubkey equality for outputs, which may not uniquely identify outputs if the same change script is reused across rounds

04

No explicit CVE, advisory, or vendor security disclosure present in commit or references

Risk score

Why this scored 54/100

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