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.
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.
Bitcoin Optech’s Oct. 9 newsletter highlighted both changes as closing protection gaps during dual funding and splicing.
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.
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.
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.
Keeping keys is only part of the defense
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.
A compromised backend could report a fee within budget while constructing a transaction that actually paid more, including by dropping the change output. Under Bitcoin’s transaction accounting, input value not assigned to outputs becomes a miner fee. Missing change can therefore spend funds without paying an attacker’s address.
When a fee budget is supplied, the repair calculates the actual fee from the amounts of the coins being spent, fetched by transaction ID to authenticate their values. It checks that the backend’s reported fee matches and applies the budget to the actual fee. It also checks that Eclair’s rebuilt contributions pay the same verified fee and rejects invalid change-output positions.
These are distinct from the cooperative-closing fee flaw covered in CryptoSlate’s September report and the restart denial-of-service issues covered Oct. 2.
These repairs address Eclair’s dual-funding, splicing and signer configurations. Operators should check that their installed build contains the October changes.
