Skip to content
This repository has been archived by the owner on Jul 6, 2022. It is now read-only.

Should we have the ability to revoke unclaimed tokens? #18

Closed
pabloruiz55 opened this issue Jan 3, 2018 · 4 comments
Closed

Should we have the ability to revoke unclaimed tokens? #18

pabloruiz55 opened this issue Jan 3, 2018 · 4 comments

Comments

@pabloruiz55
Copy link
Contributor

Open Zeppelin's Vesting contract template offers the possibility of revoking unclaimed tokens.

This should be a MUST for founder / advisor tokens.

Right now, there's no way to stop vesting for the tokens an advisor/founder gets. You would need to do that in case they leave the company before the vesting fully completes.

@everhusk
Copy link
Contributor

everhusk commented Jan 3, 2018

No it's okay, we have everything allocated so it's not an issue.

@everhusk everhusk closed this as completed Jan 3, 2018
@pabloruiz55
Copy link
Contributor Author

That's not what I mean.
Say you allocate 1000 tokens to me as a founder, which would get vested up to 4 years.
Right now I could call the transferTokens() function every now and then to get the share of tokens corresponding to the vesting.

The purpose of having a vesting scheme is that if I leave the company before the vesting period ends I don;t get all the tokens.

Right now, if I left the company on year 2, I could still claim the tokens for year 3 and 4 when the time comes.

Tokens MUST have the ability to be revoked, if not, people that leave the organization will still have access to them, which defeats the purpose of vesting.

@everhusk
Copy link
Contributor

everhusk commented Jan 3, 2018

I understand, it's not a problem because the founder funds are going to a multisig wallet which will be distributed by head office if the founder is still in the company.

@pabloruiz55
Copy link
Contributor Author

pabloruiz55 commented Jan 3, 2018 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants