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

Create fresh shutdown nonce on reconnection (#3184)

Public commit record

What the developer wrote

Authored by Bastien Teinturier

93/100 · Strong
Create fresh shutdown nonce on reconnection (#3184)

When we disconnect after sending `shutdown`, we must re-send `shutdown`.
When using taproot, we must generate a fresh nonce and store the private
nonce locally, otherwise we won't be able to create our `closing_sig`.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This patch fixes a bug in the Eclair Lightning node that occurs when a channel is closing using the newer Taproot channel type and the connection drops after a shutdown message was sent. On reconnection, the node must resend shutdown, but it was reusing an old cryptographic nonce. For Taproot, each shutdown needs a fresh nonce, and the node must keep the matching private nonce to later sign the closing transaction. Without the fix, the node could be unable to produce its closing signature after reconnecting, potentially stalling or complicating mutual channel closure.

Recommended action

Apply the patch. Ensure nodes running Taproot channels are upgraded, as the bug can prevent successful closing signature creation after a reconnection during shutdown. Monitor for any stuck closing negotiations and consider alerting peers to upgrade if mutual close stalls.

Security signals we found

01

Taproot channel close nonce reuse bug fixed

02

Reconnection shutdown retransmission now regenerates shutdown instead of replaying stale message

03

Private nonce storage dependency for closing_sig creation

04

Test coverage added for fresh nonce on reconnection and successful closing transaction publication

Risk score

Why this scored 59/100

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