Consider renaming Rune ID to Rune Pointer about runestone HOT 7 CLOSED

rune location?

from runestone.

I think that would be confusing, since I would think of the location of a rune as being the outputs which currently have a non-zero output of the rune.

from runestone.

Another idea is "slot". I've used the word "slot" to refer to some combination of block height / transaction index / output index, but it's not a common use.

from runestone.

I think that would be confusing, since I would think of the location of a rune as being the outputs which currently have a non-zero output of the rune.

Gotcha. Internally on my end, I refer to tx as location and output indices as positions.

from runestone.

Question, did we ever agree on whether runestones in multiple OP_RETURNs of a nonstandard transaction are allowed or not? If not, what's the expected behavior to resolve two different runestones? (First one in output order, or both invalid?)

from runestone.

Also, other names to "rune pointer" are:

• rune reference
• rune handle
• rune descriptor
• issuance ID
• rune birthday (works well with #35 with BLOCK/TX as some sort of date looking string)

from runestone.

I think Rune ID is okay for now.

from runestone.