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

Produce FundingInfo::Contribution variants in ChannelMonitor

Public commit record

What the developer wrote

Authored by Wilmer Paulino

73/100 · Adequate
Produce FundingInfo::Contribution variants in ChannelMonitor

Similar to the `ChannelManager`, we expose the contributed inputs and
outputs of a splice via `FundingInfo::Contribution` at the
`ChannelMonitor` level such that we don't lose the context when the
channel closes while a splice is still pending. This relies on tracking
the `FundingContribution` that was provided to the `ChannelManager`
prior to negotiating the new funding transaction. If no
`FundingContribution` exists, then we continue to emit the
`FundingInfo::OutPoint` variant.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit improves how the Lightning Dev Kit node keeps track of funds involved in a 'splice' (a way to resize a Lightning channel while it is open). Previously, if the channel closed while a splice was still pending, the wallet only received a generic reference to the old funding transaction. Now it receives the actual inputs and outputs the user contributed, making it easier to recover those funds safely. The change is a feature completeness / robustness improvement rather than a fix for an active exploit.

Recommended action

Treat as a normal code-review item. Verify that the new serialization fields are optional and that downgrades/upgrades across versions do not lose the contribution data. Confirm that the test coverage exercises both the Contribution and OutPoint DiscardFunding paths. No urgent security response is indicated.

Security signals we found

01

Data-loss / wallet-recovery robustness: richer DiscardFunding events reduce the chance that user funds from a splice contribution become unrecoverable after an unexpected channel close.

02

Serialization schema change: new optional TLV fields (7 in RenegotiatedFunding, 13 in FundingScope, 41 in ChannelMonitor) preserve backward compatibility.

03

No input validation changes: the patch relies on the existing FundingContribution logic and does not introduce new parsing of untrusted data.

04

No privilege boundary or remote-triggerable code path is added.

Risk score

Why this scored 24/100

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