ELI5 anyone? 🫠

@Luke Dashjr did you or Larry ever see this comment in the filter-ordinals gist? It had slipped out my mind already.

Gist

filter-ordinals.patch

GitHub Gist: instantly share code, notes, and snippets.

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 😬

ngl, this is fun 😬

New psyop just dropped. The existing standardness rules such as the 80 byte limit on OP_RETURN are now called "paternalisms", and a few devs have started to make moves to remove them from Bitcoin Core v26 and onwards. This would change the default relaying policy to further encourage the use of Bitcoin as a permanent storage medium. If you want to voice your concern over this development you can do it in this Pull Request:

GitHub

Remove arbitrary restrictions on OP_RETURN by default by petertodd · Pull Request #28130 · bitcoin/bitcoin

Any number or size of data-carrying OP_RETURN outputs are allowed, and the -datacarrier option is removed. For those who want to limit data carryin...