ord icon indicating copy to clipboard operation
ord copied to clipboard

Allow burning inscriptions

Open casey opened this issue 2 years ago • 5 comments

It should be possible to burn inscriptions, to indicate that they can't be traded or transferred.

Add a subcommand ord wallet burn INSCRIPTION_ID which takes an inscrpition and sends it to an OP_RETURN. It should strip it down to the minimum size and return any postage to the user. Since the intention is to burn a sat, it the output size should be 1, not zero.

This should also allow including either an arbitrary UTF-8 string payload, or an arbitrary binary payload, and mark which one it is so they can be displayed correctly.

casey avatar Jan 22 '23 20:01 casey

Suggest confirmation step (eg. re-enter inscription string like deleting a GitHub repo). But, I guess that's interactive and thus bad for automation. Maybe ok without conf for CLI client...

batcavekid avatar Jan 23 '23 11:01 batcavekid

In general I don't think confirmation steps are a good idea for CLI tools. We let the user toast zillions of sats using --fee-rate 100 on a 1 meg inscriptions, or send 10 BTC, with no confirmation. For consistency, and to make sure that users don't expect a confirmation step when there is none, I don't think we should add any to the CLI.

casey avatar Jan 23 '23 18:01 casey

Makes sense, warning would be more useful in a gui.

batcavekid avatar Jan 26 '23 09:01 batcavekid

Like burn idea.

Is "scrub" as an alternative to "burn" possible? Meaning, for a mutable inscription user would have 2 options:

  • burn
  • scrub

Particularly if it is a rare sat, user may want to clean the sat of inscriptions and keep it, or re-inscribe it, rather than burning.

If immutability is implemented later (eg. via burning the Collection (Prime) Sats), there would be no option to scrub subordinate sats, only burn them.

batcavekid avatar Jan 26 '23 09:01 batcavekid

New burn PR = #3437

onchainguy-btc avatar Apr 14 '24 20:04 onchainguy-btc