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

Burn token which are used for buying: Burnback #32

Open
martinkrung opened this issue Mar 6, 2021 · 1 comment
Open

Burn token which are used for buying: Burnback #32

martinkrung opened this issue Mar 6, 2021 · 1 comment
Labels
enhancement New feature or request experimental

Comments

@martinkrung
Copy link
Member

Burn token is a quit often used to take a token out of circulation

Detailed Description

If a buyback is done in an open market sometimes the token are burned to 0x0000... This flag could forward the token directly to 0x000 after settlement.

Context

Burnback for DXD token?

Possible Implementation

Forward incoming token to 0x00..

@martinkrung martinkrung added enhancement New feature or request experimental labels Mar 6, 2021
@martinkrung martinkrung added this to the MVP milestone Mar 6, 2021
@nicoelzer
Copy link
Collaborator

nicoelzer commented Mar 6, 2021

@martinkrung I guess there are different use case where IDO projects want to burn tokens, so we could implement this in a reusable pattern.

I could envision we have multiple token utilities functions (token burns, tokens mints, token creations, ..), that are provided by a "token module" which can easily be imported in templates.

Ruff specification for the token burn function:

  • token (address)
  • amount (uint256)
  • burnDate (uint256)

@martinkrung martinkrung modified the milestones: MVP, Extended Product Mar 15, 2021
@martinkrung martinkrung modified the milestones: Extended Product, Extended Product (Vision, on zen) May 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request experimental
Projects
None yet
Development

No branches or pull requests

2 participants