BIP 110, formally titled the Reduced Data Temporary Softfork, seeks to impose restrictions on data storage for a one-year period. The proposal would cap OP_RETURN outputs at 83 bytes and limit overall payloads to 256 bytes, though it would exempt outputs created prior to its activation. Proponents argue these measures are necessary to curb arbitrary data storage and alleviate the operational burden on node operators, particularly as inscriptions and tokens increase demand on the network.
Saylor, however, warns that using consensus rules to restrict specific transaction structures sets a dangerous precedent. In his critique, titled “110 Reasons BIP 110 Is a Bad Idea,” he contends that the protocol is ill-equipped to distinguish between the value of various data types, such as authentication records or legal contracts. He maintains that Bitcoin should remain a neutral layer, leaving decisions regarding transaction validity to market forces and fee dynamics rather than protocol-level censorship.
Support for the proposal remains stalled, with miner signaling hovering near zero—well below the 55% threshold required for activation. Despite the pushback from industry figures like Saylor and Blockstream co-founder Adam Back, developer Luke Dashjr continues to advocate for the change, citing concerns that data-heavy activity threatens Bitcoin’s primary function as peer-to-peer money. The impasse highlights a fundamental rift in the community regarding how the network should evolve and who bears the responsibility for managing its resource constraints.
Comments (0)
No comments yet. Be the first!