A heated dispute over the proposed removal of the 80-byte OP_RETURN limit has intensified within the Bitcoin development community, driving a notable surge in adoption of the alternative client Bitcoin Knots. Node count for Knots rose 49% in April, from 674 on April 1 to 1,006 by month's end. Despite this growth, Bitcoin Core remains the overwhelmingly dominant client, controlling 94.78% of reachable public nodes.
The Proposal: Peter Todd's Push to Abolish the 80-Byte Ceiling
Developer Peter Todd introduced a proposal to eliminate the longstanding 80-byte restriction on OP_RETURN outputs. This change would allow much larger datasets to be embedded directly into the Bitcoin blockchain. Proponents argue the current cap is arbitrary, outdated, and easily circumvented—as evidenced by Bitcoin Ordinal inscriptions and Runes tokens already bypassing the limit. Opponents, however, view the proposal as antithetical to Bitcoin's design ethos, warning it could open the floodgates to chain bloat and spam.
Luke Dashjr: 'Utter Insanity'
Bitcoin Core developer Luke Dashjr has been the most vocal critic, labeling the plan “utter insanity” and framing it as a direct assault on the network. He warns that loosening data guardrails could overwhelm the blockchain with spam. The dispute has fueled intense debates on GitHub, accusations of censorship, and a noticeable uptick in Bitcoin Knots deployments in April. Knots is an alternative full-node client derived from Bitcoin Core, designed for granular control over mempool policies and transaction relay.
Compared to Bitcoin Core, Knots ships with expanded features, additional patches, and finer mempool-policy dials that govern which transactions a node relays or archives. This makes it attractive to operators who want to filter out what they consider spam—such as large OP_RETURN data payloads.
Network Composition: Core Dominance Unshaken
As of early May, 20,213 public Bitcoin Core nodes were reachable out of a total of 21,326 public nodes. Core accounts for 94.78% of the network, while Bitcoin Knots holds roughly 4.72%. Even if a Knots node refuses to relay oversized OP_RETURN transactions, a Core node can still propagate those transactions as long as they satisfy Bitcoin's consensus rules and Core's mempool parameters.
Theoretical analysis shows that even if Knots became the most dominant client and chose to decline relay of consensus-valid transactions like large OP_RETURN payloads or Ordinals, Core nodes—aided by the remaining minority of peers and miners—could still shepherd those transfers to finality. Permissive mining policies running on Core nodes would ultimately include the transactions in blocks, though propagation might slow if Knots controlled most relay pathways.
Consensus Integrity: Both Clients Represent Bitcoin
It is important to note that Knots would not become “Bitcoin” by sheer node count. As long as both Knots and Core adhere to identical consensus rules, each represents Bitcoin. A client ceases to align with Bitcoin only 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. Therefore, while Knots' node count increase is noteworthy, it remains insufficient to prevent data storage on the Bitcoin blockchain should the OP_RETURN cap be lifted.