Unbound inscription off-by-one error in current ordinals.com index

[rafaelcr]

There seems to be an off-by-one error when assigning a location to an unbound inscription at block 879369.

If we look at the last unbound inscription at block 879368 we see its location as

0000000000000000000000000000000000000000000000000000000000000000:0:74620

However, the first unbound inscription in the next block 879369 reports its location as

0000000000000000000000000000000000000000000000000000000000000000:0:74622

Perhaps I'm missing something but shouldn't that inscription be at unbound offset 746621?

[raphjaph]

Ah yes, this is a variant of a bug one of your predecessors found with inscription numbers. See this PR for a fix and this issue in general. It would renumber a lot of inscriptions so we decided that we would have to live with it.

It has to do with the way we process inscriptions that are fee inscribed (the reveal transaction spends it directly into the coinbase).