via my node.
Discussion
So you can't via my node or the majority of nodes. >70%.. Why is that I wonder!?
It doesn't matter if 99.9% of nodes run knots. I can always run my own node...
your second point is wrong... again...
So removing the limit in core hasn't increased spam, so knots has worked
🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣
Core has not made a new release yet... 29 is still the current. Removing the limit will not increase spam because the limit never stopped "spam" to begin with.
The limit is still there on all nodes currently by default, yet, I can still make a tx with one beyond the limit...
Why do spammers stay within op return limits then?
Because it's cheaper to stuff the witness with arbitrary data.... You are arguing out of your depth with extreme conviction...
Strong Mac vibes.
Filters buddy.. Filters. You will get there eventually.. Reel in your ego and admit you are wrong here.
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.
You want to "fix" it, then roll back to 2014 and remove OPRETURN and the Segwit discount. That's a hard fork. It's not happening. Running knots is just a virtue signal, not a solution. It does nothing.
Stops spam. Why you use email spam filters? You still receive spam?
Email is not Bitcoin. I won't entertain the argument. They're not even close.
You won't entertain understanding your own thinking? Understood.
Email is extraordinarily centralized. You want that for Bitcoin?
I run knots which makes it more decentralised. You are running core and allowing them to dictate node settings and policy
What? You can set policy however you want to in core? WTF are you talking about. Every node, no matter what flavor, further decentralizes the network...
You are really confused my guy.
Default settings are important, thats why core wanted to remove the ability to change them. I thought you were in favour of decentralisation?
firstly, They DIDN'T remove them. The default limit was changed to like a million bytes or something. Basically no limit. You can still set a limit just fine with core. Even when 30 comes out.
secondly, if and when they DO remove OP_RETUN limit it's just the OP_Return limit. All other policies remain. policies generally exist to make sure the user doesn't fuck something up and make a bad tx. It's not for making sure the network doesn't get the transactions.
I actually don't run core or knots, but I do run a node. I'll let you guess the flavor. It's one that doesn't have any policy restrictions for anything. I can make whatever transaction I want to with my node.
So you need to run a node without filters to spam Bitcoin. Understood. 
I don't spam Bitcoin.
Then stick within 80 limit 
Not my node. I want an accurate picture of the mempool when I make a regular transaction.
Majority of noderunners disagree with you. So you won't have an accurate men pool.
🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣