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

Clean up burn command #3976

Merged
merged 19 commits into from
Oct 3, 2024
Merged

Clean up burn command #3976

merged 19 commits into from
Oct 3, 2024

Conversation

casey
Copy link
Collaborator

@casey casey commented Oct 3, 2024

No description provided.

We already use `recipient` in the rest of our codebase
TARGET_POSTAGE is the default, so we don't need to specify it.
It's shorter and just as clear.
TARGET_POSTAGE is already "not too many sats", so semnatically it's the
same as MAX_BURN_SATS, and both are 10,000 sats.
Tests should be written to cover bugs that we might conceivably have.
However, in this case, the argument to the burn function is an
inscription ID, so we cannot conceivably accept a rune.
We already know it's an inscription ID from the type
@casey casey requested a review from raphjaph October 3, 2024 19:55
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.

LGTM!

@casey casey merged commit 46611bd into ordinals:master Oct 3, 2024
5 checks passed
@casey casey deleted the refactor-burn branch October 3, 2024 20:57
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.

2 participants