69 sats \ 4 replies \ @petertodd 1 Jul \ on: Analysis of 0xB10C's weird bitcoin transaction bitcoin
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.
write
preview
100 sats \ 3 replies \ @supertestnet OP 1 Jul
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"
reply
29 sats \ 0 replies \ @petertodd 1 Jul
Oh! Good point, that would have been cool!
reply
100 sats \ 1 reply \ @vostrnad 1 Jul
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.
reply
100 sats \ 0 replies \ @supertestnet OP 1 Jul
Yeah but that would be totally worth it imo. It's a very cool bug and no one ever uses it, an art piece like this would be a great opportunity to showcase it
reply