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

'claim impact' feature #32

Open
Davidezrajay opened this issue Jul 6, 2020 · 4 comments
Open

'claim impact' feature #32

Davidezrajay opened this issue Jul 6, 2020 · 4 comments

Comments

@Davidezrajay
Copy link

The "burned field is "true" or "false" and in the token table.

This feature should lock the token and freeze it, preventing it from further trading. Once a token is burned, it is no longer able to switch entities.

The feature is required for an entity to realize the impact.

@ZavenArra
Copy link
Contributor

ZavenArra commented Jul 6, 2020 via email

@Davidezrajay
Copy link
Author

"Sequester" might be more fitting. Burn does sound bad.

@sebastiangaertner
Copy link

or carbonize!

@Davidezrajay
Copy link
Author

Claim or Realize impact?

@Davidezrajay Davidezrajay changed the title 'Burn' feature 'claim impact' feature Dec 1, 2020
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