-
Notifications
You must be signed in to change notification settings - Fork 15
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
Comments
You might want to consider not using the word ‘burned’… given that the goal of the platform is specific not to burn trees but rather to grow them, it makes it appear that the tree itself has been somehow ‘burned’. I think you want use a different expression.
… On Jul 6, 2020, at 11:09 AM, DavidEzraJay ***@***.***> wrote:
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.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#32>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACZATSSIIKLAELWI4GHVKDR2IHOJANCNFSM4OR3AAPQ>.
|
"Sequester" might be more fitting. Burn does sound bad. |
or carbonize! |
Claim or Realize impact? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: