Keep track on which side initiated a mutual close #3042
Merged
+105
−51
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.
We currently lose this information once we transition to
SHUTDOWN
(inNORMAL
, we can compute it based on whichshutdown
is present).I tried two approaches in two successive commits:
Option[ClosingFeerates]
byOption[CloseInitiated]
(which itself stores anOption[ClosingFeerates]
. This approach is very close to what we have currently, but ambiguous in the non-initiator case (there is no difference between "no close in progress" and "a close as non-initiator"). This ambiguity makes the backward compat code simpler.CloseStatus
. This approach is a bit more involved, but also unambiguous and probably easier for the reader. TheCloseStatus
is optional inNORMAL
state, mandatory inSHUTDOWN
state.