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

splice: Add Bolt references and conform to them

Public commit record

What the developer wrote

Authored by Dusty Daemon

68/100 · Adequate
splice: Add Bolt references and conform to them

Adding Bolt references around `commitment_signed` logic and conforming to them.

This allows us to remove the `await_commitment_succcess` logic which was never elegant anyway, nice!

While we’re there we remove a parameter from `handle_peer_commit_sig_batch` that shouldn’t have been there anyway.

Changelog-Changed: Adding stricter conformance to Bolt spec for splice commitments.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit tightens how Core Lightning handles commitment messages during splicing (a way to resize a Lightning channel). It removes an internal 'await commitment success' flag and instead follows stricter BOLT specification rules: requiring a batch of commitment_signed messages when splices are pending, requiring a funding_txid in those messages, and failing the channel with an error if those rules are violated. The change is framed as spec conformance, but it also removes a lenient 'ignore stale commit_sig' path that previously could have let mismatched messages pass during a splice race.

Recommended action

Treat as a spec-conformance hardening change. Review that the new error paths cannot be triggered by a malicious peer to force unnecessary channel closures (griefing), and verify test coverage for single commitment_signed during pending splices, missing funding_txid, and mismatched funding_txid cases.

Security signals we found

01

Stricter BOLT conformance for splice commitment_signed handling

02

Removal of await_commitment_succcess race-tolerance flag

03

New mandatory error/fail-channel paths for malformed or incomplete commitment batches

04

Change from ignoring stale commit_sig to requiring correct funding_txid or failing the channel

05

Changelog-Changed cites Bolt spec conformance for splice commitments

Risk score

Why this scored 45/100

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