All news is rigorously fact-checked and reviewed by leading blockchain experts and seasoned industry insiders.
- The Bitcoin Improvement Proposal (BIT-444) seeks to cap OP_RETURN outputs at 83 bytes and restrict other data embedding methods.
- While veteran developer Luke Dashjr supports the proposal as a temporary fix, critics warn it constitutes censorship, noting that arbitrary data has been part of Bitcoin since inception.
The Bitcoin blockchain network is all set to get a new proposal dubbed the Bitcoin Improvement Proposal 444 (BIP-444) amid a growing dispute among BTC developers, regarding the amount of arbitrary data required to be permitted on the Bitcoin blockchain. The proposal, published on Friday, follows the rollout of Bitcoin Core v30.
The release of the Bitcoin core version effectively removes the cap on data that can be added to transactions using the OP_RETURN function, provided users pay sufficient fees. Despite heated debate over the change, adoption remains limited, with only 6.3% of reachable nodes running the new version, according to Bitnodes. The proposal comes just as BTC price is showing some strength ahead of the Fed rate cuts this week, as reported by CNF.
BIP-444 aims to reverse parts of this change and impose new restrictions on arbitrary data insertion methods. Supporters argue that tighter limits are necessary to prevent the upload of illegal content, such as child sexual abuse material (CSAM), which could expose node operators to potential legal risks. The proposal noted:
“If the blockchain contains content that is illegal to possess or distribute, node operators are forced to choose between violating the law (or their conscience) or shutting down their node. This unacceptable dilemma directly undermines the incentive to validate, leading to inevitable centralization and posing an existential threat to Bitcoin’s security model.”
Bitcoin Proposal BIP-444 Seeks to Temporarily Restrict Arbitrary Data on Blockchain
The newly introduced Bitcoin Improvement Proposal 444 (BIP-444) seeks to temporarily restrict how much arbitrary data can be added to Bitcoin transactions. This makes it one of the most consequential attempts to address concerns over the network’s data usage and potential legal exposure.
Under the proposal, OP_RETURN outputs would be capped at 83 bytes, while most other scriptPubKeys would be limited to 34 bytes. Thus, it would effectively restrict outputs that embed large scripts or data blobs.
Some of the additional measures include capping the size of individual data pushes, invalidating unused or undefined script versions to prevent circumvention, limiting embedded Merkle tree sizes in Taproot outputs, and banning OP_IF inside Tapscripts—a move that would effectively disable the Ordinals inscription method.
These changes would constitute a temporary soft fork, invalidating some previously valid transactions for about a year. The proposal emphasizes that the measure is intended as a short-term intervention to “mitigate a specific crisis,” not a long-term shift in Bitcoin’s development direction.
BIP-444 was authored by a developer using the pseudonym “Dathon Ohm,” who joined GitHub and X (formerly Twitter) only days before submitting the proposal and has no prior visible history in Bitcoin development.
BTC Community Members Shared Mixed Views
Longtime Bitcoin developer Luke Dashjr, a vocal critic of Ordinals, has voiced his support for the proposal, stating on X that it is “on track with no technical objections.” “This isn’t intended to be an ideal solution, only good enough and super simple to buy time to design a long-term solution,” Dashjr wrote on X Sunday.
Critics of the proposal argue that arbitrary data storage has been part of Bitcoin since the genesis block. Thus, restricting it would amount to censorship, undermining BTC’s core principle of permissionless access. X user Leonidas, a prominent member of the Ordinals community, said in September that miners and mining pools controlling over half of BTC’s hash rate told him they would accept any consensus-valid transactions, provided the appropriate fees are paid.
