You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make counterparty_node_id non-optional on ChannelReady and ChannelClosed event
We no longer need to maintain backwards compatibility with LDK Node
v0.1.0, so we can make this a required field and avoid propagating
the Option through the API.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,10 @@
1
+
# Pending
2
+
3
+
## Serialization Compatibility
4
+
- The `counterparty_node_id` field of the `ChannelReady` and `ChannelClosed` events is now
5
+
required. Events persisted by LDK Node v0.1.0 and prior that are missing this field will
6
+
fail to deserialize.
7
+
1
8
# 0.7.0 - Dec. 3, 2025
2
9
This seventh minor release introduces numerous new features, bug fixes, and API improvements. In particular, it adds support for channel Splicing, Async Payments, as well as sourcing chain data from a Bitcoin Core REST backend.
0 commit comments