|
| 1 | +# 0.1.5 - Jul XXX, 2025 - "Async Path Reduction" |
| 2 | + |
| 3 | +## Performance Improvements |
| 4 | + * `NetworkGraph`'s expensive internal consistency checks have now been |
| 5 | + disabled in debug builds in addition to release builds (#3687). |
| 6 | + |
| 7 | +## Bug Fixes |
| 8 | + * Pathfinding which results in a multi-path payment is now substantially |
| 9 | + smarter, using fewer paths and better optimizing fees and successes (#3890). |
| 10 | + * Force-closing a channel while it is blocked on another channel's async |
| 11 | + `ChannelMonitorUpdate` can no longer lead to a panic (#3858). |
| 12 | + * `ChannelMonitorUpdate`s can no longer be released to storage too early when |
| 13 | + doing async updates or on restart. This only impacts async |
| 14 | + `ChannelMonitorUpdate` persistence and can lead to loss of funds only in rare |
| 15 | + cases with `ChannelMonitorUpdate` persistence order inversions (#3907). |
| 16 | + |
| 17 | +## Security |
| 18 | +0.1.5 fixes a vulnerability which could allow a peer to overdraw their reserve |
| 19 | +value, potentially cutting into commitment transaction fees on channels with a |
| 20 | +low reserve. |
| 21 | + * Due to a bug in checking whether an HTLC is dust during acceptance, near-dust |
| 22 | + HTLCs were not counted towards the commitment transaction fee, but did |
| 23 | + eventually contribute to it when we built a commitment transaction. This can |
| 24 | + be used by a counterparty to overdraw their reserve value, or, for channels |
| 25 | + with a low reserve value, cut into the commitment transaction fee (#3933). |
| 26 | + |
| 27 | + |
1 | 28 | # 0.1.4 - May 23, 2025 - "Careful Validation of Bogus States" |
2 | 29 |
|
3 | 30 | ## Bug Fixes |
|
0 commit comments