-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Document runes #3380
Document runes #3380
Conversation
yo dog. i heard you like prs. so i pr'd your pr so you can review while you review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LFG!
|
||
A rune may not be minted in or after the block whose height is equal to the end | ||
offset plus the height of the block in which the rune was etched. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the behavior if neither a premine nor terms are specified? It seems the default for each of those is 0/do nothing. Does that etch a valid rune with 0 max supply (effectively "burning" the name), or does it create a cenotaph (and burn all runes that are also on that tx)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If neither premine nor terms are supplied, the supply is zero, but the runestone is not a cenotaph.
This reverts commit b8dfbf3.
No description provided.