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

Update features early on reconnection (#3310)

Public commit record

What the developer wrote

Authored by pm47

65/100 · Adequate
Update features early on reconnection (#3310)

Otherwise some upgrade paths may fail.
✓ Descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This patch fixes the order in which Eclair updates Lightning protocol feature flags when a channel reconnects. Previously, the code built the reconnection message using stale feature information and only updated features afterward. Now features are refreshed first, so the reconnection handshake uses the correct, current capabilities. The commit message says this prevents some upgrade paths from failing. There is no direct evidence this is exploitable for theft or denial of service, but using stale feature data during a protocol handshake can cause compatibility or state-mismatch problems.

Recommended action

Treat as a correctness fix and include in the next maintenance release. Operators running nodes that use dual-funding, splicing, or taproot channels should upgrade to avoid reconnection failures or handshake inconsistencies. No immediate emergency response is indicated because the diff does not demonstrate an exploitable vulnerability, but the change should be reviewed and tested against the relevant BOLTs and upgrade scenarios.

Security signals we found

01

State variable used before update (stale feature data consumed during reconnection handshake)

02

Protocol feature negotiation ordering bug

03

Lightning ChannelReestablish TLV construction depends on freshly negotiated features

04

Potential protocol state mismatch between peers on reconnection

05

No explicit security framing in commit message or diff

Risk score

Why this scored 34/100

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