QuiverCrypto QUIVERCRYPTO SUBSCRIBE
QuiverCrypto
← Blog

BIP-110: The stalled fork and the future of Bitcoin's on-chain data debate

BIP-110's mandatory signaling period began, but the proposal faced setbacks. What does this mean for Bitcoin data policies?

05 September 2026 · 6 min read

BIP-110: The stalled fork and the future of Bitcoin's on-chain data debate

In the early hours of August 9, 2026, Bitcoin reached block height 961,632, marking the initiation of the mandatory signaling period for BIP-110, a proposed consensus upgrade aimed at changing how Bitcoin handles institutional-bear-market-and-its-impact-on-transfers-highlights-reliance-on-interest-income/">liquidity/">on-chain data. However, the new proposal faced immediate hurdles, producing just two blocks before stalling.

As the protocol upgrade began, nodes enforcing BIP-110's rules began rejecting blocks that did not signal version bit 4, consequently splitting from the main chain. In stark contrast, the Bitcoin main chain proceeded normally, producing blocks unaffected by the BIP-110 changes.

Understanding BIP-110's objectives and challenges

BIP-110, formally known as "Reduced Data Temporary Softfork," was introduced by the pseudonymous developer Dathon Ohm, with contributions from Luke Dashjr on an earlier draft. The BIP proposes a series of seven consensus restrictions meant to last about a year. Highlights of these restrictions include:

  • Limiting standard new output scripts to 34 bytes.
  • Restricting new output scriptPubKeys whose first opcode is OP_RETURN to 83 bytes.
  • Capping various data pushes and witness stack elements at 256 bytes.
  • Limiting particular Taproot functionalities.

Despite these restrictions, BIP-110 does not aim to eliminate on-chain data completely. It acknowledges the potential for data to be split into smaller pieces or disguised but seeks to complicate the inscription of large amounts of contiguous data, particularly targeting Ordinals inscriptions.

One of the key issues under discussion is whether user-activated soft forks (UAFs) should dictate Bitcoin’s consensus rules. The proposal argues for stricter rules, claiming that existing standards are being exploited in ways that raise costs for ordinary transactions.

The road leading to BIP-110's signaling period

The turmoil surrounding BIP-110 began gaining momentum after the release of Bitcoin Core 30.0 in October 2025, which increased the default -datacarriersize from 83 bytes to 100,000 bytes, significantly easing the OP_RETURN relay limit. This change allowed for a greater volume of non-financial data to compete with payment transactions.

Interestingly, only 51 blocks signaled support for BIP-110's changes during the recent difficulty adjustment period. This represented merely 2.53% of the total blocks, far lower than the proposed 55% threshold necessary for voluntary early lock-in. Consequently, without strong miner support, BIP-110 has existed as a minority chain with severely limited hash power, developing no significant foothold in the Bitcoin network.

The timeline events leading up to the BIP-110 signaling phase paint a clear picture of a fractured community:

  • October 10, 2025: Bitcoin Core 30.0 was released, altering OP_RETURN policies.
  • March 1, 2026: Barefoot Mining mined the first block in support of BIP-110.
  • April 2026: Dathon Ohm announced project updates and submitted pull requests.
  • August 9, 2026: The mandatory signaling period commenced with Bitcoin at block height 961,632.

Current issues and future implications

Observers have noted that the conflict surrounding BIP-110 does not appear to stem strictly from its structural form but rather from a broader philosophical debate about Bitcoin’s governance and the principles of decentralization. Key figures like Michael Saylor have articulated concerns that altering consensus rules based on temporary controversies could weaken Bitcoin's foundational freedoms.

Saylor's stance emphasizes that the market should dictate the value of data usage without enforced restrictions, advocating for decentralized decision-making rather than centralized controls dictated by miners. On the other hand, proponents of BIP-110 argue for user rights to define acceptable operational rules and state that the prevailing scenario is stifling growth due to excessive non-financial data filling the blockchain.

These diverging viewpoints highlight an emerging conflict where one side seeks to impose restrictions to streamline Bitcoin's primary purpose as a financial asset, while the other insists on maintaining open access to all forms of data, regardless of their intent.

Real-world implications: Replay attacks and governance disputes

As the failed BIP-110 activation highlights its present challenges, the implications for ordinary Bitcoin holders could be far-reaching. There is a notable risk associated with replay attacks, as identified by Bitcoin developer Kevin Loaec and hardware wallet maker Ledger. Transactions that are valid on both the main and minority chains may inadvertently lead to unintended consequences, such as a user transferring forks coins while affecting their original Bitcoin holdings.

The growing governance disputes surrounding BIP-110 have birthed criticisms among key contributors, with reactions to Luke Dashjr’s editorial decisions triggering discussions about requirements for proposal approvals. Such internal conflicts may set a precedent for future governance approaches, and it remains to be seen how subsequent proposals will be handled in light of these tensions.

Ultimately, the fate of BIP-110 serves as a reminder that Bitcoin, while operating under a decentralized framework, remains subject to complex politics and dynamic economic interests. Its unsuccessful launch may inhibit forward motion for proposals seeking to amend consensus rules without a broader base of miner coordination.

Looking ahead: Potential paths for Bitcoin's data governance

The failed BIP-110 initiative indicates that future attempts to create a consensus upgrade will require more than just signaling support from a minority of nodes. Broader participation among miners, exchanges, users and custodians will be necessary to create a working protocol embraced by the whole network.

Moreover, the ongoing debate will likely shift focus toward solutions that pivot on policy adjustments regarding node relay capacities or smaller technical amendments rather than sweeping consensus changes. Proponents of more open data policies—such as Leonidas' DOG Mode—may play a pivotal role in steering Bitcoin's trajectory as opposing factions continue to negotiate their visions for the network.

Despite the immediate setbacks of BIP-110, the discussions sparked by its proposals will continue to resonate through the Bitcoin community, pushing towards different avenues for managing on-chain data in ways that balance the need for transaction efficiency with the desire for open-access innovation.

As discussions evolve, all participants should remain vigilant to protect their holdings and navigate the uncharted territory of Bitcoin’s future governance. With a clearer view of potential challenges and opportunities, users can prepare themselves for an uncertain but promising future in the world of cryptocurrency.

This article is intended for informational purposes only. It does not constitute investment, trading, or technical advice. Readers should exercise due diligence and assess risk when handling assets on forks or modified chains.