|
1 | | -# 0.1.5 - Jul XXX, 2025 - "Async Path Reduction" |
| 1 | +# 0.1.8 - Dec 2, 2025 - "Async Update Completion" |
| 2 | + |
| 3 | +## Bug Fixes |
| 4 | + * In cases where an MPP payment is claimed while one channel is waiting on a |
| 5 | + counterparty's `revoke_and_ack` message and the `revoke_and_ack` message is |
| 6 | + received prior to the asynchronous completion of the MPP-claim |
| 7 | + `ChannelMonitorUpdate`, the channel will no longer hang (#4236). |
| 8 | + * Deserializing invalid `Duration`s can no longer panic (#4172). |
| 9 | + |
| 10 | + |
| 11 | +# 0.1.7 - Oct 21, 2025 - "Unstable Release CI" |
| 12 | + |
| 13 | +## Bug Fixes |
| 14 | + * Builds with the `docsrs` cfg flag (set automatically for builds on docs.rs |
| 15 | + but otherwise not used) were fixed. |
| 16 | + |
| 17 | + |
| 18 | +# 0.1.6 - Oct 10, 2025 - "Async Preimage Claims" |
| 19 | + |
| 20 | +## Performance Improvements |
| 21 | + * `NetworkGraph::remove_stale_channels_and_tracking` has been sped up by more |
| 22 | + than 20x in cases where many entries need to be removed (such as after |
| 23 | + initial gossip sync, #4080). |
| 24 | + |
| 25 | +## Bug Fixes |
| 26 | + * Delivery of on-chain resolutions of HTLCs to `ChannelManager` has been made |
| 27 | + more robust to prevent loss in some exceedingly rare crash cases. This may |
| 28 | + marginally increase payment resolution event replays on startup (#3984). |
| 29 | + * Corrected forwarding of new gossip to peers which we are sending an initial |
| 30 | + gossip sync to (#4107). |
| 31 | + * A rare race condition may have resulted in outbound BOLT12 payments |
| 32 | + spuriously failing while processing the `Bolt12Invoice` message (#4078). |
| 33 | + * If a channel is updated multiple times after a payment is claimed while using |
| 34 | + async persistence of the `ChannelMonitorUpdate`s, and the node then restarts |
| 35 | + with a stale copy of its `ChannelManager`, the `PaymentClaimed` may have been |
| 36 | + lost (#3988). |
| 37 | + * If an async-persisted `ChannelMonitorUpdate` for one part of an MPP claim |
| 38 | + does not complete before multiple `ChannelMonitorUpdate`s for another channel |
| 39 | + in the same MPP claim complete, and the node restarts twice, the preimage may |
| 40 | + be lost and the MPP payment part may not be claimed (#3928). |
| 41 | + |
| 42 | +## Security |
| 43 | +0.1.6 fixes a denial of service vulnerability and a funds-theft vulnerability. |
| 44 | + * When a channel has been force-closed, we have already claimed some of its |
| 45 | + HTLCs on-chain, and we later learn a new preimage allowing us to claim |
| 46 | + further HTLCs on-chain, we could in some cases generate invalid claim |
| 47 | + transactions leading to loss of funds (#4154). |
| 48 | + * When a `ChannelMonitor` is created for a channel which is never funded with |
| 49 | + a real transaction, `ChannelMonitor::get_claimable_balances` would never be |
| 50 | + empty. As a result, `ChannelMonitor::check_and_update_full_resolution_status` |
| 51 | + would never indicate the monitor is prunable, and thus |
| 52 | + `ChainMonitor::archive_fully_resolved_channel_monitors` would never remove |
| 53 | + it. This allows a peer which opens channels without funding them to bloat our |
| 54 | + memory and disk space, eventually leading to denial-of-service (#4081). |
| 55 | + |
| 56 | + |
| 57 | +# 0.1.5 - Jul 16, 2025 - "Async Path Reduction" |
2 | 58 |
|
3 | 59 | ## Performance Improvements |
4 | 60 | * `NetworkGraph`'s expensive internal consistency checks have now been |
|
0 commit comments