33
33
known TLV fields were incorrectly encoded into the ` ExtraData ` field of
34
34
messages in the dynamic commitment set.
35
35
36
+ - Fixed [ zombie channel leak] ( https://github.com/lightningnetwork/lnd/pull/10015 )
37
+ in the memory graph, resulting in incorrect path finding and memory usage.
38
+
36
39
# New Features
37
40
38
41
## Functional Enhancements
@@ -110,7 +113,6 @@ circuit. The indices are only available for forwarding events saved after v0.20.
110
113
* Add graph SQL migration logic:
111
114
* [ 1] ( https://github.com/lightningnetwork/lnd/pull/10036 )
112
115
* [ 2] ( https://github.com/lightningnetwork/lnd/pull/10050 )
113
- * [ 3] ( https://github.com/lightningnetwork/lnd/pull/10038 )
114
116
115
117
## RPC Updates
116
118
* Previously the ` RoutingPolicy ` would return the inbound fee record in its
@@ -119,17 +121,8 @@ circuit. The indices are only available for forwarding events saved after v0.20.
119
121
[ fixed] ( https://github.com/lightningnetwork/lnd/pull/9572 ) , the affected RPCs
120
122
are ` SubscribeChannelGraph ` , ` GetChanInfo ` , ` GetNodeInfo ` and ` DescribeGraph ` .
121
123
122
- * [ Fix a bug] ( https://github.com/lightningnetwork/lnd/pull/10064 ) where the
123
- ` GetChanInfo ` was not returning the correct gRPC status code in the cases
124
- where the channel is unknown to the node. The same is done for ` LookupInvoice `
125
- for the case where the DB is kvdb backed and no invoices have yet been added
126
- to the database.
127
124
128
125
## lncli Updates
129
- * Previously, users could only specify one ` outgoing_chan_id ` when calling the
130
- ` lncli queryroutes ` or the QueryRoutes RPC. With this change, multiple
131
- ` outgoing_chan_id ` can be passed during the call.
132
-
133
126
134
127
## Code Health
135
128
@@ -163,10 +156,6 @@ reader of a payment request.
163
156
| [ ` routerrpc.SendPaymentV2 ` ] ( https://lightning.engineering/api-docs/api/lnd/router/send-payment-v2/index.html ) | ✅ | ` POST ` | ` /v2/router/send ` |
164
157
| [ ` routerrpc.TrackPaymentV2 ` ] ( https://lightning.engineering/api-docs/api/lnd/router/track-payment-v2/ ) | ✅ | ` GET ` | ` /v2/router/track/{payment_hash} ` |
165
158
166
- * We are deprecating ` OutgoingChanId ` in favour of ` OutgoingChanIds ` in the
167
- ` QueryRoutes ` RPC. This [ transition] ( https://github.com/lightningnetwork/lnd/pull/10057 ) allows us to specify more than one outgoing channel
168
- the pathfinder should use when finding a route.
169
-
170
159
# Technical and Architectural Updates
171
160
## BOLT Spec Updates
172
161
@@ -206,6 +195,5 @@ reader of a payment request.
206
195
* Funyug
207
196
* Mohamed Awnallah
208
197
* Pins
209
- * Torkel Rogstad
210
198
* Yong Yu
211
199
* Ziggie
0 commit comments