|
29 | 29 | `OnChainSweep` and only being used when the on-chain sweep is urgent (#3268). |
30 | 30 | * All `ChannelMonitor`s are no longer persisted after each block connection, |
31 | 31 | instead spreading them out over a handful of blocks to reduce load spikes. |
32 | | - Note that this will increase the incidence of `ChannelMonitor`s which have |
| 32 | + Note that this will increase the incidence of `ChannelMonitor`s that have |
33 | 33 | different best blocks on startup, requiring some additional chain replay |
34 | 34 | (but only on some `ChannelMonitor`s) on startup for `Listen` users (#2966). |
35 | 35 | * A new format for Rapid Gossip Sync data is now supported which contains |
36 | 36 | additional node metadata and is more extensible (#3098). |
37 | 37 | * `ChannelManager::send_payment_with_route` is now deprecated in favor of the |
38 | 38 | much easier to use `Channelmanager::send_payment`. Those who wish to manually |
39 | 39 | select the route such payments go over should do so by matching the |
40 | | - `payment_id` in `Router::find_route_with_id` (#3224). |
| 40 | + `payment_id` passed to `send_payment` in `Router::find_route_with_id` (#3224) |
41 | 41 | * `lightning-transaction-sync` now takes most `Confirm`s as a generic `Deref`. |
42 | 42 | You may need an explicit `as &(dyn Confirm)` to update existing code (#3101). |
43 | 43 | * HTLCs will now be forwarded over any channel with a peer, rather than only |
|
62 | 62 | * BOLT 12 invoice requests now go out over, and accept responses over, multiple |
63 | 63 | paths (#3087). |
64 | 64 | * `OnionMessenger` now supports intercepting and re-forwarding onion messages |
65 | | - for peers which are offline at the time of receipt when constructed with |
| 65 | + for peers that are offline at the time of receipt when constructed with |
66 | 66 | `new_with_offline_peer_interception` (#2973). |
67 | 67 | * Onion message handling trait methods now generally take a `Responder` which |
68 | 68 | can be used to create a `ResponseInstruction` to better control how responses |
|
73 | 73 | * Blinded paths used for BOLT 12 `Offer`/`Refund`s are now compact when they |
74 | 74 | expire relatively soon, making them somewhat smaller (#3011, #3080). |
75 | 75 | * `ChannelManager::force_close_*` now take a err msg to send to peers (#2889). |
| 76 | + * `ChannelDetails::is_public` has been renamed to `is_announced` and |
| 77 | + `ChannelHandshakeConfig::announced_channel` to `announce_for_forwarding` to |
| 78 | + address various misconceptions about the purpose of announcement (#3257). |
76 | 79 | * `BlindedPath`s are now split into `BlindedMessagePath`s and |
77 | 80 | `BlindedPaymentPath`s and `advance_path_by_one` added to each (#3182). |
78 | 81 | * `BlindedPaymentPath` now includes the `BlindedPayInfo` (#3245). |
79 | 82 | * BOLT 12 `Offer`/`Refund` builders no longer require a description, instead |
80 | 83 | allowing it to be set on the builder itself (#3018). |
81 | 84 | * The `{Inbound,Outbound}HTLCState{,Details}` and `ChannelDetails` structs have |
82 | 85 | moved to the `ln::channel_state` module (#3089). |
83 | | - * `Event::OpenChannelRequest` now contains `params` and `is_public` (#3019). |
| 86 | + * `Event::OpenChannelRequest` now contains `params` and `is_announced` (#3019). |
84 | 87 | * Peers are no longer disconnected when we force-close a channel (#3088). |
85 | 88 | * BOLT12 `Offer` and `Refund` now implement `Readable` (#2965). |
86 | 89 | * `RecipientOnionFields` is now included in `Event::PaymentClaimed` (#3084). |
|
96 | 99 | applied to the network graph via `Event::PaymentPathFailed`, preventing a |
97 | 100 | node along the path from identifying the sender of a payment (#3083). |
98 | 101 | * In order to prevent senders from identifying the recipient of a BOLT 12 offer |
99 | | - which included a blinded path, cryptographic information from blinded paths |
| 102 | + that included a blinded path, cryptographic information from blinded paths |
100 | 103 | are now included in the invoice request verification (#3085, #3139, #3242). |
101 | 104 | * Routes are now length-limited based on the actual onion contents rather than |
102 | | - a fixed value. This ensures no routes are generated which are unpayable when |
| 105 | + a fixed value. This ensures no routes are generated that are unpayable when |
103 | 106 | sending HTLCs with custom TLVs, blinded paths, or metadata (#3026, #3156). |
104 | 107 | * Unannounced LDK nodes (or ones without a network graph) will now include |
105 | 108 | unannounced peers as introduction points in blinded paths. This addresses |
|
130 | 133 | be persisted in the `ChannelMonitor` for one or more MPP parts, resulting in |
131 | 134 | only some of the payment's value being claimed (#3120). |
132 | 135 | * A rare race was fixed which could lead to `ChannelMonitorUpdate`s appearing |
133 | | - after a full `ChannelMonitor` persistence which already contained the same |
| 136 | + after a full `ChannelMonitor` persistence that already contained the same |
134 | 137 | update. This could have caused a panic on startup for users of the |
135 | 138 | `MonitorUpdatingPersister` in rare cases after a crash (#3196). |
136 | 139 | * Background Processor is now woken from `ChainMonitor` when new blocks appear, |
|
168 | 171 | * LDK now supports BOLT 12 Offers without descriptions when no amount is |
169 | 172 | present (#3018). |
170 | 173 | * A bug was fixed which might have led to LDK spuriously rejecting |
171 | | - `channel_update`s which use as-yet-undefined flag bits (#3144). |
| 174 | + `channel_update`s that use as-yet-undefined flag bits (#3144). |
172 | 175 |
|
173 | 176 | XXX change stats |
174 | 177 |
|
|
0 commit comments