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

Document runes #3380

Merged
merged 19 commits into from
Mar 28, 2024
Merged

Document runes #3380

merged 19 commits into from
Mar 28, 2024

Conversation

casey
Copy link
Collaborator

@casey casey commented Mar 27, 2024

No description provided.

@rot13maxi
Copy link
Contributor

yo dog. i heard you like prs. so i pr'd your pr so you can review while you review

casey#2

Copy link
Collaborator

@raphjaph raphjaph left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LFG!

@casey casey enabled auto-merge (squash) March 28, 2024 00:40
@casey casey merged commit 6c356eb into ordinals:master Mar 28, 2024
5 checks passed
vuviettai pushed a commit to codelight-co/runebeta_ord that referenced this pull request Mar 28, 2024
@casey casey deleted the document-runes branch March 28, 2024 20:53

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.

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)?

Copy link
Collaborator Author

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.

harutyunaraci pushed a commit to brc721-core/ord that referenced this pull request Mar 30, 2024
harutyunaraci added a commit to brc721-core/ord that referenced this pull request Apr 2, 2024
harutyunaraci pushed a commit to brc721-core/ord that referenced this pull request Apr 2, 2024
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

Successfully merging this pull request may close these issues.

4 participants