Bitcoin Faces Fork Risk: BIP-444 Legal Warnings Cause Community Backlash

BIP-444 suggests that rejecting the fork could pose “legal or moral” risks, potentially angering the community over the perceived coercive language.

The Bitcoin (BTC) developer community is facing some unrest following the publication of Bitcoin Improvement Proposal 444 (BIP-444), a ‘reduced data’ soft fork that aims to limit certain types of on-chain data storage.

The proposal, introduced by contributor dathonohm and linked to longtime developer Luke Dashjr, has sparked debate due to language suggesting legal ramifications for rejecting the fork.

The controversial proposal

Published on October 24, 2025, BIP-444 is labeled a “temporary soft fork with reduced data.” The main purpose is to prevent people from storing large files, such as images, within Bitcoin transactions.

The authors claim this is necessary because Bitcoin Core 30 removed the 80 byte limit for OP_RETURN transactions, allowing users to store almost 4 MB of non-financial data on-chain. They claim that this could lead to illegal content being permanently added to the blockchain, putting any person operating a Bitcoin node at legal risk.

Dashjr previously described the changes to OP_RETURN transactions as “utter madness”, warning that it would open the door to spam and unwanted data. Supporters of the change argued that Bitcoin should remain neutral and report all valid transactions regardless of purpose. Now BIP-444 appears to be a counter-reaction to that liberalization, an attempt to reintroduce strict limits after the expansion of Core 30.

However, critics argue that the tone and technical implications of the proposal cross a line. In one section, the draft warns that “rejecting this soft fork may have legal or moral consequences for you, or may result in you forking into a new altcoin such as Bcash.” This is seen by many as an attempt to push through change using fear.

Another section calls for “retroactive chain reorganization” to counter “an immediate crisis” caused by alleged illegal content in Bitcoin Core 30. This means that if a block with “troublesome content” is found, the new rules can be applied to erase the block and all blocks after it, effectively rewriting part of the blockchain’s history.

You might also like:

Critics point out that the proposal admits that it will not completely stop spam. It also places strict limits on advanced smart contracts, which could interrupt the development of projects like BitVM.

Community department and technical issues

The response from public figures in the community was swift and severe. Research group BitMEX Research warned that the plan would… opposite of its intended effect.

“A bad actor looking to execute a double spend attack can cause CSAM to reorganize onchain and succeed with his attack,” they posted. “The proposal therefore provides an economic incentive for CSAM in the chain.”

Many are concerned about the technical consequences. Developer Stephan Livera highlighted a comment from a fellow expert that warned that restricting Taproot scripts and removing OP_IF could “freeze funds” or block legitimate use cases for smart contracts, such as inheritance and recovery systems.

Another developer, Nitesh, expressed a general sense of frustration: post:

“The way the BIP is worded makes it sound like the government is threatening us.”

Developer Matt Corallo summed up the concerns of many by comparing the careful approach usually taken with Bitcoin changes to the aggressive style of this proposal, simply saying: “This BIP: ‘YOLO’”.

However, proponents see the measure as a short-term solution. On-chain analyst _Checkmate defended the plan, saying: “We need a temporary soft fork to stop the spread of spam. Just give us two weeks.” Dashjr himself responded to critics by saying the proposal has “no technical objections” and aims to invalidate spam-based Taproot abuse.