Coop-Settle channel-state logic#7233
Merged
Merged
Conversation
f3fa686 to
904b9f7
Compare
istankovic
reviewed
Jul 23, 2021
904b9f7 to
ec30b5f
Compare
Contributor
Did we agree on having a specific endpoint for it? Or couldn't we optimisticly try to coop settle and if not possible do the old settlement process? |
Contributor
Author
That's the plan - reuse the channel-close endpoint: there try a coop-settle first and if that expires go with the traditional close/settle cycle. |
4 tasks
istankovic
reviewed
Aug 3, 2021
istankovic
reviewed
Aug 3, 2021
istankovic
reviewed
Aug 3, 2021
istankovic
reviewed
Aug 5, 2021
istankovic
reviewed
Aug 5, 2021
istankovic
reviewed
Aug 5, 2021
istankovic
reviewed
Aug 5, 2021
istankovic
reviewed
Aug 5, 2021
istankovic
reviewed
Aug 5, 2021
karlb
reviewed
Aug 5, 2021
istankovic
reviewed
Aug 5, 2021
istankovic
reviewed
Aug 5, 2021
istankovic
reviewed
Aug 5, 2021
istankovic
reviewed
Aug 5, 2021
istankovic
reviewed
Aug 5, 2021
istankovic
reviewed
Aug 5, 2021
karlb
reviewed
Aug 5, 2021
istankovic
reviewed
Aug 5, 2021
istankovic
reviewed
Aug 5, 2021
5b76a2f to
8f6e7f8
Compare
ulope
reviewed
Aug 9, 2021
8f6e7f8 to
739348f
Compare
The single file testing the state-machine for the NettingChannelState and NettingChannelEndstate was very large and was testing a lot of different state-changes. In this commit, the file is split up in a separate module, roughly grouped by the type of state-changes that are tested
Before, the logic to handle the `ActionChannelCoopSettle` was there, but the channels state machine would not process the event. Now, the dynamic type-checking of incoming events will forward the action to the appropriate handler-function.
And drop the unneded type annotation.
It's still useful.
739348f to
0919ec7
Compare
0919ec7 to
e31db23
Compare
istankovic
approved these changes
Aug 11, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Implement the Coop-Settle logic built on-top of the Withdraw protocol.
This PR implements the logic as specified in this proposal.
It leverages the internal locking of channels with the
NettingChannelEndState.withdraws_pendingchecks, that arealready in place for the withdraws.
The most important additional verification for coop-settle is:
This PR lacks:
ActionInitCoopSettleContractSendCoopSettleevent