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

Token Manager: owner initiated token burn #919

Closed
lkngtn opened this issue Jul 12, 2019 · 4 comments
Closed

Token Manager: owner initiated token burn #919

lkngtn opened this issue Jul 12, 2019 · 4 comments

Comments

@lkngtn
Copy link
Contributor

lkngtn commented Jul 12, 2019

Note: this has been closed to be tracked in the "wishlist for future upgrades".

There are cases where it would be handy to be able to allow users to burn their own tokens without requiring a vote. Currently the Token Managers burn() function allows burning any and all tokens, so it is not practical to grant this to all token holders.

In order to allow any token holder to burn only their own tokens we would need to add new functionality. I think this could be accomplished by adding a new personalBurn() function or by putting that logic in a standalone forwarder or ACL oracle.

I don't have a strong preference on the approach, though I lean towards either the forwarder or oracle as I don't think this is a universally applicable feature of the token manager.

@sohkai
Copy link
Contributor

sohkai commented Jul 12, 2019

I'm wondering what circumstances a user would want to do this?

As you said, it is certainly easy functionality to add to the Token Manager, but hard to imagine someone invoking this without something else happening in tandem (e.g. a ragequit), which would require at least a forwarder (we can design an app that receives the burn permission and only invokes a token burn on the msg.sender).

@luisivan
Copy link
Contributor

Cannot you just send your tokens to 0x000...? It wouldn't change the token supply count, but it'd be the same from a user perspective

@lkngtn
Copy link
Contributor Author

lkngtn commented Jul 15, 2019

I'm wondering what circumstances a user would want to do this?

One situation which came up was within the Coop, Tokens were used as membership in the org there was no way for a member to relinquish their membership token. In order to burn a token we would have had to create a vote and have other member approve the vote, which purely from a practicality perspective is quite inefficient and doesn't make a lot of logical sense. If a user is trying to relinquish their token they should not need approval from the rest of the member in order to do so (this is just a waste of transactions and attention).

What ended up happening in the Coop is that people simply stopped voting and engaging with the org. Eventually enough of the membership did this which resulted in issues where it was difficult to meet approval quorum, and votes appeared illegitimate because of a lack of participation.

Cannot you just send your tokens to 0x000...? It wouldn't change the token supply count, but it'd be the same from a user perspective

Yes this effectively burns the token, but because it does not remove the token from the supply calculations like quorum and participation are impacted.

For what its worth I would not consider this a high priority issue, but felt it was worth documenting so it can be referenced in the future.

@sohkai sohkai changed the title owner initiated token burn Token Manager: owner initiated token burn Oct 16, 2019
@sohkai
Copy link
Contributor

sohkai commented Mar 18, 2020

Closing; we can evaluate this in future releases of the Token Manager.

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

No branches or pull requests

3 participants