Your signal. Your price.
Eclair’s splice fixes prevent peers from blocking on-chain HTLC enforcement with unpublishable splice transactions, conflicting transactions, or confirmed RBF replacements. Eclair now checks splice transactions before signing, retries broadcasts after conflicts, and reacts to the replacement transaction that confirms.
Eclair added checks against excessive fees in dual funding and splicing: it independently verifies Bitcoin Core-built transactions and rejects peer-proposed RBF fee rates above Eclair’s calculated maximum when Eclair pays. LND fixed 32-bit fee aggregation that could understate fees in BOLT11 invoices with blinded paths.
LDK 0.3 release candidate 2 introduces RBF fee bumping for stuck splices, defaults to negotiating anchor channels, and invalidates older Bolt 11 invoices. The LDK project has also migrated its repository off GitHub to a self-hosted mirror.
LDK release candidate 0.3 makes anchor channels the default and enables RBF fee-bumping for pending splices. LDK stable release 0.2.6 addresses a crash bug involving duplicate HTLCs and a security flaw where peers could siphon channel fees.
Eclair patched a vulnerability where malicious payment recipients could spoof intermediate routing failures to crash the node's payment lifecycle actor. The release also fixes a bug where Eclair registered incorrect MuSig2 nonces during RBF funding transaction attempts.
Keagan McClelland views restrictive mempool relay policies as unreliable tools because they diverge from consensus. Since users can submit transactions directly to miners, policies like default RBF do not offer robust protection against zero-confirmation transaction exploits.
Bitcoin Core now allows wallets to store multiple transaction variants sharing the same transaction identifier but having different witness identifiers. This allows the wallet to optimize RBF fee bumps by choosing the transaction variant with the lowest overall weight.