The release of Bitcoin Core v0.30 has come and gone, but the drama surrounding it has not ended. As nodes on the network update to the new version, it allows for easier relay of arbitrary data in transactions and opens up what some consider new features, while the opposing camp considers it enabling a new attack vector.
During the build-up to the launch of Bitcoin Core v0.30, we’ve seen a sizable chunk of node runners (around 21% if Coin Dance is to be believed) jump ship and opt for Bitcoin Knots instead. While their share of the network has grown, it’s nowhere near enough to enforce its filter preferences.
The battle has shifted from the mempool policy layer to the consensus layer with Bitcoin Improvement Proposal 444 (BIP-444), a proposal that has divided the Bitcoin community along philosophical lines and raised fundamental questions about what Bitcoin should be.
The stakes are high, the arguments are fierce, and the outcome could significantly impact Bitcoin’s future trajectory.
What is BIP-444?
BIP-444, titled “Reduced Data Temporary Softfork,” was published on October 24, 2025, by an anonymous developer known as Dathon Ohm. At its core, this proposal seeks to implement a temporary one-year soft fork that would dramatically restrict the amount of arbitrary, non-financial data that can be stored in Bitcoin transactions.
The proposal aims to impose strict limits on data size: OP_RETURN outputs would be capped at 83 bytes, and most other scriptPubKeys at 34 bytes. Additionally, the proposal would limit OP_PUSHDATA to 256 bytes and introduce several other technical restrictions designed to prevent large data payloads from being embedded in the blockchain.
BIP-444 is considerably stricter than just limiting OP_RETURN; it would make previously valid transactions invalid if they exceed these data limits during the temporary period. The proposal includes restrictions on Taproot control blocks, limitations on witness stacks with Taproot annexes, and prohibitions on certain script operations that have been used to embed large amounts of data on-chain.
Why Has BIP-444 Been Proposed?
Bitcoin Core v30 removed an 83-byte cap on OP_RETURN outputs, allowing much larger data payloads provided the sender pays sufficient transaction fees. While this update was intended to enhance flexibility and support complex Layer-2 systems and cross-chain proofs, it also opened the door to significantly increased data storage on the blockchain, from ASCII art to more complex meta protocols and more.
The proposal’s supporters argue that this change has created several critical risks:
Legal Liability Concerns
Supporters of BIP-444 fear legal liabilities from illegal content being uploaded to the blockchain, with particular concerns about child sexual abuse material being permanently stored. The proposal argues that if the blockchain contains content that is illegal to possess or distribute, node operators face an impossible choice between violating the law or shutting down their nodes.
The distinction made in BIP-444 is crucial: unlike financial transactions that violate sanctions (where nodes simply record that a transaction occurred), illegal data makes nodes active participants in storing and distributing the illegal content itself. This creates a fundamentally different risk profile that transaction fees cannot compensate for.
And yes, a user could embed this type of data into the Bitcoin blockchain. Yes there is a history of it being done on other chains with larger data carrier sizes, like BSV.
However, the onus is still on the miner or mining pool to lay its head on the chopping block and associate itself with accepting fees for relaying that type of information and content to the blockchain and embedding it for all nodes to store for a lifetime.
Network Decentralisation Threats
The proposal warns that if node operators must choose between violating laws or shutting down infrastructure, validation could consolidate into a small set of legally protected institutional nodes, undermining Bitcoin’s core trust assumptions. This represents what supporters view as an existential threat to Bitcoin’s security model, which depends on a distributed network of independent validators.
The concern is that the stigma and legal risks associated with running a full node could discourage ordinary users from participating in network validation. Without widespread node operation, Bitcoin would become more centralised, with validation concentrated among well-resourced entities that can navigate legal complexities.
Data Storage Abuse
The v30 update has enabled the proliferation of NFTs, memecoins, and other data-heavy experiments on Bitcoin. Protocols like Ordinals, which store NFT-like digital artifacts directly on-chain, have driven significant block space usage. While this has generated miner fee revenue, critics argue that Bitcoin’s scarce block space should be preserved primarily for financial transactions rather than arbitrary data storage.
The Technical Implementation
BIP-444 proposes a temporary soft fork with specific technical restrictions. The key changes include:
- Output Size Limits: New output scriptPubKeys would be capped at 34 bytes, with OP_RETURN outputs allowed up to 83 bytes
- Data Push Limits: OP_PUSHDATA operations with payloads larger than 256 bytes would be invalid (except for BIP16 redeemScript pushes)
- Witness Version Restrictions: Spending undefined witness versions would become invalid
- Taproot Constraints: Witness stacks with Taproot annexes would be invalid, and Taproot control blocks would be limited to 257 bytes
- Tapscript Operation Restrictions: OP_IF operations inside Tapscripts would be forbidden, effectively disabling Ordinals-style inscriptions
The proposal urges a temporary one-year soft fork, giving developers time to “refine less restrictive rules” while preserving Bitcoin’s legal neutrality. Importantly, unlike a hard fork that would split the chain, this soft fork would simply change the rules so that old nodes still accept new blocks as valid.
The temporary nature is deliberate: if no further action is taken, these restrictions would automatically expire after approximately one year (at block height 987,424). This gives the community time to develop consensus-driven alternatives without making a permanent change to the protocol.
The Community Backlash
The reaction to BIP-444 has been swift and polarising, revealing deep ideological divisions within the Bitcoin community.
Support from Bitcoin Purists
Veteran developer Luke Dashjr, known for his opposition to Ordinals, has voiced support for the proposal, noting it is “on track with no technical objections”. Supporters frame BIP-444 as an emergency response necessary to protect Bitcoin’s core monetary function and prevent legal exposure that could drive node centralisation.
On-chain analyst Checkmatey praised the proposal, calling it “a necessary stop to the spam,” arguing that preserving Bitcoin’s monetary purity could “unlock a $30–60 trillion asset class”. This perspective holds that Bitcoin’s primary value proposition is as sound money, and diluting that focus with arbitrary data storage threatens long-term adoption.
Fierce Opposition
Critics have been equally vocal in their opposition. Detractors, including Ordinals proponents and Casa co-founder Jameson Lopp, argue that restricting data storage amounts to censorship and undermines Bitcoin’s permissionless ethos.
Alex Thorn, head of research at Galaxy Digital, called the soft fork “an attack on Bitcoin” and “incredibly stupid”.
The criticism of BIP-444 stands on several key points:
- Censorship Concerns: Opponents view any restriction on what data can be included in valid transactions as a violation of Bitcoin’s neutral, permissionless design. They argue that Bitcoin should not discriminate between types of data or attempt to define what constitutes “legitimate” use.
- Ineffectiveness: Canadian cryptographer Peter Todd demonstrated the proposal’s limitations by publishing a test transaction that embedded the entire text of BIP-444 while still complying with its restrictions. This highlighted that determined actors could still embed significant data using creative encoding methods.
- Perverse Incentives: BitMEX Research warned that BIP-444 might incentivise the abuse it hopes to prevent, noting: “A bad actor who wants to conduct a double-spend attack could put CSAM on-chain to cause a re-org and succeed with their attack”. The concern is that creating taboos around certain blockchain content could weaponise it for attacks.
- Precedent Setting: Many fear that accepting content-based restrictions, even temporarily, sets a dangerous precedent. If Bitcoin developers can decide that certain types of data should be blocked, what prevents future restrictions based on political or regulatory pressure?
The Legitimacy Questions
The proposal’s anonymous author, “Dathon Ohm,” has no known Bitcoin development history, raising questions about its credibility. The GitHub account was created just days before submitting the proposal, and the developer has no established track record in the Bitcoin ecosystem.
The proposal has yet to be distributed to the Bitcoin Development Mailing List, a necessary step for gathering broader feedback and moving toward acceptance. This bypassing of formal channels has raised eyebrows among long-time Bitcoin contributors who expect significant protocol changes to follow established governance processes.
Despite these concerns, the proposal has gained significant traction on social media and forums, generating intense discussion and revealing the depth of disagreement within the community.
Potential Impact on the Bitcoin Network
The potential implications of BIP-444 are far-reaching and multifaceted:
Immediate Technical Impact
If activated, BIP-444 would immediately shut down protocols like Ordinals that depend on large data inscriptions in it’s current form. This would eliminate a revenue source for miners who have benefited from the fees generated by these transactions over the past two years. Currently, only about 6.3% of reachable nodes run v30, according to Bitnodes data, suggesting limited adoption of the very feature BIP-444 seeks to roll back.
But that doesn’t mean the deploy would be absolute; it could motivate developers who are profiting from these types of transactions to seek out a new method of embedding data, and we would return to square one despite pushing through a soft fork.
Risk of Chain Split
While soft forks are designed to avoid immediate chain splits, Dashjr describes the proposal as a User-Activated Soft Fork (UASF), meaning adoption would be driven by users, not miners. This approach echoes the 2017 SegWit activation but raises questions about what happens if there’s strong disagreement. If a significant portion of the network refuses to adopt BIP-444, it could create practical fragmentation even without a technical fork.
Long-term Philosophical Impact
Perhaps most significantly, BIP-444 forces Bitcoin to confront a fundamental question: Is Bitcoin purely a monetary network, or is it a general-purpose, censorship-resistant ledger? The real fight is about purpose.
One side wants Bitcoin focused on money, the other sees it as a censorship-resistant ledger for many uses.
This debate touches on Bitcoin’s core value propositions. If Bitcoin begins making distinctions about acceptable uses and content types, it could undermine its neutrality in ways that extend beyond this specific proposal. Conversely, if Bitcoin cannot address clear abuse cases that threaten node operation, it may face genuine existential risks from regulatory pressure or declining decentralisation.
Regulatory and Social Implications
The proposal’s emphasis on legal liability and illegal content creates complex dynamics with regulators and lawmakers. Some argue that proactively addressing these concerns demonstrates responsible stewardship and could protect Bitcoin from heavy-handed regulation. Others worry that signalling responsiveness to legal pressure invites further regulatory demands and undermines Bitcoin’s resistance to censorship.
The social stigma concern is particularly nuanced. Even if legal risks are overstated, the perception that running a Bitcoin node means hosting objectionable content could discourage participation in network validation. This psychological barrier could prove more damaging than actual legal enforcement.
Where Does Bitcoin Go From Here?
The BIP-444 debate represents more than a technical disagreement—it’s a clash of fundamental visions for Bitcoin’s future. The proposal asks the community to choose between prioritising Bitcoin’s monetary function and preserving absolute permissionlessness for all data.
Several paths forward are possible:
- Adoption of BIP-444: If the proposal gains sufficient support, it would provide a one-year breathing room to develop more nuanced solutions. This could involve technical approaches like content-addressable links to off-chain storage or refined consensus rules that better balance competing concerns.
- Rejection and Status Quo: The community might decide that the risks of content-based restrictions outweigh the benefits, choosing to maintain Bitcoin’s current permissionless approach and accept the associated challenges.
- Alternative Solutions: The debate might catalyse the development of different approaches that address the legitimate concerns around node operation and legal risk without imposing content restrictions. This could involve layer-2 solutions, enhanced privacy techniques, or social coordination around node operation best practices.
- Community Fragmentation: In a worst-case scenario, irreconcilable differences could lead to multiple Bitcoin implementations with different rule sets, fragmenting the network’s unity and potentially damaging Bitcoin’s value proposition as a unified monetary standard.
A Fork In The Road
BIP-444 continues one of Bitcoin’s most consequential debates since the block size wars. At stake is nothing less than Bitcoin’s essential character and long-term viability. The proposal forces difficult questions about the trade-offs between neutrality and practicality, permissionlessness and sustainability, ideological purity and real-world resilience.
The proposal raises concerns over Bitcoin’s future, highlighting ideological divides and the challenges of maintaining neutrality. As the Bitcoin community grapples with these issues, the outcome will reveal much about the network’s ability to navigate complex challenges while preserving its core values.
Whether BIP-444 ultimately succeeds or fails, the debate itself serves a valuable purpose: forcing Bitcoin stakeholders to articulate their vision for the network’s future in the public square and to confront the difficult trade-offs inherent in building a global, permissionless monetary system. The temporary nature of the proposal provides space for this critical conversation without forcing immediate, irreversible decisions.
