Core–Knots OP_RETURN Dispute Escalates Into a Bitcoin Governance Fight
Bitcoin Knots released a November build retaining a far tighter default for OP_RETURN data than Bitcoin Core v30, as the dispute over relay policy, arbitrary data and node-operator discretion became a broader Bitcoin governance controversy.
By November, a technical disagreement ignited by Bitcoin Core v30 had developed into one of the year’s most visible Bitcoin governance disputes. Core v30, released October 10, raised the default -datacarriersize setting to 100,000 bytes and allowed multiple OP_RETURN outputs, effectively removing the earlier practical relay limit for this form of transaction data. Supporters argued that relay policy should reflect transactions miners could already include; critics argued that permissive defaults encouraged non-monetary data use and weakened node operators’ ability to discourage it.
Bitcoin Knots became the principal software expression of the opposing view. Its November 10 release used an 83-byte default for -datacarriersize, close to the older Core policy and dramatically below Core v30’s 100,000-byte setting. Around the same period, the Reduced Data Temporary Softfork proposal that would later be assigned BIP 110 continued to be revised and debated, adding a possible consensus-level response to what had begun as a relay-policy dispute.
The importance of the episode was not that one implementation changed a configuration value. It was that developers, node operators and users publicly argued over who should set practical network policy, whether relay neutrality or restrictive defaults better served Bitcoin, and how far users should go in coordinating around alternative software. The disagreement illustrated Bitcoin governance in practice: no central authority could settle the matter, and competing implementations, user choice and social coordination became part of the debate.