nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk did you or Larry ever see this comment in the filter-ordinals gist? It had slipped out my mind already.

https://gist.github.com/luke-jr/4c022839584020444915c84bdd825831?permalink_comment_id=4599817#gistcomment-4599817

Now that I've learned how to decode transactions I see that the particular one I mentioned has extra opcode noise before the data envelope. To my untrained eye it looks like a conscious attempt at evading #ordisrespector 😬

J’ai tenté quelque chose au cas où ils venais a changer pour OP_TRUE et OP_NOTIF comme décrit dans le mail

https://gist.github.com/Retropex/64e81f934364387c3623ff674f3ba0e2

https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-July/021819.html

Reply to this note

Please Login to reply.

Discussion

Whoa, good work 😶

It wasn’t complicated I just changed the OP code. 😅 I just hope it will work I don’t know how to test it.

Excellent! investigative work..👏👍🙂

As you can see, Bitcoin is under #attack from WITHIN. We the #virtuous #FullNodes and #Bitcoin loyalist must take back control of the code.

Strip out all the subversive non-Bitcoin financial code. Then clean it up and lock it down for the long run..⚖️👮‍♂️😠🧡👑🗽