@@ -119,19 +119,58 @@ Proposals (BIPs)][bips repo], [Lightning BOLTs][bolts repo],
119
119
[ Lightning BLIPs] [ blips repo ] , [ Bitcoin Inquisition] [ bitcoin inquisition
120
120
repo] , and [ BINANAs] [ binana repo ] ._
121
121
122
- - [ Bitcoin Core #31122 ] [ ] cluster mempool: Implement changeset interface for mempool
123
-
124
- - [ Core Lightning #7852 ] [ ] pyln-client: restore backwards compatibility with CLN prior to 24.08
125
-
126
- - [ Core Lightning #7740 ] [ ] askrene: add algorithm to compute feasible flow
127
-
128
- - [ Core Lightning #7719 ] [ ] splice: Update funding pubkey on splice lock
129
-
130
- - [ Eclair #2935 ] [ ] Add force-close notification
131
-
132
- - [ LDK #3137 ] [ ] Implement accepting dual-funded channels without contributing
133
-
134
- - [ LND #8337 ] [ ] [ 1/4] - protofsm: add new package for driving generic protocol FSMs
122
+ - [ Bitcoin Core #31122 ] [ ] implements a ` changeset ` interface for the mempool,
123
+ allowing a node to compute the impact of a proposed set of changes on the state
124
+ of the mempool. For example, checking whether ancestor/descendant/[ TRUC] [ topic v3
125
+ transaction relay] (and future cluster) limits are violated when a transaction
126
+ or a package is accepted, or determining whether an [ RBF] [ topic RBF ] fee bump
127
+ improves the state of the mempool. This PR is part of the [ cluster
128
+ mempool] [ topic cluster mempool ] project.
129
+
130
+ - [ Core Lightning #7852 ] [ ] restores backwards compatibility with versions prior
131
+ to 24.08 for the ` pyln-client ` plugin (a Python client library) by
132
+ reintroducing a description field.
133
+
134
+ - [ Core Lightning #7740 ] [ ] improves the minimum cost flow (MCF) solver of the
135
+ ` askrene ` (see [ Newsletter #316 ] [ news316 askrene ] ) plugin by providing an API
136
+ that abstracts the complexity of MCF solving to allow easier integration of
137
+ newly added graph-based flow computation algorithms. The solver adopts the
138
+ same channel cost function linearization as ` renepay ` (see [ Newsletter
139
+ #263 ] [ news263 renepay ] ), which improves pathfinding reliability, and
140
+ introduces support for customizable units beyond msats, allowing greater
141
+ scalability for large payments. This PR adds the ` simple_feasibleflow ` ,
142
+ ` get_augmenting_flow ` , ` augment_flow ` , and ` node_balance ` methods to improve
143
+ the efficiency of flow calculations.
144
+
145
+ - [ Core Lightning #7719 ] [ ] achieves interoperability with Eclair for
146
+ [ splicing] [ topic splicing ] , allowing splices to be executed between the two
147
+ implementations. This PR introduces several changes to align with Eclair’s
148
+ implementation including support for rotating remote funding keys, adding
149
+ ` batch_size ` for commitment-signed messages, preventing transmission of
150
+ previous funding transactions due to packet size limits, removing blockhashes
151
+ from messages, and adjusting pre-set funding output balances.
152
+
153
+ - [ Eclair #2935 ] [ ] adds a notification to the node operator in the event of a
154
+ channel force close initiated by a channel peer.
155
+
156
+ - [ LDK #3137 ] [ ] adds support for accepting peer-initiated [ dual-funded
157
+ channels] [ topic dual funding ] , although funding or creating such channels is
158
+ not yet supported. If ` manually_accept_inbound_channels ` is set to false,
159
+ channels are automatically accepted, while the
160
+ ` ChannelManager::accept_inbound_channel() ` function allows manual acceptance.
161
+ A new ` channel_negotiation_type ` field is introduced to distinguish between
162
+ inbound requests for dual-funded and non-dual-funded channels.
163
+ [ Zero-conf] [ topic zero-conf channels ] dual-funded channels and
164
+ [ RBF] [ topic rbf ] fee
165
+ bumping of funding transactions are not supported.
166
+
167
+ - [ LND #8337 ] [ ] introduces the ` protofsm ` package, a reusable framework for
168
+ creating event-driven protocol finite state machines (FSMs) in LND. Instead of
169
+ writing boilerplate code to handle states, transitions, and events, developers
170
+ can define the states, what triggers events, and the rules for moving between
171
+ them, and the ` State ` interface will encapsulate behavior, handle events, and
172
+ determine terminal states, while daemon adapters handle side effects like
173
+ broadcasting transactions and sending peer messages.
135
174
136
175
{% include references.md %}
137
176
{% include linkers/issues.md v=2 issues="31122,7852,7740,7719,2935,3137,8337" %}
@@ -147,3 +186,5 @@ repo], and [BINANAs][binana repo]._
147
186
[ core lightning 24.11rc2 ] : https://github.com/ElementsProject/lightning/releases/tag/v24.11rc2
148
187
[ bdk 0.30.0 ] : https://github.com/bitcoindevkit/bdk/releases/tag/v0.30.0
149
188
[ ldk 0.18.4-beta.rc1 ] : https://github.com/lightningnetwork/lnd/releases/tag/v0.18.4-beta.rc1
189
+ [ news316 askrene ] : /en/newsletters/2024/08/16/#core-lightning-7517
190
+ [ news263 renepay ] : /en/newsletters/2023/08/09/#core-lightning-6376
0 commit comments