Op return limit doesn’t change much of anything. That’s the point. It is a useless bit of code. You can use a myriad of other methods to stuff data into the chain. Most of those methods are worse for the node operators.
I think Maxwell’s commentary on this issue is the most useful https://bitcointalk.org/index.php?topic=5539943.40
The framing of this as one side is pro spam and the other side is anti spam is not correct. No one wants the stupid jpegs except perhaps the money launderers who find them useful. But you can’t stop them because you can’t stop fake pubkeys from being use to store data, you can’t stop miners from mining consensus valid nonstandard transactions.
Login to reply
Replies (3)
What the fallacy?
Dig up stupid!
The Core vs Knots framing is false. The issue is that #bitcoin has been attacked by its CoreDevs, challenging it‘s immutability. Bitcoin must do two things in the absolute. It needs to be scarce, and it needs to be immutable (can never be changed). Or it’s donezo. Core and Knots updating the code, IS the threat. We need to freeze the code. It doesn’t need features. And therefore it doesn’t need maintenance. It’s a ruleset. Not an app. Or it’s dead.