Ensure monitors are not archived if they have a preimage we need #3450
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a
ChannelMonitor
sees a payment preimage on chain for an outbound HTLC, it creates aMonitorEvent
containing the preimage to pass to the inbound edge. The inclusion of the transaction containing the payment preimage (plus six confirmations) also results in the correspondingBalance
being removed from the live balance set, allowing theChannelMonitor
to be pruned (after a further 4032 blocks).While
MonitorEvent
s should always be processed in a timely manner, if a node is suffering from a bug where they are not, its possible for 4038 blocks to pass with the preimage-containingMonitorEvent
still pending. If that happens, its possible theChannelMonitor
is archived even though the preimage in it is needed in another channel (orChannelMonitor
), causing funds loss.Luckily the fix is simple - check for pending events before allowing a
ChannelMonitor
to be archived.Fixes #2153