Blab Crypto
Michael Saylor Opposes Bitcoins BIP-110 Data-Restriction Proposal
In a recent article titled “110 Reasons BIP 110 Is a Bad Idea,” MicroStrategy’s executive chairman Michael Saylor delivers a scathing critique of Bitcoin Improvement Proposal 110 (BIP‑110). The proposal, known as the Reduced Data Temporary Soft‑fork, would introduce a one‑year consensus change that caps the size of data embedded in Bitcoin transactions. Saylor argues that such a rule would erode the network’s neutrality by imposing consensus‑level restrictions on transaction data.
BIP‑110 proposes to limit OP_RETURN outputs to 83 bytes and restrict the total payload of non‑standard transactions to 256 bytes. Transactions that create outputs before the activation of the rule would remain exempt, meaning the change would not affect existing on‑chain data. Supporters claim the proposal will reduce the amount of non‑financial data on the blockchain, thereby lowering the storage burden on full‑node operators and preventing block space from being filled with large, non‑payment payloads.
Saylor’s main objection is that the Bitcoin protocol cannot reliably determine the purpose of data embedded in a transaction. He writes that the network cannot distinguish whether a data field contains an image, a proof of authenticity, a contract, or any other future use. Consequently, he argues that miners, node operators, and the fee market should manage disputed activity without altering the base‑layer consensus rules.
In his article, Saylor concludes that “Bitcoin does not need guardians of purity. It needs guardians of neutrality.” He has previously described the consensus precedent set by BIP‑110 as “extremely dangerous” and warned that the proposal could create fork risks if adopted without broad support.
The debate over BIP‑110 has attracted attention from several key stakeholders. Adam Back, co‑founder of Blockstream and a prominent Bitcoin developer, has publicly opposed the proposal and cautioned that enforcing disputed rules without widespread miner backing could lead to a split. Back’s stance echoes Saylor’s concerns about the potential for a hard fork.
On the other side, Bitcoin developer Luke Dashjr has remained a supporter of the proposal. According to reports, Dashjr has rejected calls to withdraw BIP‑110 even as the community’s focus has shifted toward Ordinals, Runes, and other data‑heavy uses that the proposal seeks to limit.
Miner support for BIP‑110 is currently negligible. The activation mechanism requires 55 % of miners to signal support, which translates to 1,109 of the 2,016 mined blocks. As of July 12, 2026, the signaling rate was near zero, far below the threshold needed to lock in the proposed rules.
Because BIP‑110 is temporary, if the activation threshold is reached, the restrictions would automatically expire after approximately one year, at block height 987,424. The proposal’s design reflects a compromise: it would impose a short‑term limit on data‑heavy transactions while preserving the network’s long‑term neutrality.
The controversy highlights the broader governance challenges facing Bitcoin. Consensus rules are intended to be stable and predictable, and any change requires a high level of agreement among miners, developers, and node operators. The BIP‑110 debate illustrates how differing views on data usage, node resource constraints, and the role of consensus can lead to deep divisions within the community.
Saylor’s position aligns with his long‑standing view that Bitcoin’s value lies in its predictable rules rather than frequent feature changes. He has repeatedly argued that policy tools, pruning, fee pricing, and second‑layer solutions can address resource use without altering the base layer.
As the BIP‑110 discussion continues, the Bitcoin community remains divided. The proposal’s future hinges on miner signaling and the willingness of developers and node operators to accept a temporary change to the protocol. Until the activation threshold is met, BIP‑110 will remain a proposal on the table, and the network will continue to operate under its current rules.
The debate also serves as a reminder that Bitcoin’s governance model relies on consensus and that any attempt to alter the protocol must be carefully weighed against the network’s core principles of neutrality and stability.
BIP‑110 proposes to limit OP_RETURN outputs to 83 bytes and restrict the total payload of non‑standard transactions to 256 bytes. Transactions that create outputs before the activation of the rule would remain exempt, meaning the change would not affect existing on‑chain data. Supporters claim the proposal will reduce the amount of non‑financial data on the blockchain, thereby lowering the storage burden on full‑node operators and preventing block space from being filled with large, non‑payment payloads.
Saylor’s main objection is that the Bitcoin protocol cannot reliably determine the purpose of data embedded in a transaction. He writes that the network cannot distinguish whether a data field contains an image, a proof of authenticity, a contract, or any other future use. Consequently, he argues that miners, node operators, and the fee market should manage disputed activity without altering the base‑layer consensus rules.
In his article, Saylor concludes that “Bitcoin does not need guardians of purity. It needs guardians of neutrality.” He has previously described the consensus precedent set by BIP‑110 as “extremely dangerous” and warned that the proposal could create fork risks if adopted without broad support.
The debate over BIP‑110 has attracted attention from several key stakeholders. Adam Back, co‑founder of Blockstream and a prominent Bitcoin developer, has publicly opposed the proposal and cautioned that enforcing disputed rules without widespread miner backing could lead to a split. Back’s stance echoes Saylor’s concerns about the potential for a hard fork.
On the other side, Bitcoin developer Luke Dashjr has remained a supporter of the proposal. According to reports, Dashjr has rejected calls to withdraw BIP‑110 even as the community’s focus has shifted toward Ordinals, Runes, and other data‑heavy uses that the proposal seeks to limit.
Miner support for BIP‑110 is currently negligible. The activation mechanism requires 55 % of miners to signal support, which translates to 1,109 of the 2,016 mined blocks. As of July 12, 2026, the signaling rate was near zero, far below the threshold needed to lock in the proposed rules.
Because BIP‑110 is temporary, if the activation threshold is reached, the restrictions would automatically expire after approximately one year, at block height 987,424. The proposal’s design reflects a compromise: it would impose a short‑term limit on data‑heavy transactions while preserving the network’s long‑term neutrality.
The controversy highlights the broader governance challenges facing Bitcoin. Consensus rules are intended to be stable and predictable, and any change requires a high level of agreement among miners, developers, and node operators. The BIP‑110 debate illustrates how differing views on data usage, node resource constraints, and the role of consensus can lead to deep divisions within the community.
Saylor’s position aligns with his long‑standing view that Bitcoin’s value lies in its predictable rules rather than frequent feature changes. He has repeatedly argued that policy tools, pruning, fee pricing, and second‑layer solutions can address resource use without altering the base layer.
As the BIP‑110 discussion continues, the Bitcoin community remains divided. The proposal’s future hinges on miner signaling and the willingness of developers and node operators to accept a temporary change to the protocol. Until the activation threshold is met, BIP‑110 will remain a proposal on the table, and the network will continue to operate under its current rules.
The debate also serves as a reminder that Bitcoin’s governance model relies on consensus and that any attempt to alter the protocol must be carefully weighed against the network’s core principles of neutrality and stability.
