Matt Corallo f60da31e56 Add forward-compat due serialization variants of HTLCFailureMsg ... Going forward, all lightning messages have a TLV stream suffix, allowing new fields to be added as needed. In the P2P protocol, messages have an explicit length, so there is no implied length in the TLV stream itself. HTLCFailureMsg enum variants have messages in them, but without a size prefix or any explicit end. Thus, if a HTLCFailureMsg is read as a part of a ChannelManager, with a TLV stream at the end, there is no way to differentiate between the end of the message and the next field(s) in the ChannelManager. Here we add two new variant values for HTLCFailureMsg variants in the read path, allowing us to switch to the new values if/when we add new TLV fields in UpdateFailHTLC or UpdateFailMalformedHTLC so that older versions can still read the new TLV fields.		2021-09-18 01:01:41 +00:00
..
src	Add forward-compat due serialization variants of HTLCFailureMsg	2021-09-18 01:01:41 +00:00
Cargo.toml	Update versions to 0.0.100 and lightning-invoice to 0.8	2021-08-17 18:55:07 +00:00