Matt Corallo 70ae45fea0 Don't fail HTLCs in revoked commitment txn until we spend them ... When we see a counterparty revoked commitment transaction on-chain we shouldn't immediately queue up HTLCs present in it for resolution until we have spent the HTLC outputs in some kind of claim transaction. In order to do so, we first have to change the `fail_unbroadcast_htlcs!()` call to provide it with the HTLCs which are present in the (revoked) commitment transaction which was broadcast. However, this is not sufficient - because all of those HTLCs had their `HTLCSource` removed when the commitment transaction was revoked, we also have to update `fail_unbroadcast_htlcs` to check the payment hash and amount when the `HTLCSource` is `None`. Somewhat surprisingly, several tests actually explicitly tested for the old behavior, which required amending to pass with the new changes. Finally, this adds a debug assertion when writing `ChannelMonitor`s to ensure `HTLCSource`s do not leak.		2022-06-21 16:14:55 +00:00
..
src	Don't fail HTLCs in revoked commitment txn until we spend them	2022-06-21 16:14:55 +00:00
Cargo.toml	Update crate versions to 0.0.108/invoice 0.16	2022-06-10 14:53:23 +00:00