You’re missing the point. Models suggest that even if 99.9% of nodes run restricted policy, a toxic op_return and a motivated attacker will still find a way to embed a large file on the network. Core 30 changed everything. Prior to it was possible to limit this attack vector with stricter policy. Consensus change is the only mitigation right now. That’s why it’s more important than ever to realise the risk associated with compromised dev team. We should stop pretending consensus is effective defence against human governance. It’s good enough, but not a painkiller.

> BIP 110 which is actually changing OTHER people's experience of Bitcoin

Yes, if you’re using Bitcoin as money it will actually *improve* your experience.

If you’re using it for something else, it will degrade your experience. Simple as that.

The question we need to answer is do we want other uses for Bitcoin besides money. My answer is a clear NO and my node reflects this answer.

> IMO we should convince people / nodes to change their relay policy back to 80 cap on op_return and to solo mine with ocean defining their own block

We tried this for 3 years.

Economic incentives can become mal-incentives. Once a mal-incentive exists long enough, entire industries start depending on it. At that point fixing the problem threatens the people profiting from the distortion. The incentive system becomes self-defending. I hope you can see the irony. If you don’t, I can give you some real live examples to prove incentive can be co-opted just as easily and then be turned on its head. See Goodheart’s Law for reference. And substitute “the measures” for “miner revenue”, “security budget” or whatever made up metric you like to justify miners mining spam.

I feel the same anger.

You have much to learn.
1) The supply of Bitcoin can easily be diluted with wrappers and paper claims off chain. Past cycle is evident for this.
2) The spam issue raises the bar for new participants bc it’s more difficult to do an IDB (4GB of RAM HW no longer works), you need 8-12 at minimum. The same problem is here for old participants who need to make a fresh sync of the blockchain due to critical errors, or changing hardware.
3) the Blocksize limit doesn’t prevent storage concerns, see below image for details.

Thank you for putting the whole clown show into words this well.

In Bulgaria too 😅

Pure spectacle

lol what 😆