Skip to content
This repository has been archived by the owner on Sep 27, 2019. It is now read-only.

Enable challenging in the indirect-defunding protocol #503

Open
geoknee opened this issue May 17, 2019 · 3 comments
Open

Enable challenging in the indirect-defunding protocol #503

geoknee opened this issue May 17, 2019 · 3 comments
Assignees
@geoknee
Labels
wallet

Comments

@geoknee
Copy link
Collaborator

geoknee commented May 17, 2019

In case your opponent has rage-quit and you need to get your money back.
@geoknee geoknee added the wallet label May 17, 2019
@geoknee
Copy link
Collaborator Author

geoknee commented May 17, 2019 •
edited
Loading

Presently, the indirect-defunding state machines progress automatically so an "asleep but online" opponent will not require forceMoving.

@geoknee
Copy link
Collaborator Author

geoknee commented May 17, 2019

...so we should introduce some user prompts into those state machines, in order to simulate an offline opponent.

@geoknee geoknee self-assigned this May 25, 2019
@geoknee geoknee mentioned this issue May 26, 2019
Closed
11 tasks
@geoknee geoknee mentioned this issue Jun 3, 2019
Closed
8 tasks
@geoknee
Copy link
Collaborator Author

geoknee commented Jun 18, 2019

See #520

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@geoknee geoknee

Labels
wallet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Ledger disputes during indirect-defunding magmo/apps
1 participant
@geoknee