Bitcoin’s open-source developer community is facing a heated debate following a new Bitcoin Improvement Proposal (BIP) that aims to temporarily restrict how much arbitrary data can be stored on the blockchain. The move comes in response to growing concerns that the Bitcoin network could be used to host illegal or harmful data after the Bitcoin Core v30 update lifted previous limits on OP_RETURN data storage.
The proposal, authored by Dathon Ohm and published on October 24, 2025, introduces what he calls the “Reduced Data Temporary Soft Fork.” The plan seeks to impose a one-year limit on certain types of data embedded in Bitcoin transactions, effectively reducing the risk of blockchain misuse while giving developers time to design a more permanent solution.
Under Ohm’s proposal, OP_RETURN outputs—a transaction field that allows users to store small pieces of arbitrary data—would be capped at 83 bytes, significantly reducing the capacity for embedding large datasets or files. Additionally, output scripts exceeding 34 bytes would be invalidated, and Taproot control blocks would be limited to 257 bytes.
The soft fork would also restrict undefined witness versions and disallow certain script operations that could otherwise enable complex or nonstandard data embedding. These restrictions, the proposal explains, are intended to be simple enough for rapid deployment should the community need to act swiftly in response to data abuse incidents.
The proposal includes a self-expiration mechanism, automatically deactivating after roughly one year. During this time, Bitcoin’s core developers and researchers would be expected to explore longer-term solutions that maintain Bitcoin’s permissionless nature while mitigating risks associated with storing arbitrary content.
According to the proposal, the primary motivation behind the temporary restrictions is to protect node operators from potential legal or ethical exposure. Bitcoin’s decentralized architecture requires users to run fully validating nodes that download and verify all blockchain data—including any arbitrary content that may be embedded within it.
“If the blockchain contains content that is illegal to possess or distribute, node operators are forced to choose between violating the law or shutting down their node,” the proposal warns.
Supporters of the soft fork argue that the measure is a necessary emergency safeguard following the v30 update, which inadvertently made it easier to attach large data payloads to Bitcoin transactions. Some developers have expressed concern that, without restrictions, malicious actors could exploit this feature to upload illegal materials, potentially jeopardizing the legal standing of anyone running a node.
While the intent behind the proposal appears focused on protecting participants, it has sparked significant pushback from parts of the Bitcoin community. Critics argue that any form of protocol-level data restriction could undermine Bitcoin’s core principle of neutrality, setting a dangerous precedent for future censorship.
Well-known Bitcoin advocate Jameson Lopp was among the first to voice skepticism, highlighting the difficulty of defining “illegal or universally abhorrent content” across multiple jurisdictions.
“There are a multitude of legal jurisdictions and subjective views on content; Bitcoin as a system does not recognize any of them,” Lopp commented.
Another developer expressed outright rejection, saying:
“This change is motivated by external, political, and legal factors—not by how the software itself functions.”
Critics also contend that Bitcoin should remain agnostic to data stored on its blockchain, maintaining its stance as a tool for financial freedom rather than content moderation.
In response to the backlash, Ohm clarified that the proposal is not an attempt to censor users but rather a form of “protocol maintenance.” The draft explicitly states:
“Bitcoin is money, not speech.”
Proponents argue that the soft fork does not restrict financial transactions or limit Bitcoin’s utility as a peer-to-peer cash system. Instead, it serves as a temporary safeguard designed to prevent the blockchain from being exploited in ways that could endanger the ecosystem as a whole.
They also note that the proposal’s one-year expiry ensures that it will not become a permanent constraint on Bitcoin’s capabilities unless the community agrees on a longer-term alternative.
If approved, the soft fork would activate at block height 934,864, estimated to occur around February 1, 2026, and expire automatically at block height 987,424, approximately one year later.
However, the proposal also includes a “crisis activation” clause, allowing it to be deployed reactively if illegal data is discovered on-chain before the scheduled activation. In such a case, the new rules could be triggered to immediately invalidate any block containing unlawful content.
The debate over the “Reduced Data Temporary Soft Fork” underscores the ongoing tension between Bitcoin’s decentralization ethos and the need for responsible protocol governance. While most developers agree that protecting the network from misuse is important, opinions diverge sharply on whether this should be achieved through consensus-level intervention.
As discussions continue on developer forums and GitHub, the proposal remains a test case for how Bitcoin’s community handles complex ethical and technical challenges without compromising the principles that define the world’s largest cryptocurrency.
Dan hold a master of finance from the ISEG (France) , Dan is also a Fan of cryptocurrencies and mining. Send a tip to: 0x4C6D67705aF449f0C0102D4C7C693ad4A64926e9
Get the latest Crypto & Blockchain News in your inbox.
