22 sats \ 19 replies \ @ChrisS 10 Aug \ on: First transaction using OP_CAT on the mainnet bitcoin
How did they use op_cat when bitcoin core nodes don’t know how to deal with that op code on the stack?
Here is rijndaels answer in a comment on the post:
“ The hex value that used to be OP_CAT is defined to be an OP_SUCCESS in taproot, meaning that if its in a script, the script is valid. But, since it used to be OP_CAT, software like the mempool-space parser parses it as OP_CAT. BIP-420 picks that value to be OP_CAT, so if CAT were active today, this would be a valid tramsaction. To un-upgraded nodes (like… almost all of them), it is still a valid transaction because it doesnt see CAT, it sees SUCCESS. This is how we can add CAT as a softfork. Upgraded nodes will see 0x7e and interpret it as CAT. Unupgraded nodes will see it as SUCCESS. ”
Likely a backend deal with mara
reply
It doesn’t matter how much you pay the miners, the nodes won’t verify an invalid transaction.
reply
It’s a repeat of the bigger block debate
reply
reply
The nodes wouldn't validate the bigger blocks that hard forked into BCH
The blocksize war of 2017
reply
reply
I didn't say the transaction was similar
What is similar is that nodes won't verify an invalid transaction even if miners do
reply
Mempool has it labeled as 'Seen in Mempool'
reply