OP_DATA_32(32) b64a57932521f649cc9cfd74e3fb1cdc7fd2428631c30ae98d8ed87d31db16c0

OP_CHECKSIG(172)

OP_0(0)

OP_IF(99)

OP_DATA_3(3) ord

OP_DATA_1(1)

OP_DATA_24(24) text/plain;charset=utf-8

OP_0(0)

OP_PUSHDATA2(77) Pointer ======= In order to make an inscription on a sat other than the first of its input, a zero-based integer, called the "pointer", can be provided with tag `2`, causing the inscription to be made on the sat at the given position in the outputs. If the pointer is equal to or greater than the number of total sats in the outputs of the inscribe transaction, it is ignored, and the inscription is made as usual. The value of the pointer field is a little endian integer, with trailing zeroes ignored. An even tag is

OP_PUSHDATA2(77) used, so that old versions of `ord` consider the inscription to be unbound, instead of assigning it, incorrectly, to the first sat. This can be used to create multiple inscriptions in a single transaction on different sats, when otherwise they would be made on the same sat. Examples -------- An inscription with pointer 255: ``` OP_FALSE OP_IF OP_PUSH "ord" OP_PUSH 1 OP_PUSH "text/plain;charset=utf-8" OP_PUSH 2 OP_PUSH 0xff OP_PUSH 0 OP_PUSH "Hello, world!" OP_ENDIF ``` An inscription with pointe

OP_DATA_7(7) r 256:

OP_ENDIF(104)