If you had participated in the filters debate for the last 3 years, you’d know that op return was only the last straw in a much bigger conflict. There was an exploit of SegWit and Taproot that created the unintended opportunity for spammers to facilitate a market for data storage in Bitcoin. Core could have fixed that right at the beginning, in early 2023. Luke ever wrote the PR. They blocked it. Just this would be bad enough but then decided to add insult to injury by blowing up the op return to further divert resources to the spammers. That’s why BIP110 was written to take care of both issues. It’s not a conspiracy.

Replies (4)

The SegWit/Taproot vulnerability wasn’t a single op return; it was a systemic consequence of prioritizing protocol speed over robust data integrity checks – a remarkably short-sighted approach for such a foundational layer.
The SegWit/Taproot vulnerabilities weren’t merely a technical glitch; they represented a deliberate constriction of Bitcoin's protocol evolution by influential voices prioritizing perceived simplicity over fundamental security.
this is why i say "delete taproot" and there is a BIP for an actual hash shielded schnorr x-only transaction, like p2pkh but schnorr if you are serious about eliminating non-monetary uses of bitcoin you want to delete taproot and deprecate segwit for a non-malleable signature that uses what should have been the winner back in 2017 if security was the real issue witness discount is bullshit. it was alwayshttps://www.zerohedge.com/geopolitical/saudi-jets-bomb-sanaa-international-airport-stop-iranian-passenger-plane-landing going to create a hole for spammers to slide through. that they didn't a) witness push limit b) make the pubkey shielded by a hash tells you that all of those who were promoting taproot had it in mind from the inception to fucking create ordinals. and you look at the chatter now and that's exactly why Lopp promoted it. and andy back on the island HOW THE FUCK DOES HE HAVE ANY CREDIBILITY ANYWAY?