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

Specification of ForceMove to exhibit safety. #2

Open
wants to merge 66 commits into
base: master
Choose a base branch
from

Conversation

andrewgordstewart
Copy link
Contributor

No description provided.

At this point, by front-running, Eve can force an infinite loop of
forceMoves, where Alice has no choice but to call refute. Since refute
does not increment the channel's turnNumber on chain, this creates an
infinite loop.
At this point, if Alice has commitments {5,6} and Eve calls
ForceMove(5), then Alice can't refute, and instead needs to respond with
a move.
Once the channel is in the CHALLENGE mode with the latest turn number,
Eve would be forced to either
- respond with a move (which Alice is ok with)
- respond with an alternative move, providing a full round (which Alice
  has to be ok with, since she signed one of the commitments in that
  round, and has no control over the later commitments)
- refute with a later state signed by Alice (which she can't)
(Some of the algorithm overflows currently.)
There's no need to define it as a constant and then check that it's
a participant's IDX. Plus, this way, models exhaustively check all positions
of Alice in the participants array.
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

Successfully merging this pull request may close these issues.

1 participant