Bitcoin's BIP 110 proposal, which would temporarily cap arbitrary data on the blockchain, is heading toward an early August deadline with miner support stuck below 1% and major figures like Michael Saylor and Adam Back openly opposing it. The measure appears destined to create only a small minority chain rather than reshape the Bitcoin network itself.

What Is BIP 110 and Why Does It Matter?

BIP 110, formally titled the Reduced Data Temporary Soft Fork, sits at the center of a fundamental debate about what Bitcoin block space should be used for. The proposal would tighten restrictions on how users store non-financial data on the Bitcoin blockchain for one year. Specifically, it would cap OP_RETURN (a data field within transactions) at smaller sizes, block most arbitrary data chunks above 256 bytes, and restrict certain script formats used mainly for data storage.

Bitcoin transactions can carry both money and extra data. Ordinals, inscriptions, and some token schemes use these data pathways to store images, text, and token metadata directly on the blockchain. Supporters of BIP 110 argue that tightening these pathways would keep Bitcoin focused on payments and reduce the computational burden on nodes that store and relay the entire blockchain. Critics, however, contend that the proposal improperly censors valid, fee-paying transactions and sets a dangerous precedent for consensus-based rule changes.

Why Are Bitcoin's Most Influential Figures Opposing the Change?

Two of Bitcoin's most prominent voices came out against BIP 110 in July 2026. Michael Saylor, founder of MicroStrategy, posted that "there are 110 things more dangerous to Bitcoin than spam," arguing the proposal "turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions." He emphasized that the real danger lies in the precedent it would set.

"Bitcoin respectfully says no to what you want," said Adam Back, Blockstream co-founder whose hashcash design is cited in the Bitcoin white paper.

Adam Back, Co-founder at Blockstream

Back added that if supporters of BIP 110 remain unconvinced, their recourse is to "group together and fork away," but that "bitcoin won't be joining it." This reflects a core principle of Bitcoin's design: the network resists change unless the vast majority of independent operators agree to adopt it.

Back

How Does Bitcoin's Consensus Mechanism Work?

BIP 110 does not rely on the traditional path of overwhelming miner approval. Instead, it uses a user-activated soft fork (UASF), a mechanism in which nodes enforce a rule whether or not miners agree. The threshold for this approach is set at 55% miner signaling, significantly lower than the traditional 95% requirement.

Despite this lower bar, support has been virtually nonexistent. Miner signaling has never risen above approximately 1% in any period and currently stands at zero, with no major mining pool backing the proposal. Among the nodes that store and relay the blockchain, adoption sits in the low single digits, carried almost entirely by Bitcoin Knots, an alternative implementation to the dominant Bitcoin Core software.

What Happens When the August Deadline Arrives?

The current signaling period runs from block 957,600 to 959,615, with a voluntary lock-in deadline at block 961,542 in the following period, expected in early August. Nodes running BIP 110 software would then begin rejecting any block that does not signal support, with activation projected near September.

In practice, a rule enforced by only a few percent of nodes and almost no miners does not change Bitcoin for everyone. Instead, it would split off a minority chain separate from the main Bitcoin network. This outcome underscores a fundamental truth about Bitcoin: the network's resistance to change is not written down in code but emerges from thousands of independent operators who must each opt in as a means of consensus.

Understanding the Broader Spam Debate

The underlying concern driving BIP 110 is real and worth examining. Blocks have carried more non-financial data since October 2025, and reasonable observers see this as a drift from Bitcoin as a payments system toward Bitcoin as a database. This tension reflects genuine disagreement about Bitcoin's purpose and optimal use of its limited block space.

However, Bitcoin's design philosophy prioritizes network consensus over top-down rule changes. The protocol changes only when the network agrees to run the change, and on the evidence so far, the network will not run BIP 110. The proposal illustrates how Bitcoin's decentralized governance works in practice: when a significant portion of the community opposes a change, that opposition can prevent it from becoming reality, even if the underlying technical concern has merit.

How to Understand Bitcoin's Governance in Practice

• Miner Signaling: Miners indicate support for proposed changes by signaling their preference during specific blockchain periods, but their support alone does not guarantee adoption without broader network consensus.
• Node Adoption: Individual node operators must choose to run software that enforces new rules; without sufficient node adoption, a proposed change remains a minority fork rather than a network-wide upgrade.
• Community Debate: Influential figures and developers publicly discuss the merits and risks of proposals, shaping the broader conversation about whether a change aligns with Bitcoin's core principles and long-term health.

The BIP 110 saga demonstrates that Bitcoin's governance is fundamentally different from traditional software updates or corporate decision-making. There is no central authority that can impose changes, and no voting mechanism that guarantees a majority can override a determined minority. Instead, Bitcoin relies on a form of rough consensus among thousands of independent participants, each running their own node and making their own choice about which rules to enforce.