Very simple for me. 1- if filters don't work at all, it's ok to leave it. 2-if they work, leave it or spam will skyrocket. 3-in doubt, don't change bitcoin. Core handled this very badly. So for me it's run old version of Core, or Knots, to leave bitcoin as it is now.

op_return filter and limits are so bad that everyone has been running them since 2013 and everyone is running them right now, so I but now apparently everyone is retarded, and all those past devs didn't know shit either.

Core has been taken over. Instead of telling them to fuck off they just dropped their pants to them. It's no longer defending node runners interests. If this isn't an attack I don't know what is. We must be as a network absolutely hostile to this, (like they are) you don't fight hostility with diplomacy. Fire Core, let them Jpegs threat Luke or submit PR for him. lol.

X (formerly Twitter)

Leonidas 🧡 $DOG (@LeonidasNFT) on X

An open letter to Bitcoin Core, Any serious attempt by Bitcoin Core to tighten policy rules or censor Ordinals and Runes transactions will be met ...

Segwit : we are going to give a data discount to incentivise less utxos. Result: spam. Taproot : more data with the segwit discount, more spam. Guess what will happen with op_return to tackle again utxo set? lol. Guess what stops utxo set bloat? fees.

Core : we changed op_return limits so that spam is less harmful to the utxo set, filters don't work. - So does this stop the spam in the utxo set? - No, we just hope the spam bad actors consider this approach to do less harm. lmao.

Core arguments are like those normies who say any attempt at privacy is useless bc you have to give some data to someone eventually or someone leaks your phone to others and "what do you have to hide".

how will nodes running on machines with AV handle malicious code (virus) on Core 30 op_return.