Eclair updates Bitcoin Lightning funding rules

The development team behind Eclair has announced a significant update to its Bitcoin Lightning Network software aimed at tightening channel funding requirements. The change comes as a direct response to potential vulnerabilities linked to the use of unconfirmed inputs when opening payment channels. By restricting how these inputs are handled, the team hopes to improve the overall safety of the second layer payment architecture.

Historically, users could open channels using transactions that had not yet been confirmed by the Bitcoin blockchain. While this feature provided flexibility, it also created openings for malicious actors to manipulate the state of the Lightning channel. The new rules mandate that funding transactions must meet higher confirmation thresholds before the channel is considered active for routing payments. This change effectively forces users to wait for at least one confirmation on the base layer to ensure the validity of the channel opening.

This update is part of a broader effort within the Bitcoin community to harden Layer 2 solutions against edge case attacks. As the Lightning Network continues to grow in 2026, the reliance on unconfirmed inputs has been identified as a point of friction that could be exploited to lock up liquidity or disrupt payment paths. By enforcing stricter standards, Eclair aims to reduce the risk of channel closure disputes and failed payments that can occur when the underlying transaction is replaced or dropped.

Node operators are encouraged to update their software to the latest version to comply with these new security standards. Those who fail to update may find their nodes unable to open new channels with peers who have already adopted the stricter requirements. This move signifies a maturation of the Lightning ecosystem where reliability and security are prioritized over the speed of channel creation.

The Bitcoin development community has largely praised this move as a necessary step for the protocol. Although it introduces a small amount of latency for new channel setups, the trade off is considered acceptable given the importance of maintaining a reliable payment rail. Traders and developers should ensure their infrastructure is compatible with these changes to avoid any disruption in their routing capabilities during the coming weeks.