forked from ordinals/ord
-
Notifications
You must be signed in to change notification settings - Fork 37
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Allow including metadata when burning inscriptions (ordinals#4045)
- Loading branch information
Showing
19 changed files
with
432 additions
and
75 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -34,7 +34,7 @@ impl Charm { | |
Self::Burned, | ||
]; | ||
|
||
fn flag(self) -> u16 { | ||
pub fn flag(self) -> u16 { | ||
1 << self as u16 | ||
} | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
Burning | ||
======= | ||
|
||
Inscriptions may be burned by constructing a transaction that spends them to a | ||
script pubkey beginning with `OP_RETURN`. | ||
|
||
Sending inscriptions to a so-called "burn address" is not recognized by `ord`. | ||
|
||
Burned inscriptions receive the "burned" charm, recognized with 🔥 on the | ||
inscription's `/inscription` page. | ||
|
||
When burning inscriptions, CBOR metadata may be included in a data push | ||
immediately following the `OP_RETURN`. | ||
|
||
Burn metadata is unstructured, having no meaning to the underlying protocol, | ||
and should be human readable. It is displayed on the burned inscription's | ||
`/inscription` page, in the same manner as inscription metadata, under the | ||
heading "burn metadata". | ||
|
||
Use it, if you feel like it, to commemorate the inscription, celebrate the | ||
closing of a collection, or for whatever other purposes you so desire. | ||
|
||
Data pushes after the first are currently ignored by `ord`. However, they may | ||
be given future meaning by the protocol, and should not be used. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.