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

Add splice-out support

Public commit record

What the developer wrote

Authored by Jeffrey Czyz

51/100 · Thin
Add splice-out support

Update SpliceContribution with a variant used to support splice-out
(i.e., removing funds from a channel). The TxOut values must not exceed
the users channel balance after accounting for fees and the reserve
requirement.
✓ Subject identifies a change✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit adds 'splice-out' support to the Lightning Dev Kit, allowing users to remove funds from an existing channel while keeping the channel open. The change introduces new code paths that handle negative contributions (removing funds) and adds checks to ensure the user cannot remove more than their channel balance after accounting for fees and reserve requirements. It is a feature addition, not a documented security fix, but it touches sensitive financial-validation logic.

Recommended action

Review the splice-out validation logic for off-by-one, rounding, and fee-estimation edge cases; complete the TODO enforcing the channel reserve minimum after splice-out; and add fuzz/negative tests for maliciously crafted output sets and feerates.

Security signals we found

01

New financial-validation function added: check_splice_contribution_sufficient

02

Splice-out allows negative contribution values, a historically sensitive code path

03

Fee estimation now includes user-controlled outputs, increasing attack surface for fee manipulation

04

Remaining TODO: 'Check that channel balance does not go below the channel reserve'

05

Error handling changed from generic 'Insufficient inputs for splicing' to more specific messages

06

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

Risk score

Why this scored 32/100

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