|
| 1 | +# 0.1.2 - Apr 02, 2025 - "Foolishly Edgy Cases" |
| 2 | + |
| 3 | +## API Updates |
| 4 | + * `lightning-invoice` is now re-exported as `lightning::bolt11_invoice` |
| 5 | + (#3671). |
| 6 | + |
| 7 | +## Performance Improvements |
| 8 | + * `rapid-gossip-sync` graph parsing is substantially faster, resolving a |
| 9 | + regression in 0.1 (#3581). |
| 10 | + * `NetworkGraph` loading is now substantially faster and does fewer |
| 11 | + allocations, resulting in a 20% further improvement in `rapid-gossip-sync` |
| 12 | + loading when initializing from scratch (#3581). |
| 13 | + * `ChannelMonitor`s for closed channels are no longer always re-persisted |
| 14 | + immediately after startup, reducing on-startup I/O burden (#3619). |
| 15 | + |
| 16 | +## Bug Fixes |
| 17 | + * BOLT 11 invoices longer than 1023 bytes long (and up to 7089 bytes) now |
| 18 | + properly parse (#3665). |
| 19 | + * In some cases, when using synchronous persistence with higher latency than |
| 20 | + the latency to communicate with peers, when receiving an MPP payment with |
| 21 | + multiple parts received over the same channel, a channel could hang and not |
| 22 | + make progress, eventually leading to a force-closure due to timed-out HTLCs. |
| 23 | + This has now been fixed (#3680). |
| 24 | + * Some rare cases with multi-hop BOLT 11 route hints or multiple redundant |
| 25 | + blinded paths could have led to the router creating invalid `Route`s were |
| 26 | + fixed (#3586). |
| 27 | + * Corrected the decay logic in `ProbabilisticScorer`'s historical buckets |
| 28 | + model. Note that by default historical buckets are only decayed if no new |
| 29 | + datapoints have been added for a channel for two weeks (#3562). |
| 30 | + * `{Channel,Onion}MessageHandler::peer_disconnected` will now be called if a |
| 31 | + different message handler refused connection by returning an `Err` from its |
| 32 | + `peer_connected` method (#3580). |
| 33 | + * If the counterparty broadcasts a revoked state with pending HTLCs, those |
| 34 | + will now be claimed with other outputs which we consider to not be |
| 35 | + vulnerable to pinning attacks if they are not yet claimable by our |
| 36 | + counterparty, potentially reducing our exposure to pinning attacks (#3564). |
| 37 | + |
1 | 38 | # 0.1.1 - Jan 28, 2025 - "Onchain Matters"
|
2 | 39 |
|
3 | 40 | ## API Updates
|
|
0 commit comments