Skip to content

Commit a60df5a

Browse files
committed
Add CHANGELOG entry for 0.0.120
1 parent a175958 commit a60df5a

File tree

1 file changed

+38
-0
lines changed

1 file changed

+38
-0
lines changed

CHANGELOG.md

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,41 @@
1+
# 0.0.120 - XXX - "Blinded Fuzzers"
2+
3+
## API Updates
4+
* The `PeerManager` bound on `UtxoLookup` was removed entirely. This enables
5+
use of `UtxoLookup` in cases broken in 0.0.119 by #2773 (#2822).
6+
* LDK now exposes and fully implements the route blinding feature (#2812).
7+
* The `lightning-transaction-sync` crate no longer relies on system time
8+
without the `time` feature (#2799, #2817).
9+
* `lightning::onion_message`'s module layout has changed (#2821).
10+
* `Event::ChannelClosed` now includes the `channel_funding_txo` (#2800).
11+
* `CandidateRouteHop` variants were destructured into individual structs,
12+
hiding some fields which were not generally consumable (#2802).
13+
14+
## Bug Fixes
15+
* Fixed a rare issue where `lightning-net-tokio` may not fully flush its send
16+
buffer, leading to connection hangs (#2832).
17+
* Fixed a panic which may occur when connecting to a peer if we opened a second
18+
channel with that peer while they were disconnected (#2808).
19+
* `Feature`'s `Eq` and `Hash` implementation now ignore dummy bytes (#2808).
20+
* Some missing `DiscardFunding` or `ChannelClosed` events are now generated in
21+
rare funding-related failures (#2809).
22+
* Fixed a privacy issue in blinded path generation where the real
23+
`cltv_expiry_delta` would be exposed to senders (#2831).
24+
25+
## Security
26+
0.0.120 fixes a denial-of-service vulnerability which is reachable from
27+
untrusted input from peers if the `UserConfig::manually_accept_inbound_channels`
28+
option is enabled.
29+
* A peer which sent an `open_channel` message with the `channel_type` field
30+
unfilled would trigger a reachable `unwrap` since LDK XXX (#2808).
31+
* In protocols where a funding output is shared with our counterparty before
32+
it is given to LDK, a malicious peer could have caused a reachable panic
33+
by reusing the same funding info in (#2809).
34+
35+
XXX add stats
36+
37+
## Bug Fixes
38+
139
# 0.0.119 - Dec 15, 2023 - "Spring Cleaning for Christmas"
240

341
## API Updates

0 commit comments

Comments
 (0)