This release has been named by @sangbida
Highlights for Users
- This release candidate includes a downgrade tool!
lightningd-downgradewill downgrade your database from v25.12 to v25.09 if something goes wrong - New nodes will now be created with a BIP-39 12-word phrase as their root secret. BIP-39 12-word base functionality in
lightning-hsmtoolto supporthsm_secretfiles. - We solved the case of the
missing_utxobug!! - We received great feedback about
xpayand adjusted accordingly: which will no longer try to send too many HTLCs through unknown channels (6, as that is Phoenix's limit) unless it has no choice, we've fixed a clash with simultaneous payments viaroutehintsand blinded paths and asked xpay to wait if it suspects a payment failure is due to a height disagreement with the final node. - Added
askrene-bias-node: an RPC command to set a bias on node's outgoing or incoming channels. - Use the new
networkeventssubsystem to access information about peers: ping times and connection times. - We've configured an
experimental-lsps-clientandexperimental-lsps2-servicesupport for LSPS level 2 specification.
Highlights for Developers
There's a vast array of performance improvements for large nodes... Do not pass go. Go directly to the changelog!
- Multiple significant speedups for large nodes have been added to lightningd, especially preventing "freezes" under exceptionally high load and helping it to handle large numbers of command outputs gracefully.
- Postgres: significant speedup on read-only operations (e.g. 30% on empty SELECTs)
Protocol Updates
- We now re-transmit unseen funding transactions on startup, for more robustness.
- Stricter conformance to Bolt spec for splice commitments.
See the changelog for full details
Since 25.09 we’ve had 520 commits in 92 days by 24 authors
A special thanks to our four first time contributors:
@noblepayne
@claudio.raimondi
@botantony
@wqxoxo
An enormous thanks to the very cool Core Lightning team:
@rustyrussell, @ShahanaFarooqui, @sangbida, @endothermicdev, @cdecker, @nepet, @Lagrang3, and @niftynei