Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unclear specification of adjudication methods #367

Open
matthiasgeihs opened this issue Aug 2, 2022 · 1 comment
Open

Unclear specification of adjudication methods #367

matthiasgeihs opened this issue Aug 2, 2022 · 1 comment

Comments

@matthiasgeihs
Copy link
Contributor

Location

package client
package channel

Problem

At the moment it is not clearly specified whether the adjudicator methods should wait for the correct phase before on-chain calls are made.

  • For example, Channel.ForceUpdate is designed such that it ensures the channel registration, but it does not wait for the dispute period to be over.
  • Another example is Channel.Withdraw. It enforces the registration of a channel in the dispute case, but it does not wait until the channel can be concluded.

Currently, it is implicitly in the responsibility of the chain backends to ensure the correct waiting period. However, this is not clearly specified and it could better be done consistently in the core client.

Proposal

Ensure that Channel.ForceUpdate and Channel.Withdraw wait until the corresponding phase is reached before sending the call to the Adjudicator.

@matthiasgeihs
Copy link
Contributor Author

Side node: As the MockBackend used for testing the core does not use proper time out logic yet, these things are easily missed in the core client tests. We should implement the timeout logic for events emitted by the Mock Backend Subscription.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant