OP_RETURN Dispute Opens a New Bitcoin Core Governance Fight
Debate over Bitcoin Core’s OP_RETURN relay policy broadened into a dispute about transaction filtering, inscriptions, node policy, and the authority of maintainers to set defaults.
By early May 2025, a technical argument over Bitcoin Core’s treatment of OP_RETURN data had become a broader governance dispute. Developers debated whether Bitcoin Core should increase or remove its default relay-size limit for OP_RETURN outputs, which are commonly used to attach arbitrary data to transactions.
The immediate technical issue involved relay policy rather than Bitcoin’s consensus rules. Nodes could already choose their own policy, and miners could include transactions that other nodes might not relay. The controversy nevertheless touched deeper questions: whether software defaults should discourage large non-payment data, whether filtering was effective once users could route around it, and how much influence Bitcoin Core maintainers should exercise over network policy.
May marked the public origin of a conflict that did not disappear after a single code discussion. Later in 2025, the issue became associated with increased use of Bitcoin Knots and a wider community argument over spam, inscriptions, developer authority, and node-software choice. The early relay-policy debate had become a recognizable Bitcoin governance controversy with consequences that continued through the rest of the year.