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

VipnodePool: Support self-withdraw using operator-signed payloads #2

Open
shazow opened this issue Nov 13, 2018 · 0 comments
Open

VipnodePool: Support self-withdraw using operator-signed payloads #2

shazow opened this issue Nov 13, 2018 · 0 comments

Comments

@shazow
Copy link
Member

shazow commented Nov 13, 2018

Right now, the operator must execute and pay for the transaction fee to allow others to withdraw (unless the ForceWithdraw flow is completed).

This requires the operator to maintain a balance in the wallet to pay for fees, which makes things logistically harder.

Would be nice if the operator could provide a signed payload for the withdraw request (approving a specific amount) that the withdrawer can use to perform their own transaction.

One gotcha: If the client requests a withdraw, the pool signs over a withdraw confirmation they can use to self-withdraw, there is no way to force the client to actually use it. That's probably okay, since it falls back to the ForceWithdraw flow.

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