Executive Overview

However, BIP110 lacks broad consensus across the global Bitcoin ecosystem. Bitcoin Core, the dominant software client powering over 98% of the network’s nodes, has not adopted the proposal. Furthermore, only an estimated 1% to 2% of the network’s total hash power has signaled support for the upgrade in recent weeks.

Despite this lack of consensus, the developers and users of BIP110-enforcing clients like Bitcoin Knots are moving forward. Starting at block 961,632—estimated to be mined on or around August 8—BIP110-enforcing nodes will begin actively rejecting any blocks that do not signal support for the upgrade.

This move introduces a coordination challenge reminiscent of the historic "Blocksize Wars" of 2017. Depending on how miners, node operators, and economic actors respond, the activation deadline could trigger several distinct outcomes: the isolation and stalling of Bitcoin Knots nodes, a sudden capitulation by miners to avoid block rejection, or a permanent chain split resulting in the creation of a new "forkcoin."

This investigative report examines the origins of the BIP110 debate, analyzes the technical mechanics of the impending activation, evaluates the three primary scenarios for how this confrontation may unfold, and assesses the long-term implications for Bitcoin’s security model and market valuation.

Detailed Chronology: The Road to BIP110

[2023: Rise of Ordinals & BRC-20] ──> [Mempool Congestion & Fee Spikes] ──> [BIP110 Drafted by Knots Developers] ──> [Aug 8: Block 961,632 Activation Deadline]

The Genesis of the Data Debate

The conflict over BIP110 is rooted in the introduction of the Ordinals protocol in early 2023. By leveraging Bitcoin’s Taproot upgrade, Ordinals allowed users to inscribe arbitrary data—such as images, text, and alternative token formats—directly into the witness portion of Bitcoin transactions.

This development divided the Bitcoin community into two main philosophical camps:

  • The Utility/Permissionless Camp: Argues that any transaction that pays the prevailing market fee is valid and that Bitcoin should remain an open, censorship-resistant block space market.
  • The Purist/Conservationist Camp: Views arbitrary data inscriptions as an "exploit" or "spam" that bloats the blockchain, increases the cost of running a full node, and crowds out traditional peer-to-peer financial transactions.

Luke Dashjr, a prominent Bitcoin Core contributor and the primary maintainer of the Bitcoin Knots client, became a leading voice of the conservationist camp. Bitcoin Knots, a derivative of Bitcoin Core that includes advanced policy customization features, historically offered more aggressive spam-filtering defaults. To address what they viewed as systemic abuse of the protocol, Knots developers drafted and integrated BIP110.

The Mechanics of BIP110

BIP110 is designed as a soft fork—a backward-compatible protocol change that restricts the rules of the network. Specifically, BIP110 limits the size of OP_RETURN outputs, which are traditionally used to embed up to 80 bytes of arbitrary metadata into a transaction. By enforcing stricter limits on OP_RETURN and filtering other data carriers, BIP110 aims to make it economically and technically unfeasible to host large data payloads on the blockchain.

To activate these rules across the network, BIP110 employs a mandatory signaling window. Similar to the User-Activated Soft Forks (UASF) of Bitcoin’s past, BIP110-enforcing nodes require miners to include a specific signal in the block header (often utilizing version-bit signaling) to indicate readiness for the new rules.

The critical threshold is set for block 961,632, projected to occur on or around August 8. From this block forward, any block mined without the BIP110 signal will be treated as invalid by BIP110-enforcing nodes, regardless of the cumulative proof-of-work backing it.

Supporting Context & Metrics

To understand the stakes of the BIP110 activation, it is necessary to examine the current distribution of power across the Bitcoin network. Bitcoin’s consensus is maintained through a delicate balance of three primary groups: miners, node operators, and economic actors (exchanges, merchants, and custody providers).

Node Software Distribution

While Bitcoin is a decentralized network, the software clients that users choose to run dictate the rules they enforce. Bitcoin Core remains the overwhelming standard for the industry.

Client Software Estimated Market Share BIP110 Enforcement Status
Bitcoin Core ~98.5% Non-Enforcing (Ignores BIP110 signals/rules)
Bitcoin Knots ~1.0% – 1.5% Enforcing (Rejects non-signaling blocks after Block 961,632)
Other Clients < 0.5% Non-Enforcing

Data Source: Bitnodes.io / Alternative Node Crawlers

Miner Signaling Metrics

Miners secure the network by constructing blocks and resolving double-spend attempts. For a soft fork to activate smoothly, it typically requires a supermajority (often 90% to 95%) of hash power signaling support over a set difficulty epoch (2,016 blocks).

In the weeks leading up to the August 8 deadline, signaling for BIP110 has hovered between 1% and 2% of the global hash rate. This indicates that the vast majority of industrial mining pools have either chosen to ignore the proposal or are actively opposed to its implementation, likely due to the transaction fee revenue generated by Ordinals and other data-carrying transactions.

Market Sentiments: Fork Futures

Historically, when a chain split is threatened, speculative markets emerge to price the potential outcome. "Fork Futures" allow traders to bet on the post-split value of the competing chains.

In the case of BIP110, experimental futures contracts and social sentiment indicators suggest virtually no market demand for a BIP110-restricted chain. The lack of liquidity and bid volume for "BIP110 Coins" indicates that the economic consensus remains firmly behind the original, unrestricted Bitcoin protocol rules enforced by Bitcoin Core.

Scenario Analysis: How the Activation Will Play Out

The disparity between the low miner signaling rate and the hard enforcement deadline of Bitcoin Knots sets up a game-theoretic confrontation. There are three primary paths the network could take starting at block 961,632.

                  ┌─── [Scenario 1: No Signaling] ───> Knots Nodes Stall / Potential GPU Hard Fork
                  │
Block 961,632 ────┼─── [Scenario 2: All Miners Signal] ───> Successful Soft Fork (or Latent Split)
                  │
                  └─── [Scenario 3: Sizable Minority Signals] ───> Immediate Chain Split (Two Coins)

Scenario 1: (Almost) No Miners Signal (The Status Quo Maintained)

If current mining metrics persist, the vast majority of global hash power will continue to mine blocks without the BIP110 signal after the August 8 deadline.

Impact on the Mainstream Ecosystem

For users running Bitcoin Core, standard wallets, and major exchange interfaces, the transition will be invisible. Because Bitcoin Core does not recognize BIP110, it will continue to accept non-signaling blocks as valid. The blockchain will proceed as normal, transactions will confirm within the standard 10-minute window, and fee markets will remain unaffected.

Impact on the BIP110 / Knots Ecosystem

For users running Bitcoin Knots or other BIP110-enforcing software, the consequences will be severe. Because their nodes will reject any block lacking the BIP110 signal, and because almost no miners are producing such blocks, these nodes will effectively stop receiving updates.

  • Node Stalling: Enforcing nodes will see the blockchain "freeze" at block 961,631. No new transactions will confirm on their local ledgers.
  • Loss of Utility: Merchants or users relying solely on Knots nodes will be unable to accept payments or broadcast transactions to the wider network, rendering their node infrastructure unusable until they manually downgrade or switch to Bitcoin Core.

The Hard Fork Escape Hatch

Faced with a stalled network, BIP110 proponents would have to choose between admitting defeat (by reverting to non-BIP110 software) or executing a hard fork.

A hard fork would involve changing the proof-of-work (PoW) algorithm of the BIP110 chain—for example, switching from SHA-256 to a GPU-friendly algorithm. This would render industrial ASIC mining rigs useless on the BIP110 chain, allowing hobbyists and home miners using GPUs to mine blocks and resume transaction processing. However, this action would permanently sever the BIP110 project from the main Bitcoin network, creating an entirely new altcoin.

Scenario 2: (Almost) All Miners Signal (The Capitulation)

In this scenario, miners—fearing that even a small percentage of rejecting nodes could disrupt block validation or cause localized network instability—decide to preemptively signal support for BIP110.

The Activation Path

If a supermajority of miners signal for BIP110, all blocks mined will contain the required version bits. Consequently, both Bitcoin Core and Bitcoin Knots nodes will remain on the same chain. After a designated coordination period (typically two weeks following the signal activation), the BIP110 rules would officially go into effect across the network. By early September, transactions violating the new OP_RETURN and data limits would no longer be accepted into blocks.

The Caveat of "False Signaling"

Blockchain signaling is a coordination tool, not a guarantee of rule enforcement. Miners can easily modify their block templates to include the BIP110 signal without actually running the BIP110 software or validating its rules. They may do this simply to prevent their blocks from being rejected by Knots nodes, while continuing to include high-fee, data-heavy transactions.

[Miner Blocks] ───(Signals BIP110)───> [Bitcoin Core Node] ───> Accepts Block (Ignores OP_RETURN limits)
       │
       └─────────(Signals BIP110)───> [Bitcoin Knots Node] ───> Rejects Block if OP_RETURN limit is violated

If miners "falsely signal" and eventually mine a block containing an invalid data payload, a split will occur:

  • Bitcoin Core nodes (and non-enforcing economic nodes) will accept the block because they do not validate BIP110 rules.
  • Bitcoin Knots nodes will reject the block as invalid.

Despite the initial appearance of a successful upgrade, the network would still split into two distinct ledgers.

Scenario 3: A Sizable Minority of Miners Signal (The Split)

This scenario represents the most disruptive outcome: a split where a meaningful minority of miners (e.g., 10% to 20%) actively support and enforce BIP110, while the majority continue to mine under the original rules.

The Mechanics of the Split

If a minority of miners decide to signal BIP110 and reject all non-signaling blocks, they will begin building a separate, parallel blockchain. 

                          ┌─── [Original Chain] (80% Hashrate) ─── Normal Blocks (~12 min block times initially)
                          │
[Block 961,631] ──────────┤
                          │
                          └─── [BIP110 Chain]   (20% Hashrate) ─── Slow Blocks (~50 min block times initially)

Because the minority chain only has a fraction of the original hashrate, its block times will initially be very slow—potentially taking 50 to 100 minutes per block. It will remain in this sluggish state until the next difficulty adjustment epoch (which occurs every 2,016 blocks), at which point the mining difficulty on the BIP110 chain will adjust downward, restoring the average 10-minute block time.

Meanwhile, the majority chain running the original rules will experience a minor slowdown (e.g., block times increasing to 11 or 12 minutes) until its own difficulty adjustment occurs, after which it will return to normal operations.

The "Wipeout" Risk

A critical technical hazard in minority soft forks is the "wipeout risk." If the BIP110 chain is a strict mathematical subset of the original chain’s rules (a classic soft fork), then non-upgraded Bitcoin Core nodes will view BIP110 blocks as valid.

If, at any point in the future, the BIP110 chain accumulates more total proof-of-work (becomes "longer") than the original chain, all Bitcoin Core nodes will automatically reorg (reorganize) to the BIP110 chain. This would wipe out all transactions and block rewards generated on the original chain since the split.

To mitigate this risk, users and miners on the original chain can employ manual intervention:

  • Manual Invalidation: Node operators can use commands like invalidateblock on their Core nodes to manually reject the BIP110 chain’s blocks.
  • Hard Fork Protection: The majority chain can implement a minor hard fork to ensure their nodes never recognize the BIP110 chain, making the split permanent and removing the wipeout risk.

Official Statements and Viewpoints

The debate surrounding BIP110 reflects deep ideological divisions regarding Bitcoin’s governance and design philosophy.

Proponents: Preserving Decentralization

Supporters of BIP110, led by developers within the Bitcoin Knots ecosystem, argue that the proposal is a defensive measure necessary to protect Bitcoin’s long-term decentralization.

In public discussions, proponents emphasize that the rapid growth of the blockchain’s size (state bloat) makes it increasingly difficult for average users to run a full node on consumer-grade hardware. They view the insertion of arbitrary data into the ledger as a tragedy of the commons, where short-term speculative use cases (like image inscriptions) jeopardize the network’s censorship resistance. From their perspective, BIP110 is a legitimate exercise of node sovereignty to enforce quality control on the ledger.

Critics: A Harmful and Fracturing Attempt

Critics, including many mainstream Bitcoin Core contributors and economic actors, argue that BIP110 is both ineffective and dangerous.

They point out that trying to filter transactions based on data content is a losing battle; developers of data protocols can easily obfuscate their payloads to look like standard multisig transactions or taproot outputs, rendering simple OP_RETURN limits useless.

Furthermore, critics argue that attempting to force a consensus change without overwhelming support from the economic community is irresponsible. They warn that it risks fragmenting the network, confusing users, and introducing security vulnerabilities like replay attacks.

Future Outlook: Navigating a Chain Split

As the August 8 deadline approaches, the probability of a silent failure for BIP110 (Scenario 1) remains high due to the lack of miner and economic support. However, should a chain split occur, users and investors must navigate the practical realities of a multi-chain environment.

The Problem of Replay Attacks

BIP110 does not include native replay protection. If the chain splits, a transaction broadcast on the original Bitcoin network can be copied by third parties and replayed on the BIP110 network (and vice versa). 

[User Broadcasts Tx on Original Chain] ───> Transaction Executed (Original Chain)
                                                 │
                                                 ▼ (Copied by Network Observers)
                                        [Transaction Replayed on BIP110 Chain]

This means that if you attempt to sell or transfer your coins on one chain, you may accidentally transfer the corresponding coins on the other chain to the same recipient, resulting in unintended financial loss.

Investor and User Checklist

To protect assets during a potential split, industry experts recommend the following precautions:

  1. Prioritize Self-Custody: Ensure your private keys are held in a wallet you control, rather than on an exchange. If a split occurs, holding your own keys guarantees you will own coins on both chains.
  2. Avoid Transacting During the Fork: Refrain from sending transactions around the August 8 activation window. Wait until the network stabilizes and clear tools emerge to safely split your coins.
  3. Utilize Coin-Splitting Techniques: Once the split is established, use advanced techniques—such as mixing your UTXOs with newly mined "coinbase" coins unique to one of the chains—to ensure your transactions cannot be replayed on the opposing network.

Conclusion

The BIP110 activation represents a real-world test of Bitcoin’s decentralized governance model. It highlights a fundamental truth of the network: while developers can write code and miners can construct blocks, the ultimate authority to define what constitutes "Bitcoin" rests with the collective economic consensus of its users. Whether BIP110 succeeds in restricting blockchain data or fades into obscurity as a failed fork attempt, the outcome will provide valuable insights into how Bitcoin resolves conflicts over its scarcest resource—block space.