Michael Saylor, Bitcoin Core, and Knots: Navigating the OP_RETURN War

A look at Michael Saylor's stance on the Bitcoin Core vs. Knots debate over OP_RETURN limits, and the broader implications for Bitcoin's future.

The Bitcoin community is currently engaged in a fierce debate regarding data storage. This debate pits Bitcoin Core, the most popular software for node operators, against Knots, a fork focused on greater user control. At the heart of this disagreement lies the contentious change to OP_RETURN.

Saylor's Take: A Word Salad or Strategic Ambiguity?

When asked about the OP_RETURN debate, Michael Saylor, chairman of MicroStrategy, gave a response that was seen as vague. He called the debate a "second-order or maybe even a third-order change." Saylor cautioned against unintended consequences from even well-intentioned upgrades to Bitcoin. While some interpreted his comments as pro-Knots or pro-ossification, others disagreed. Ultimately, his response lacked technical depth, failing to address key aspects like data storage limits and node costs.

The OP_RETURN War: Core vs. Knots

The core issue revolves around Bitcoin Core's v30 update, which increases the mempool's default datacarrier limit for OP_RETURN from under 90 bytes to roughly 100,000 bytes. Knots, on the other hand, plans to maintain the lower data cap as a deterrent to arbitrary data storage. This has led to what's been called Bitcoin's "OP_RETURN War."

Knots argues that Core v30 has conceded to corporate data storage interests, which goes against Bitcoin’s core function as a non-fiat financial system. Core v30 proponents claim that spamming is unstoppable, as spammers will continuously find ways to bypass filters.

Relay Fee Reduction and Node Dominance

Bitcoin Core 29.1 has also lowered the default minimum relay fee for transactions by 90%. While individual node operators can adjust this, most are expected to stick with the default. Although, Bitcoin Knots 29.1 does not inherit Bitcoin Core’s new defaults. Instead, with this update, Knots decided to “make most policy options configurable in GUI Options, and add ‘corepolicy’ option to use Bitcoin Core defaults.”

Currently, Bitcoin Core dominates the node landscape, but Knots maintains a significant presence. The exact dominance of each version is hotly contested.

Conclusion: A Fork in the Road?

The debate between Bitcoin Core and Knots highlights fundamental disagreements about Bitcoin's direction. Will it embrace arbitrary data storage, or will it prioritize its role as a peer-to-peer electronic cash system? The answer remains uncertain, but one thing is clear: the Bitcoin community is passionate and engaged, even if they sometimes act like cats and dogs. Whatever happens, it's sure to be an interesting ride. Buckle up, buttercups!