Jimmy Song, a prominent Bitcoin (BTC) developer and advocate, criticized the Bitcoin Core developers’ decision to eliminate the OP_Return limit for non-monetary data on the Bitcoin blockchain in the upcoming Bitcoin Core 30 upgrade, labeling it as a “fiat” mindset.
Song accused the Core developers of dismissing user concerns about the removal of the OP_Return limit, currently set at 80 bytes, and neglecting the substantial backlash from the Bitcoin community and node operators. He also stated:
“The claim that spam is hard to define, and therefore we shouldn’t differentiate in the software, is a futile argument from fiat politics that pretends not to recognize the obvious, preventing the real debate from commencing — the non-monetary applications of Bitcoin are spam.
While one can debate if this is a desirable situation, claiming it can’t be defined is merely a delaying tactic that fails to address the genuine discussion about its actual effects — especially considering the long-term consequences of this change,” Song added.
The OP_Return controversy has persisted for almost six months, echoing the Bitcoin block size wars of 2015 to 2017, which ultimately led to a hard fork resulting in the creation of Bitcoin Cash (BCH). This has prompted speculation in the Bitcoin community about whether the OP_Return disputes might lead to a similar division.
Related: The creators of Taproot didn’t anticipate its ‘trolling value’ — Bitcoin developer
Node runners opt for Bitcoin Knots in a historic migration
The unilateral decision by Bitcoin Core developers to lift the OP_Return data limit has created divisions within the Bitcoin community, prompting a historic influx of Bitcoin node runners to Bitcoin Knots, an alternative implementation of Bitcoin node software.
This rise in nodes utilizing Bitcoin Knots, which now represent about 20% of the network compared to roughly 1% in 2024, marks a dramatic increase within just nine months.
Knots permits node runners to impose strict data size limitations, which supporters argue is essential for maintaining the decentralization of the Bitcoin protocol.
The Bitcoin ledger has accumulated approximately 680 gigabytes of data since the decentralized protocol’s inception in 2009, owing to Bitcoin’s straightforward architecture and rigid data limits.
Bitcoin’s minimal data storage requirements enable anyone to run a node on standard retail computer hardware for as low as $300, promoting accessibility and ensuring maximal decentralization.
In contrast, higher-throughput blockchain networks and smart contract platforms, generating much larger data volumes, may cost tens of thousands of dollars to operate and necessitate specialized commercial hardware, restricting node operation and consensus rule enforcement to affluent investors and large corporations.
Rigid hardware requirements lead to increased centralization of a blockchain protocol and a heightened risk of collusion among a few nodes to alter consensus rules or reverse transactions.
Magazine: Bitcoin’s long-term security budget dilemma: Impending crisis or mere FUD?
