The Bitcoin (BTC) network needs a “conservative” client implementation to protect its monetary properties and reinforce decentralization, Jimmy Song, co‑founder of ProductionReady, told Cointelegraph. ProductionReady is a nonprofit that funds open‑source Bitcoin node software development and education.
Song said the organization has a bias against large code changes unless there is overwhelming community support. “The general principle is: if you’re not sure a change makes the money better, don’t make it,” he said.
ProductionReady plans to restore the 83‑byte OP_RETURN limit for arbitrary, non‑monetary data in Bitcoin transactions, arguing that limiting arbitrary data helps keep node storage costs low — a key factor in enabling ordinary users to run full nodes. “The more self‑sovereign Bitcoin users are, the more decentralized and resilient the network becomes. That means keeping the cost of running a node low enough for ordinary people to do it,” Song said. He added that when storage and bandwidth requirements grow, fewer people verify transactions themselves and the network centralizes by default.
Maximizing the number of accessible nodes reduces the risk of false transactions or collusion by a small set of actors. ProductionReady frames a conservative client as one that takes the tradeoff between new features and node resource requirements seriously.
The debate over node storage and on‑chain data intensified in 2025 after Bitcoin Core developers changed the OP_RETURN limit in Bitcoin Core version 30 from 83 bytes to 100,000 bytes despite substantial community pushback. The proposal reportedly received roughly four times as many downvotes as upvotes on its GitHub pull request. Bitcoin Core 30 went live in October 2025, and the change led to a historic surge in nodes running Bitcoin Knots, an alternative Bitcoin node implementation.
As of recent data, there are about 4,746 Bitcoin Knots nodes, representing roughly 21.7% of the network; in 2024 Knots represented about 1% of nodes. Bitcoin Core remains the dominant software, with around 77.8% of nodes running some version of Core. The Core 30 OP_RETURN decision and the resulting shift toward alternative clients underscore ongoing tensions about protocol changes, decentralization, and who gets to decide the tradeoffs for Bitcoin’s long‑term resilience.