--
Share
Bitcoin Core v30 didn’t just push a bad relay policy. It formalized a dangerous consensus-adjacent behavior that allows arbitrary data—including potentially illegal content—to be stored on-chain. This undermines Bitcoin’s utility as a financial protocol, dilutes its blockspace incentive structure, and opens the door for real legal threats to node runners and miners.
What we’re dealing with is not a mempool issue. It’s a systemic shift away from monetary finality toward unbounded, protocol-level ambiguity. The only viable response—the only way to defend Bitcoin’s architecture—is a soft fork that reasserts validation limits at the consensus layer.
When Bitcoin Core v30 uncapped OP_RETURN, it turned a formerly discouraged practice into a relay default. This broke a fragile but important deterrent that kept large-scale arbitrary data storage off the chain.


