A fierce dispute among Bitcoin developers over a proposal to eliminate the long-standing 80-byte constraint on OP_RETURN outputs has driven a 49% surge in the node count of the alternative client Bitcoin Knots in April 2025.
The OP_RETURN Debate: Clash of Ideologies
The proposal, introduced by developer Peter Todd, aims to abolish the 80-byte limit on OP_RETURN data, potentially allowing much larger datasets to be embedded directly into the Bitcoin blockchain. Proponents argue the current cap is arbitrary, outdated, and easily bypassed—pointing to how Ordinals inscriptions and Runes have already circumvented the restriction. However, the proposal has faced strong opposition.
Bitcoin Core maintainer Luke Dashjr has emerged as a leading critic, branding the plan as "utter insanity" and a direct assault on Bitcoin's design ethos. He warns that loosening data guardrails could flood the blockchain with spam, undermining the network's primary purpose as a peer-to-peer electronic cash system. The dispute has triggered heated GitHub debates, accusations of censorship, and a notable increase in the deployment of Bitcoin Knots, an alternative full-node implementation forked from Bitcoin Core.
Bitcoin Knots Node Count Rises 49% in April
Bitcoin Knots offers expanded features, additional patches, and finer-grained mempool policy controls, allowing node operators to decide which transactions to relay or archive. On April 1, 2025, only 674 visible Knots nodes were recorded. By the end of April, that number had climbed to 1,006—a 49% increase. Yet Bitcoin Core remains the dominant client. As of 4 p.m. Eastern Time on Saturday (May 3), 20,213 public Bitcoin Core nodes were reachable, representing 94.78% of the total 21,326 public nodes. Knots accounts for roughly 4.72%.
Even If Knots Dominates, It Cannot Block Transactions
An important technical nuance: even if Bitcoin Knots were to become the most dominant client and decline to relay certain transactions it deems spam (e.g., oversized OP_RETURN data), Core nodes would still propagate those transactions as long as they adhere to Bitcoin's consensus rules and Core's mempool parameters. More critically, if miners running Core nodes adopt permissive mining policies, they would ultimately include those transactions in blocks, although propagation might slow if Knots controlled the majority of relay nodes.
Furthermore, even in a hypothetical scenario where Knots nodes outnumber Core nodes, Knots would not automatically become "Bitcoin." As long as both clients follow the same consensus rules, both represent Bitcoin. A client only ceases to be aligned with Bitcoin when a hard fork rewrites those rules, and the nodes, community, and miners collectively decide on the longest, highest-proof-of-work chain as the authentic ledger. Thus, while the surge in Knots nodes is noteworthy, it remains insufficient to thwart data storage if the OP_RETURN cap is lifted.