Wilmer Paulino e2f216b694 Track previous ChannelConfig and expire after enough ticks ... We do this to prevent payment failures while the `ChannelUpdate` for the new `ChannelConfig` still propagates throughout the network. In a follow up commit, we'll honor forwarding HTLCs that were constructed based on either the previous or current `ChannelConfig`. To handle expiration (when we should stop allowing the previous config), we rely on the ChannelManager's `timer_tick_occurred` method. After enough ticks, the previous config is cleared from memory, and only the current config applies moving forward.		2022-06-20 13:12:49 -07:00
..
src	Track previous ChannelConfig and expire after enough ticks	2022-06-20 13:12:49 -07:00
Cargo.toml	Update crate versions to 0.0.108/invoice 0.16	2022-06-10 14:53:23 +00:00