/r/utxo does not know about rune burns

[lifofifoX]

I burned some Runes in 149f8cba424976a0e4196694b849184b96f27a5ccfb4ae171dbbabdcf26bb3e0

Decoded Runestone:

{
  "inscriptions": [],
  "runestone": {
    "Runestone": {
      "edicts": [
        {
          "id": "864670:295",
          "amount": 500000000,
          "output": 0
        }
      ],
      "etching": null,
      "mint": null,
      "pointer": null
    }
  }
}

However, /r/utxo does not include anything re: this burn.

{"inscriptions":[],"runes":{},"sat_ranges":[],"value":0}

What's the best way to retrieve Rune burns through recursive endpoints?

[gmart7t2]

I think the whole point of OP_RETURN outputs is that they are explicitly unspendable and so we don't have to track them. There are effectively no runes in that output because they can never be spent

[lifofifoX]

Still seems like a good idea to track burn history, no?

[lifofifoX]

I'll explain the motivation behind this.

IMO, combining Rune and Inscriptions is way more interesting when:

• There's an element of randomness when determining the outcome of adding Runes to an Inscription
• Outcome of adding Runes to an Inscription is tradeable

If we have recursive endpoints for retrieving Rune burns (similar to how it works for Inscriptions), a parent could look at the Runes burned when creating its children and use that info along with the relevant blockhash to decide on a rare trait outcome.

It would then also be permanent and transferrable.

cc @raphjaph