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

Send splice_locked before reestablish commitment

Public commit record

What the developer wrote

Authored by Wilmer Paulino

68/100 · Adequate
Send splice_locked before reestablish commitment

If we have pending updates to send to our counterparty on
reestablishment, while also pending a `splice_locked` send, then we must
send our `splice_locked` first as the pending updates are considering
the post-splice-locked state.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit fixes the order in which a Lightning node resends messages after reconnecting to a peer during a channel splice. Previously, if the node had both a pending 'splice_locked' message and pending commitment updates to retransmit, it could send the commitment updates first. Because those updates assume the splice has already been locked in, sending them before 'splice_locked' could confuse the peer and disrupt channel state synchronization. The fix moves 'splice_locked' ahead of commitment retransmission, and adds tests to verify the correct ordering.

Recommended action

Treat as a correctness/protocol-compliance fix. Review whether the ordering bug could lead to channel desynchronization or force-close scenarios in production; if so, include in release notes and consider backporting. No immediate emergency response is indicated by the commit alone.

Security signals we found

01

State synchronization ordering bug in Lightning channel reestablishment

02

Potential protocol violation: commitment updates referencing post-splice-locked state sent before splice_locked

03

Regression tests added to enforce message ordering

04

No explicit security advisory, CVE, or researcher attribution in commit

Risk score

Why this scored 46/100

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