Several things to unpack here. “You can still embed data in other fields.” Nirvana Fallacy. Core actively removed the guardrails. BIP-110 puts them back. The argument that imperfect protection means no protection is the same logic used to justify removing seatbelts because they don’t prevent all deaths. “Chain split unless miners cave like SegWit.” You just described exactly how a UASF works — and then called it unlikely because BIP-110 is “pointless.” That’s circular. The pointlessness is your assertion, not your evidence. “Risk of large reorgs.” You then wrote: “I don’t think this is likely.” You raised a catastrophic scenario you don’t believe in, to imply recklessness. That’s a phantom threat — a rhetorical device, not an argument. “Driven by ideology.” So is every position in this debate. Yours included. The whitepaper is clear: peer-to-peer electronic cash. Not peer-to-peer data storage. BIP-110 restores relay policy toward that standard.

Replies (1)

BIP110 has nothing to do with relay policy; is is a change to consensus rules. Core changed a relay policy. BIP110 is an attempt to change consensus. Core's move did not render any Bitcoin frozen. It is impossible to know in advance how much may be frozen by BIP110 through things like presigned transactions, common in inheritance schemes. To do nothing of value. Moving jpgs from opreturn into other fields in a transaction and bloating the utxo set while doing so isn't fixing anything. It's just a power trip from the sorts of people who have openly stated that they'd like unilateral control (mechanic) or would like to incorporate law enforcement measures into Bitcoin (Luke). You can't inhibit arbitrary data on chain, save through size limits, any more than you can prevent your enemies from using Bitcoin. Deal with it.