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

Deal with foreperson losing their keys #98

Open
rmerom opened this issue Jan 11, 2017 · 3 comments
Open

Deal with foreperson losing their keys #98

rmerom opened this issue Jan 11, 2017 · 3 comments

Comments

@rmerom
Copy link
Contributor

rmerom commented Jan 11, 2017

If a regular participant loses their keys, the foreperson can retrieve the surplus funds at the end of the ROSCA and save the funds.
However, if the foreperson loses their keys, currently the funds will be "stuck" in the contract.

Suggested solution:
X time after the ROSCA ends (maybe 3 rounds?) allow WeTrust to access any surplus funds.

@rmerom rmerom changed the title Deal with foreperson losing their fees Deal with foreperson losing their keys Jan 11, 2017
@morelazers
Copy link
Contributor

I reckon it should be a constant, something like 3 months. User should still be able to withdraw after that time.

However it raises another issue: If a user comes to WeTrust 4 months after the end of a ROSCA, and claims to be the foreperson of said ROSCA, but has lost their keys, we can't verify that on-chain and (in my opinion) should not consider refunding the user.

@rmerom
Copy link
Contributor Author

rmerom commented Jan 11, 2017

You're raising a valid point about verifying who a user was. This circles back to our conversation of whether we can have the user "prove" they own the contract by submitting a secret to the contract.

Yes, as for the time to wait, maybe @gliinbox being the PM, can pitch in.

@gliinbox
Copy link

For time to wait, I agree with Tom to use a constant - like 90 days. This is in the extreme case where there might be say, 1 day ROSCA periods.

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

3 participants