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

Always emit SpliceNegotiationFailed when contributing

Public commit record

What the developer wrote

Authored by Wilmer Paulino

73/100 · Adequate
Always emit SpliceNegotiationFailed when contributing

Previously, this could result in an acceptor not receiving a
`Event::SpliceNegotiationFailed` for a splice in which they reused the
same contribution (except for the feerate change). Our API should
guarantee that users should always see `SpliceNegotiated` and
`SpliceNegotiationFailed` events for splices that they contribute to.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This patch fixes a bug in Lightning Dev Kit's splicing feature where a channel participant (the 'acceptor') could fail to receive a notification when a splice negotiation they contributed to fell through. Without that notification, the user's wallet software would not know it could safely unlock and reuse the funds it had set aside for the splice. The fix ensures both sides always get a SpliceNegotiationFailed event when a splice they contributed to fails, even if their exact same inputs/outputs were reused from a previous round.

Recommended action

Treat as a reliability/UX bug fix rather than a critical security vulnerability. Users relying on splicing should upgrade so wallets correctly receive SpliceNegotiationFailed events and can resume funding. No immediate emergency response is indicated.

Security signals we found

01

API guarantee violation: missing failure event for one party

02

Potential wallet-level fund unavailability / UX degradation

03

No cryptographic flaw or remote code execution vector

04

Fix is localized to splicing state-machine event emission

Risk score

Why this scored 32/100

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