Move ChannelManager::monitor_updated to a MonitorEvent
authorMatt Corallo <git@bluematt.me>
Thu, 7 Oct 2021 18:51:49 +0000 (18:51 +0000)
committerMatt Corallo <git@bluematt.me>
Tue, 19 Oct 2021 23:49:04 +0000 (23:49 +0000)
commit4500270488e6ed918c5f6e07310eb4a384eb6e21
tree100c219ebbcee9fd28cc4b12e928ec916a84e997
parentdf8bde9b2efdd12dcb5a4b8d5d5d2507af402598
Move ChannelManager::monitor_updated to a MonitorEvent

In the next commit we'll need ChainMonitor to "see" when a monitor
persistence completes, which means `monitor_updated` needs to move
to `ChainMonitor`. The simplest way to then communicate that
information to `ChannelManager` is via `MonitorEvet`s, which seems
to line up ok, even if they're now constructed by multiple
different places.
fuzz/src/chanmon_consistency.rs
lightning/src/chain/chainmonitor.rs
lightning/src/chain/channelmonitor.rs
lightning/src/chain/mod.rs
lightning/src/ln/chanmon_update_fail_tests.rs
lightning/src/ln/channelmanager.rs