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

Eclair v0.14.6 release (#3420)

Public commit record

What the developer wrote

Authored by Fabrice Drouin

53/100 · Thin
Eclair v0.14.6 release (#3420)

Eclair v0.14.6 release
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This commit is the release packaging for Eclair v0.14.6. The release notes explicitly state it contains 'security hardening fixes' that can be exploited by malicious nodes, and thank a researcher for responsible disclosure. The actual code changes in the commit are only version bumps and removal of a startup blocker; the security fixes themselves are not visible in this single commit. A new default setting is added that requires confirmed inputs for splicing to prevent a specific double-spend risk.

Recommended action

Treat this as a security update and upgrade to Eclair v0.14.6. Review the full v0.14.6 release notes and any associated security advisories. Ensure `require-confirmed-inputs-for-splicing` remains enabled unless there is a specific operational reason to disable it, and use RBF commands (`rbfopen`, `rbfsplice`) or raise mempool congestion settings if channel opens/splices do not confirm.

Security signals we found

01

Vendor release notes explicitly label the release as containing 'security hardening fixes' exploitable by malicious nodes

02

New default-on configuration `require-confirmed-inputs-for-splicing` mitigates unconfirmed-input double-spend risk during splicing

03

Release notes credit @erickcestari for responsible disclosures

04

Removal of an 'unsafe startup' guard that previously prevented running the snapshot build

05

Warning added against using `zero_fee_commitments` when splicing with untrusted peers

Risk score

Why this scored 74/100

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