LDK 0.3 RC3 Expands Lightning Splicing and BOLT 12

| github.com
Rust-Lightning, also known as the Lightning Development Kit (LDK), has advanced its 0.3 release from RC2 to RC3, adding major improvements for Bitcoin Lightning Network developers and node operators. LDK 0.3 expands channel splicing with replace-by-fee (RBF) support, the ability to add and remove funds in one operation, and APIs for tracking pending splices and discarded funding transactions. Anchor channel support has also broadened, while zero-fee HTLC negotiation is now enabled by default. Older pre-anchor channels are expected to be gradually deprecated. The LDK 0.3 release adds LSPS1 support, improves LSPS2 handling, and expands BOLT 12 functionality, including payer proofs, payment metadata and offers for phantom nodes. It also improves HTLC interception, blinded payment paths, routing privacy and forwarded-payment accounting. Asynchronous signing is now available across supported ECDSA channel-signer methods. Storage and reliability upgrades include PaginatedKVStore, FilesystemStoreV2, deferred ChainMonitor writes and faster parallel monitor loading. The release fixes several channel gossip, blockchain reorganisation, funding-tracking and splicing issues. LDK 0.3 requires Rust 1.75 or later. For Bitcoin traders, this is primarily infrastructure news rather than a direct price catalyst. LDK 0.3 could support more reliable Lightning payments and improve Bitcoin’s long-term payments utility, but short-term BTC market impact is likely to be limited. Developers must review migration risks because some BOLT 11 invoices containing payment metadata, unclaimed BOLT 12 refunds and in-flight BOLT 12 payments may become incompatible across versions. Downgrades can also be restricted in cases involving pending splices, asynchronous monitoring and zero-reserve channels.
Neutral
The upgrade improves Bitcoin’s Lightning Network infrastructure, which may strengthen payment reliability, liquidity management and long-term adoption. However, LDK 0.3 is developer software rather than a change to Bitcoin’s monetary policy, network settlement rules or immediate demand for BTC. As a result, the release is unlikely to create a strong short-term price signal. Some operators may delay upgrades because of compatibility risks involving BOLT 11 invoices, BOLT 12 payments, pending splices and downgrade restrictions. That could create temporary operational caution, but it is unlikely to materially affect Bitcoin’s broader market stability. Over the longer term, successful adoption could support the Bitcoin ecosystem and payments narrative, although any price benefit would probably be gradual and difficult to separate from wider market trends. The expected direct impact on BTC is therefore neutral.