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

splice: track funding_tx_index on inflights and channel funding

Public commit record

What the developer wrote

Authored by Níckolas Goline

73/100 · Adequate
splice: track funding_tx_index on inflights and channel funding

Give every funding tx a stable index: 0 for the original funding
(including RBF attempts), incrementing by 1 per splice. Threaded through
the channeld inflight, the channel, the channeld_init and
channeld_add_inflight wire messages, set on splice creation and carried
onto the channel funding when a splice locks, and persisted in the
channel_funding_inflights and channels tables. A splice inflight
pending across the upgrade is migrated to index 1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit adds a stable counter, called funding_tx_index, that tracks whether a Lightning channel is on its original funding transaction (index 0) or on a later splice (index 1, 2, etc.). It stores the index in memory, passes it between daemon processes, and saves it in the wallet database. The change is a correctness fix for how Core Lightning handles reconnections and retransmissions after a splice, but the commit itself is a feature/infrastructure patch rather than a direct fix for an active exploit.

Recommended action

Treat as a correctness improvement with latent security relevance for splice handling. Review whether any remaining code paths still identify a channel solely by funding txid instead of the (channel_id, funding_tx_index) pair, especially around reconnection, watchtower/penalty logic, and database lookups. No immediate emergency patch is indicated, but operators using splicing should upgrade to avoid reconnection edge cases.

Security signals we found

01

Adds persistent funding_tx_index to distinguish original funding from splice funding after channel funding txid changes

02

Removes xfail markers on splice reconnection tests, implying prior incorrect behavior on reestablish after splice lock

03

Updates database migrations to backfill index=1 for pending splice inflights across upgrade

04

Touches wire protocol messages (channeld_init, channeld_add_inflight) to propagate the new field

Risk score

Why this scored 33/100

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