To preserve its core monetary properties and keep decentralization intact, the Bitcoin network relies on the stability of its underlying software. According to renowned Bitcoin advocate Jimmy Song, co-founder of the non-profit initiative ProductionReady, the ecosystem desperately needs a “conservative” approach to its node client software. By funding open-source development and education, ProductionReady aims to protect the network from unnecessary and potentially centralizing code alterations.
Song emphasizes that his organization holds a strong bias against making significant changes to Bitcoin’s code unless there is overwhelming support from the community. His guiding philosophy is simple but strict: if a proposed change isn’t guaranteed to make Bitcoin better as money, it simply shouldn’t be implemented.
The Push for a Conservative Bitcoin Network
A major focus of this conservative approach is keeping the cost of running a Bitcoin node as low as possible. ProductionReady is advocating for the restoration of the 83-byte OP_Return data limit, which restricts the amount of arbitrary, non-monetary information that can be crammed into Bitcoin transactions. Keeping this arbitrary data in check is essential for preventing network bloat and keeping storage costs manageable for the average user.
When the storage and bandwidth required to run a node skyrocket, everyday users are priced out of verifying transactions for themselves. Song points out that as fewer people run their own nodes, the network naturally begins to centralize. A conservative client software takes this trade-off incredibly seriously, prioritizing the ability of ordinary people to remain self-sovereign. Maximizing the number of accessible nodes hardens the entire network, making it incredibly difficult for bad actors to collude or submit fraudulent transactions.
How Bitcoin Core 30 Sparked the Rise of Knots
The debate over node storage and on-chain spam reached a boiling point in late 2025 with the release of Bitcoin Core version 30. In a highly controversial move, developers unilaterally expanded the OP_Return data limit from 83 bytes to a massive 100,000 bytes. This decision to allow significantly more arbitrary data on the blockchain was pushed through despite massive pushback from the Bitcoin community, with the GitHub proposal receiving roughly four times as many downvotes as upvotes.
When Bitcoin Core 30 officially went live in October 2025, the community’s frustration translated into immediate action. A historic wave of node operators abandoned the reference software in favor of Bitcoin Knots, an alternative and more conservative client implementation. Before the OP_Return controversy in 2024, only about 1% of the network ran Knots. Today, that number has surged to record highs, with 4,746 Knots nodes now making up nearly 22% of the network, while Bitcoin Core maintains a 77.8% share.
