Why did Eclair change its Bitcoin funding rules for Lightning Network splices?

ACINQ's Eclair implementation now requires confirmed peer inputs for splicing by default to prevent payment failures caused by unconfirmed transactions. This October 2026 update enhances Lightning Network stability by ensuring channel capacity adjustments are backed by settled on-chain data.
Why did Eclair change its Bitcoin funding rules for Lightning Network splices?

ACINQ updated the Eclair Bitcoin funding rules to mitigate risks associated with unconfirmed inputs, which were previously causing Lightning Network payments to fail or hang. By requiring confirmed peer inputs for splices by default in its October 27, 2026 release, Eclair ensures that channel capacity adjustments—adding or removing funds—are backed by settled on-chain transactions. This shift significantly reduces the likelihood of payment disruptions and prevents vulnerabilities where a single stalled parent transaction could freeze entire channel operations.

Splicing has become a critical feature for Bitcoin’s scalability, allowing users to resize channels without the cost and downtime of a full closure. However, relying on unconfirmed inputs created a 'chain of trust' that could easily break if a transaction was dropped from the mempool or replaced via Replace-By-Fee (RBF). The new Eclair release also introduces improved recovery mechanisms for nodes forced to close channels while funding is still pending, providing a necessary safety net for liquidity providers and high-volume routing nodes operating in a congested fee environment.

In the current 2026 landscape, Bitcoin’s Layer 2 ecosystem is maturing toward more robust, 'security-first' architectures. While requiring confirmations for splicing may slightly increase the time required to adjust channel liquidity, it protects US-based node operators and institutional users from malicious or accidental disruptions. This update reflects a broader industry trend toward prioritizing transaction finality over instant but fragile liquidity adjustments.

For businesses and individual node operators using Eclair, this update necessitates a slight shift in liquidity management strategies, as they can no longer rely on 'zero-conf' inputs for immediate splicing. Investors and developers should watch for similar updates from other major Lightning implementations like LND or Core Lightning. If 'confirmed-only' splicing becomes the network-wide standard, it will likely lead to a more stable, albeit slightly slower, user experience for Bitcoin scaling solutions throughout late 2026.

Editorial method

This report is based on the linked source and is labeled with its publication date, provider, category and market-impact assessment. Market interpretation is informational, not investment advice.