Add 0.2 changelog (and quick missing spliec doc) #4163

TheBlueMatt · 2025-10-16T15:37:26Z

Note that this is against main so will need to be backported.

ldk-reviews-bot · 2025-10-16T15:37:29Z

I've assigned @joostjager as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

codecov · 2025-10-16T15:47:05Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.86%. Comparing base (05f2848) to head (a94f9f8).
⚠️ Report is 96 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4163      +/-   ##
==========================================
+ Coverage   88.78%   88.86%   +0.07%     
==========================================
  Files         180      180              
  Lines      137004   137901     +897     
  Branches   137004   137901     +897     
==========================================
+ Hits       121642   122543     +901     
- Misses      12538    12545       +7     
+ Partials     2824     2813      -11

Flag	Coverage Δ
fuzzing	`21.44% <100.00%> (+0.48%)`	⬆️
tests	`88.70% <100.00%> (+0.07%)`	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

CHANGELOG.md

joostjager

I was assigned by the bot, but as @TheBlueMatt mentioned in the meet, everyone should really check their contributions here.

NIce concise changelogs

CHANGELOG.md

joostjager · 2025-10-17T07:51:59Z

lightning/src/events/mod.rs

-	/// initialized with
+	/// Indicates that an onion message supporting peer has come online and any messages previously
+	/// stored for them (from [`Event::OnionMessageIntercepted`]s) should be forwarded to them by
+	/// calling [`OnionMessenger::forward_onion_message`].


Good addition, wasn't clear indeed that forward_onion_message needs to be called.

joostjager · 2025-10-17T07:55:20Z

CHANGELOG.md

+
+## API Updates
+
+ * Splicing is now supported. The current implementation is expected to be


Curious why it says "expected". Isn't interop confirmed?

We have not had time to do interop testing, no. We will likely do some before the release but probably not a ton.

CHANGELOG.md

joostjager · 2025-10-17T08:09:34Z

CHANGELOG.md

+   `UserConfig::reject_inbound_splices` can be set to block inbound ones (#4150)
+ * LDK now requires the `channel_type` feature in line with spec updates (#3896)
+
+XXX release stats


Reminder to update. Maybe XXX is part of the process?

Yea, will do it once we get the other PRs landed.

joostjager · 2025-10-17T08:20:13Z

CHANGELOG.md

@@ -1,3 +1,154 @@
+# 0.2 - XXX, 2025 - "Natively Asynchronous Splicing"


Would it be nice to add a bit of a sales pitch here? Example AI slop:

LDK 0.2 – “Natively Asynchronous Splicing” is here, delivering the future of Lightning development today. Splicing support has landed, letting you resize channels on the fly, with native async APIs across the stack for faster, cleaner, and more efficient operations. Async payments are now live too, enabling smoother BOLT 12 flows for often-offline users and LSPs. Zero-Fee-Commitment channels slash feerate headaches, while new LSPS and RGS features power next-gen liquidity and performance. With major speed boosts, deeper diagnostics, and smarter persistence, LDK 0.2 is your all-in-one upgrade for a faster, more flexible Lightning future.

We historically haven't, letting the API Updates section speak for itself (its roughly sorted in "importance" order so splicing and async and async payments are right at the top). We did for 0.1 just given we were starting to do backports and wanted to describe that. We do use this kinda pitch for the release announcement tho.

CHANGELOG.md

TheBlueMatt · 2025-10-29T23:50:09Z

Okay, went ahead and squashed with the following changes, I think we can go ahead and land this as draft release notes, backport it, and we'll be about ready for an 0.2-rc.

$ git diff-tree -U1 a5acf3c27 b2d9dacf81
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8614fc6948..b4839d6423 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,2 +1,2 @@
-# 0.2 - XXX, 2025 - "Natively Asynchronous Splicing"
+# 0.2 - TODO: Add release date, 2025 - "Natively Asynchronous Splicing"

@@ -39,5 +39,8 @@
    force-closure risk for feerate disagreements by using a fixed, zero fee on
-   presigned transactions, relying on anchor bumps instead. This only works with
-   LDK peers, and feature signaling may change in a future version of LDK,
-   breaking compatibility. This is negotiated automatically for
+   presigned transactions, relying on anchor bumps instead. They also utilize
+   the new TRUC + ephemeral dust policy in Bitcoin Core 29 to substantially
+   improve the lightning security model. This requires having a path of Bitcoin
+   Core 29+ nodes between you and a miner for transactions to be mined. This
+   only works with LDK peers, and feature signaling may change in a future
+   version of LDK, breaking compatibility. This is negotiated automatically for
    manually-accepted inbound channels and negotiated for outbound channels based
@@ -94,2 +97,7 @@
  * `lightning-liquidity` now supports persisting relevant state (#4059, #4118).
+ * `ChannelManager::funding_transaction_generated_manual_broadcast` was added to
+   open a channel without automatically broadcasting the funding transaction
+   (#3838). In it and `unsafe_manual_funding_transaction_generated`
+   force-closure logic has been updated to no longer automatically broadcast the
+   commitment tx unless the funding transaction has been seen on-chain (#4109).
  * Various instances of channel closure which provided a
@@ -134,2 +142,5 @@
    `ListProtocols` message (#3785).
+ * A rare race which might lead `PeerManager` (and `lightning-net-tokio`) to
+   stop reading from a peer until a new message is sent to that peer has been
+   fixed (#4168).
  * The fields in `SocketAddress::OnionV3` are now corectly parsed, and the
@@ -168,3 +179,3 @@

-XXX release stats
+TODO release stats

CHANGELOG.md

tankyleo

This just crossed my mind: should we mention the new max_tx_weight parameter on CoinSelectionSource::select_confirmed_utxos in API Updates ?

CoinSelectionSource::select_confirmed_utxos now has a max_tx_weight parameter that specifies the maximum allowed weight of the final transaction (#4129). This parameter is only expected to put a real constraint on UTXO selection in zero-fee commitment channels."

TheBlueMatt · 2025-10-30T12:55:50Z

This just crossed my mind: should we mention the new max_tx_weight parameter on CoinSelectionSource::select_confirmed_utxos in API Updates ?

We often (especially in this release cause the docs are so huge) skip documenting things that will result in a compilation error due to a changed API. I think its fine to do in this case.

TheBlueMatt · 2025-10-30T18:58:35Z

Backporting to 0.2 in #4193

TheBlueMatt · 2025-10-30T21:07:02Z

Updated the blinded message path dummy hops note and moved it out of "bug fixes":

$ git diff-tree -U1 b2d9dacf81 19fd54f525
diff --git a/CHANGELOG.md b/CHANGELOG.md
index b4839d6423..513a026f62 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -92,2 +92,4 @@
    `KVStore` to restore custom logic for specific storage objects (#3905).
+ * `BlindedMessagePath::new_with_dummy_hops` was added (but is not used by
+   default, #3726). You can use `NodeIdMessageRouter` to enable dummy hops.
  * `ProbabilisticScoringFeeParameters::probing_diversity_penalty` was added to
@@ -150,4 +152,2 @@
    marginally when forwarding gossip to a slow peer (#4093, #4096).
- * `BlindedMessagePath::new_with_dummy_hops` was added (but is not used by
-   default, #3726).
  * Blinded path serialization is now padded to better hide its contents (#3177).

jkczyz · 2025-10-30T21:15:29Z

lightning/src/ln/channelmanager.rs

+	/// After initial signatures have been exchanged, if we contributed any inputs,
+	/// [`Event::FundingTransactionReadyForSigning`] will be generated and
+	/// [`ChannelManager::funding_transaction_signed`] should be called.


We will emit this if we contributed either any non-shared inputs or any outputs. @wpaulino I can't recall why we emit this event for splice-out. In that case, we wouldn't have any inputs to sign because the shared input signing is handled by LDK.

With splice-out, it's more so to let the user have one last chance to approve the splice based on the negotiated transaction.

So if the user is calling splice_channel to initiate we'll always emit it, right? Cause we'll always contribute some input or output.

Correct. Once we allow contributions on incoming splices, an event should also be there if the user contributes anything.

CHANGELOG.md

`ChannelManager::splice_channel` initiates a splice which ultimately generates a series of events. The most important of which, `FundingTransactionReadyForSigning` (which must always be handled, unlike the others), was not documented. Here we mention the event generation.

Users implementing the "onion message mailbox" feature and handling `OnionMessageIntercepted` events need to also handle `Event::OnionMessagePeerConnected` events. Here we update the event docs for both to add additional references and be more explicit about what implementors need to do.

TheBlueMatt · 2025-10-30T21:40:47Z

Addressed further feedback:

$ git diff-tree -U2 19fd54f52 f36560d96
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 513a026f62..517102954e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -169,7 +169,7 @@
    often offline peer to come online (#3918).
  * Blinded message paths generated by previous versions of LDK, except those
-   generated for inclusion in `Bolt12Offer`s will no longer be accepted. As most
-   blinded message paths are ephemeral, this should only invalidate issued
-   `Refund`s in practice (#3917).
+   generated for inclusion in BOLT 12 `Offer`s will no longer be accepted. As
+   most blinded message paths are ephemeral, this should only invalidate issued
+   BOLT 12 `Refund`s in practice (#3917).
  * Once a channel has been spliced, LDK can no longer be downgraded.
    `UserConfig::reject_inbound_splices` can be set to block inbound ones (#4150)
diff --git a/lightning/src/ln/channelmanager.rs b/lightning/src/ln/channelmanager.rs
index 515d7dbd14..a77f086c53 100644
--- a/lightning/src/ln/channelmanager.rs
+++ b/lightning/src/ln/channelmanager.rs
@@ -4682,7 +4682,6 @@ where
 	/// [`Event::DiscardFunding`] is seen.
 	///
-	/// After initial signatures have been exchanged, if we contributed any inputs,
-	/// [`Event::FundingTransactionReadyForSigning`] will be generated and
-	/// [`ChannelManager::funding_transaction_signed`] should be called.
+	/// After initial signatures have been exchanged, [`Event::FundingTransactionReadyForSigning`]
+	/// will be generated and [`ChannelManager::funding_transaction_signed`] should be called.
 	///
 	/// If any failures occur while negotiating the funding transaction, an [`Event::SpliceFailed`]

CHANGELOG.md

tankyleo

Two small typos, take them or leave them :)

TheBlueMatt · 2025-10-30T21:46:19Z

Ugh, yea, might as well fix typos:

$ git diff-tree -U1 f36560d96 a94f9f8a9
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 517102954e..0480191933 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -33,3 +33,3 @@
    LDK-based LSPs wishing to support often-offline senders and recipients should
-   set `UserConfig::enable_htlc_hold`, support the existing "onion mesage
+   set `UserConfig::enable_htlc_hold`, support the existing "onion message
    mailbox" feature (setting `intercept_messages_for_offline_peers` on
@@ -39,3 +39,3 @@
    force-closure risk for feerate disagreements by using a fixed, zero fee on
-   presigned transactions, relying on anchor bumps instead. They also utilize
+   pre-signed transactions, relying on anchor bumps instead. They also utilize
    the new TRUC + ephemeral dust policy in Bitcoin Core 29 to substantially
@@ -127,3 +127,3 @@
    full available buffer (#3640).
- * structs in `lightning-liquidity` were renamed to be globally unique (#3583).
+ * Structs in `lightning-liquidity` were renamed to be globally unique (#3583).
  * Renamed `SpendableOutputDescriptor::outpoint` to `spendable_outpoint` (#3634)
@@ -147,3 +147,3 @@
    fixed (#4168).
- * The fields in `SocketAddress::OnionV3` are now corectly parsed, and the
+ * The fields in `SocketAddress::OnionV3` are now correctly parsed, and the
    `Display` for such addresses is now lowercase (#4090).

TheBlueMatt · 2025-11-03T21:41:04Z

Backported in #4193

Add missing release stats for 0.1

4ed4094

TheBlueMatt added the backport 0.2 label Oct 16, 2025

TheBlueMatt added this to the 0.2 milestone Oct 16, 2025

ldk-reviews-bot requested a review from joostjager October 16, 2025 15:47

valentinewallace reviewed Oct 16, 2025

View reviewed changes

CHANGELOG.md Outdated Show resolved Hide resolved

valentinewallace reviewed Oct 16, 2025

View reviewed changes

CHANGELOG.md Outdated Show resolved Hide resolved

TheBlueMatt force-pushed the 2025-09-0.2-beta branch from 4741bb1 to 596e650 Compare October 16, 2025 22:20

tnull reviewed Oct 17, 2025

View reviewed changes

CHANGELOG.md Outdated Show resolved Hide resolved

CHANGELOG.md Outdated Show resolved Hide resolved

CHANGELOG.md Show resolved Hide resolved

CHANGELOG.md Show resolved Hide resolved

CHANGELOG.md Outdated Show resolved Hide resolved

CHANGELOG.md Show resolved Hide resolved

joostjager reviewed Oct 17, 2025

View reviewed changes

carlaKC reviewed Oct 21, 2025

View reviewed changes

CHANGELOG.md Outdated Show resolved Hide resolved

TheBlueMatt force-pushed the 2025-09-0.2-beta branch from 8c3b4bd to a5acf3c Compare October 24, 2025 22:23

tankyleo reviewed Oct 29, 2025

View reviewed changes

CHANGELOG.md Show resolved Hide resolved

Add CHANGELOG entries for 0.1 patch releases

32b469f

TheBlueMatt force-pushed the 2025-09-0.2-beta branch from db8b91b to 6bb3314 Compare October 29, 2025 23:49

tankyleo reviewed Oct 30, 2025

View reviewed changes

CHANGELOG.md Outdated Show resolved Hide resolved

TheBlueMatt force-pushed the 2025-09-0.2-beta branch from 6bb3314 to b2d9dac Compare October 30, 2025 00:49

tankyleo reviewed Oct 30, 2025

View reviewed changes

TheBlueMatt mentioned this pull request Oct 30, 2025

0.2-rc1 backports #4193

Merged

TheBlueMatt force-pushed the 2025-09-0.2-beta branch from b2d9dac to 19fd54f Compare October 30, 2025 21:04

jkczyz reviewed Oct 30, 2025

View reviewed changes

TheBlueMatt added 2 commits October 30, 2025 21:40

TheBlueMatt force-pushed the 2025-09-0.2-beta branch from 19fd54f to f36560d Compare October 30, 2025 21:40

tankyleo reviewed Oct 30, 2025

View reviewed changes

CHANGELOG.md Outdated Show resolved Hide resolved

tankyleo reviewed Oct 30, 2025

View reviewed changes

CHANGELOG.md Outdated Show resolved Hide resolved

tankyleo previously approved these changes Oct 30, 2025

View reviewed changes

Add draft release notes for 0.2

a94f9f8

TheBlueMatt dismissed tankyleo’s stale review via a94f9f8 October 30, 2025 21:46

TheBlueMatt force-pushed the 2025-09-0.2-beta branch from f36560d to a94f9f8 Compare October 30, 2025 21:46

tankyleo approved these changes Oct 30, 2025

View reviewed changes

wpaulino approved these changes Oct 30, 2025

View reviewed changes

TheBlueMatt merged commit c1bca16 into lightningdevkit:main Oct 31, 2025
23 of 25 checks passed

TheBlueMatt removed the backport 0.2 label Nov 3, 2025


		## API Updates

		* Splicing is now supported. The current implementation is expected to be

		@@ -1,3 +1,154 @@
		# 0.2 - XXX, 2025 - "Natively Asynchronous Splicing"

Add 0.2 changelog (and quick missing spliec doc) #4163

Add 0.2 changelog (and quick missing spliec doc) #4163

Uh oh!

Conversation

TheBlueMatt commented Oct 16, 2025

Uh oh!

ldk-reviews-bot commented Oct 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov bot commented Oct 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

joostjager left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

TheBlueMatt commented Oct 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

tankyleo left a comment

Choose a reason for hiding this comment

Uh oh!

TheBlueMatt commented Oct 30, 2025

Uh oh!

TheBlueMatt commented Oct 30, 2025

Uh oh!

TheBlueMatt commented Oct 30, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

TheBlueMatt commented Oct 30, 2025

Uh oh!

Uh oh!

Uh oh!

tankyleo left a comment

Choose a reason for hiding this comment

Uh oh!

TheBlueMatt commented Oct 30, 2025

Uh oh!

Uh oh!

TheBlueMatt commented Nov 3, 2025

Uh oh!

Reviewers

Assignees

Labels

ldk-reviews-bot commented Oct 16, 2025 •

edited

Loading

codecov bot commented Oct 16, 2025 •

edited

Loading

TheBlueMatt commented Oct 29, 2025 •

edited

Loading