-
Notifications
You must be signed in to change notification settings - Fork 375
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
[Discussion] std.ZeroAddress
#2316
Comments
If we prioritize transaction transparency, approach 2 is likely the better method |
@leohhhn : |
Yes, the feature seems useful and will likely improve readability. Just considering whether |
We could have a "consts" stdlib or similar for this if we had more constants. Related. I think @thinhnx-var @linhpn99 - would you be open to doing a bit of research on the best way to do this? One solution is to simply have a constant that is If you can, after doing the research, please post your suggested approach either here on in the PR description. |
@leohhhn |
Good idea. Which is best:
|
@grepsuzette |
Description
Should we have a
ZeroAddress
constant in Gno which will represent a universal burn address? This should be an address for which nobody can obtain the private key. I've found it missing multiple times when developing.For example, in the case of GRC20 and other similar tokens, people usually send the tokens they want to burn to a zero address.
This "burn" functionality can be implemented in two ways as I see:
ZeroAddress
constant in Gno, for example in thestd
package, for which everyone knows the private key is not obtainable.WDYT?
The text was updated successfully, but these errors were encountered: