|
| 1 | +# 0.0.103 - 2021-11-02 |
| 2 | + |
| 3 | +## API Updates |
| 4 | + * This release is almost entirely focused on a new API in the |
| 5 | + `lightning-invoice` crate - the `InvoicePayer`. `InvoicePayer` is a |
| 6 | + struct which takes a reference to a `ChannelManager` and a `NetworkGraph` |
| 7 | + and retries payments as paths fail. It limits retries to a configurable |
| 8 | + number, but is not serialized to disk and may retry additional times across |
| 9 | + a serialization/load. In order to learn about failed payments, it must |
| 10 | + receive `Event`s directly from the `ChannelManager`, wrapping a |
| 11 | + user-provided `EventHandler` which it provides all unhandled events to |
| 12 | + (#1059). |
| 13 | + * `get_route` has been renamed `find_route` (#1059) and now takes a `Payee` |
| 14 | + struct in replacement of a number of its long list of arguments (#1134). |
| 15 | + `Payee` is further stored in the `Route` object returned and provided in the |
| 16 | + `RouteParameters` contained in `Event::PaymentPathFailed` (#1059). |
| 17 | + * `ChannelMonitor`s must now be persisted after calls which provide new block |
| 18 | + data, prior to `MonitorEvent`s being passed back to `ChannelManager` for |
| 19 | + processing. If you are using a `ChainMonitor` this is handled for you. |
| 20 | + The `Persist` API has been updated to `Option`ally take the |
| 21 | + `ChannelMonitorUpdate` as persistence events that result from chain data no |
| 22 | + longer have a corresponding update (#1108). |
| 23 | + * `routing::Score` now has a `payment_path_failed` method which it can use to |
| 24 | + learn which channels often fail payments. It is automatically called by |
| 25 | + `InvoicePayer` for failed payment paths (#1144). |
| 26 | + * The default `Scorer` implementation is now a type alias to a type generic |
| 27 | + across different clocks and supports serialization to persist scoring data |
| 28 | + across restarts (#1146). |
| 29 | + * `Event::PaymentSent` now includes the full fee which was spent across all |
| 30 | + payment paths which were fulfilled or pending when the payment was fulfilled |
| 31 | + (#1142). |
| 32 | + * `NetGraphMsgHandler` now takes a `Deref` to the `NetworkGraph`, allowing for |
| 33 | + shared references to the graph data to make serialization and references to |
| 34 | + the graph data in the `InvoicePayer`'s `Router` simpler (#1149). |
| 35 | + * `routing::Score::channel_penalty_msat` has been updated to provide the |
| 36 | + `NodeId` of both the source and destination nodes of a channel (#1133). |
| 37 | + |
| 38 | +## Bug Fixes |
| 39 | + * Delay disconnecting peers if we receive messages from them even if it takes |
| 40 | + a while to receive a pong from them. Further, avoid sending too many gossip |
| 41 | + messages between pings to ensure we should always receive pongs in a timely |
| 42 | + manner. Together, these should significantly reduce instances of us failing |
| 43 | + to remain connected to a peer during initial gossip sync (#1137). |
| 44 | + * If a payment is sent, creating an outbound HTLC and sending it to our |
| 45 | + counterparty (implying the `ChannelMonitor` was persisted on disk), but the |
| 46 | + `ChannelManager` was not persisted prior to shutdown/crash, no |
| 47 | + `Event::PaymentPathFailed` event will be generated if the HTLC is eventually |
| 48 | + failed on chain (#1104). |
| 49 | + |
| 50 | +## Serialization Compatibility |
| 51 | + * All above new Events/fields are ignored by prior clients. All above new |
| 52 | + Events/fields are not present when reading objects serialized by prior |
| 53 | + versions of the library. |
| 54 | + * Payments for which a `Route` was generated using a previous version or for |
| 55 | + which the payment was originally sent by a previous version of the library |
| 56 | + will not be retried by an `InvoicePayer`. |
| 57 | + |
| 58 | +This release was singularly focused and some contributions by third parties |
| 59 | +were delayed. |
| 60 | +In total, this release features 38 files changed, 4414 insertions, and 969 |
| 61 | +deletions in 71 commits from 2 authors, in alphabetical order: |
| 62 | + |
| 63 | + * Jeffrey Czyz |
| 64 | + * Matt Corallo |
| 65 | + |
| 66 | + |
1 | 67 | # 0.0.102 - 2021-10-18
|
2 | 68 |
|
3 | 69 | ## API Updates
|
|
0 commit comments