{"id":14389,"date":"2026-10-12T16:25:47","date_gmt":"2026-10-12T16:25:47","guid":{"rendered":"https:\/\/cryptonews.uk.com\/?p=14389"},"modified":"2026-10-12T16:25:47","modified_gmt":"2026-10-12T16:25:47","slug":"eclair-fee-fixes-target-lightning-funding-losses","status":"publish","type":"post","link":"https:\/\/cryptonews.uk.com\/?p=14389","title":{"rendered":"Eclair fee fixes target Lightning funding losses"},"content":{"rendered":"

<\/p>\n

\n

Eclair, ACINQ’s Lightning node software, has merged two repairs for gaps that could make a node lose Bitcoin through excessive mining fees during channel funding and splicing. One limits a peer’s fee-bump demands when Eclair contributes funds; the other checks transactions from a compromised Bitcoin backend while Eclair retains the signing keys.<\/p>\n

The repairs merged into the project’s master branch on Oct. 2 and Oct. 5. As of Oct. 12, its release page still listed September’s v0.14.3 as latest. The two October fixes postdate that packaged release.<\/p>\n

Bitcoin Optech’s Oct. 9 newsletter highlighted both changes as closing protection gaps during dual funding and splicing.<\/p>\n

\n

Related Reading<\/span><\/p>\n

A Bitcoin Lightning flaw could send a node\u2019s entire balance straight to miners<\/h3>\n<\/p>\n

<\/span> <\/div>\n

The first repair, PR #3388, concerns peer-initiated replace-by-fee, or RBF, attempts during a dual-funded channel opening or a splice that adjusts a channel’s funding. A peer could request a replacement transaction with a higher fee rate. Eclair kept its wallet contribution and paid for its inputs at that rate, without an upper bound or fee budget on this path.<\/p>\n

That let a malicious peer impose an arbitrary mining fee rate on the contributing node while contributing nothing itself. The loss would be paid as fees to miners rather than transferred directly to the peer.<\/p>\n

The repair rejects attempts above the maximum funding fee rate Eclair recommends to its peer. Two exceptions remain: the peer buys liquidity and pays the fees for Eclair’s inputs, or the Eclair node contributes no funds to the transaction. In those cases, Eclair does not bear the cost addressed by this limit.<\/p>\n

\"Diagram\"Diagram<\/p>\n

Keeping keys is only part of the defense<\/h2>\n

PR #3390 addresses a separate threat in Eclair-signer mode. Bitcoin Core’s backend, bitcoind, selects coins and builds transactions, while Eclair retains the keys and signs.<\/p>\n