This repository has been archived by the owner on Jan 27, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 25
Remove "start Job" button! #172
Comments
This was referenced Feb 14, 2019
@raamb So I propose the following workflow for dApp.
|
Hi @astroseger the current flow is rather similar to what you suggested the distinction being in when the channel activity is started
|
ok. I see now. We need to get the state of the channel from the service to calculate remaining funds. And you call it "start Job"... And we cannot avoid signature with metamask here, so we cannot remove "Start Job" button unless we implement #174 (which would be more convenient but less secure... ) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I would propose to completely remove "start Job" button. Why do we have it???
When user interact with service for the first time he should have "open channel" button. But if user already have a channel (and you claim that you find channels which already exits), then we obviously don't need "start Job".
User should have possibility to directly invoke new Request, or Fund/Extend the channel.
The text was updated successfully, but these errors were encountered: