That would require a different layout of inputs/outputs, since the only input with index higher than all outputs is a P2TR input, and the sighash_single bug is fixed in Taproot.

Oh! Good point, that would have been cool!

I wish he exploited the sighash_single bug. I *thought* he did in input 8 (whose signature uses sighash_one) but I checked the sig and the sighash wasn't one -- because the op_return counts as an output for purposes of calculating the sighash, so he signed a hash of his input plus that op_return "output"

supertestnet

the OP_RETURN output not only pushes text (which is normal) but also pushes all 17 numbers that bitcoin has special opcodes for

 in there too, as bizarrely Bitcoin considers it to also be a data opcode!

That's the only way I can think of for this transaction to be improved.

bitcoin

Analysis of 0xB10C's weird bitcoin transaction

> the OP_RETURN output not only pushes text (which is normal) but also pushes all 17 numbers that bitcoin has special opcodes for

The author also could have put an `OP_Reserved` in there too, as bizarrely Bitcoin considers it to also be a data opcode!

That's the only way I can think of for this transaction to be improved.