Filters buddy.. Filters. You will get there eventually.. Reel in your ego and admit you are wrong here.
Discussion
no... I just told you why. It's not filters at all. OP_RETURN doesn't get a discount, witness data does. So rather than putting arb data in OP_RETURN, you stuff the witness with it. This makes more unspendable UTXOs (bad for Bitcoin). Removing the limit does not stop this either. I don't have any ego man. I'm just arguing facts and you rebut with arguments that fall flat or don't make any sense.
Dude, you just making yourself look more silly. They spam witness data cos they can't freely spam op return.
Yes... They can. It's more expensive. And not because of filters. It's because witnesses data gets a discount.
You are the one looking more silly sir.
So which is it, cheaper or more expensive? LOL 😄
What are you not understanding... OP RETURN data is more expensive than witness data. Doesn't matter how many bytes...
Well done Sherlock, now you get it. 
What do you mean now I get it. I don't think you get it at all. What do you think I just said?
It costs more to spam op return
And why do you think that is?
Filters
Wrong. And I've explained to you why. You just aren't listening.
again... you can make a a tx with less than 1s/vb fee already and always have been able to...
Yes, but most people blocked them with filters.
Yes, they blocked them. On THEIR NODE. They did nothing to prevent it from being mined. They are concensous, non standard transactions.
Non-standard transactions. Right. And not appearing in most peoples mempool. Sort of "filtered"... Keep going...
How are you not understanding that filters only affect your node and not the network.
It's because stuffing the witness is cheaper.
Yes because the filter limit
No... Witness data gets a discount on its weight. OP RETURN doesn't. That's not a filter thing, that's not a policy. That's just how Bitcoin works. Filters have nothing to do with it.
The blockchain overwhelmingly reflects the default mempool policies set within Bitcoin Core.
This is an obvious fact.
You are incorrectly attributing the blockchain's transaction patterns to Bitcoin Core's default mempool policies. They think the blockchain 'reflects' these filters because the filters are actively preventing bad transactions from being included.
This is backwards causation. The mempool policies are purely local settings that only affect what transactions your individual node will relay or store in its mempool - they don't control what gets mined into blocks. Miners can set these filters to whatever they want, or ignore them entirely.
The real reason the blockchain resembles the default policy settings is much simpler: most people naturally create valid, reasonable transactions anyway. The blockchain looks 'clean' not because the filters are working to keep it clean, but because there wasn't much junk to filter out in the first place. The filters are largely redundant - they're rejecting transactions that most users wouldn't create anyway.
You have it the wrong way round.
They don't do anything to the network. Prove me wrong.
Where are op return codes >80?
There are very few because they don't make any sense financially. Do you want me to submit one now to prove you wrong send me 5K and I will just like I started this conversation with.