Eclair Tightens Bitcoin Funding Rules for Lightning Network Nodes

Bitcoin Lightning developer ACINQ has strongly encouraged node operators to update their software after resolving security vulnerabilities that could be leveraged by malicious peers. The company rolled out Eclair version 0.14.6, bringing in stricter transaction mandates and recovery protocols designed to stop manipulated channel funding from putting pending payments at risk.

For anyone looking into eclair bitcoin software, this update centers on a flaw regarding how Lightning channels process funding alterations before the underlying Bitcoin transactions achieve network confirmation. While the Lightning network allows users to route Bitcoin through payment channels without logging every action on the blockchain, and lets operators adjust liquidity via splicing, accepting unconfirmed funding inputs introduces manipulation risks. A malicious counterpart could double-spend an unconfirmed transaction following a splice, thus invalidating the funding setup supporting the channel.

Should an impacted channel close on the Bitcoin blockchain subsequently, conditional contracts known as HTLCs securing pending payments could become vulnerable. Although developers highlighted a potential security exposure instead of actual confirmed theft, the true scale of any real-world exploitation remains unknown.

ACINQ urges Eclair node operators to upgrade after fixing security weaknesses affecting channel funding.

Protecting Channel Splicing

The software update deploys a new security control mandating confirmed inputs from peers prior to contributing funds to channel splices. Enabled by default, this safeguard also stops operators from building extra splices on unconfirmed funding shifts. Additionally, developers refined responses when channels close while funding transactions remain unconfirmed, ensuring Eclair selects a commitment transaction recognized by its Bitcoin Core backend and reverts to the latest confirmed funding state when needed.

Another correction resolves a potential loss scenario where miners confirm transactions after Eclair stops tracking them as preferred routes. The updated logic detects such transactions and attempts to recover corresponding outputs. ACINQ also reminded operators to avoid optional zero-fee commitment features when splicing with untrusted peers, and credited security researcher Erick Cestari for responsibly disclosing the addressed issues.

Why it matters

This release alters how Lightning node operators handle funding security and splicing operations. By making confirmed peer inputs the default requirement and improving channel closure recovery, the update directly impacts node security and protects pending payments from malicious disruption.