The attempt to forcibly alter the Bitcoin protocol through a minority-supported fork has reached a technical standstill, as the breakaway chain initiated by Bitcoin Improvement Proposal 110 (BIP-110) has failed to maintain consistent block production. Following its launch on Saturday, the BIP-110 chain managed to produce only two blocks before essentially freezing, highlighting the severe mechanical challenges faced by minority forks that lack significant hashpower support. As of Sunday morning, the breakaway chain remains stalled at block 961,633, while the primary Bitcoin network has continued to function normally, progressing to block 961,681 and beyond.
This divergence occurred at block 961,632, the predetermined point where nodes running the BIP-110 software began enforcing new consensus rules. These rules require miners to signal support for a one-year moratorium on non-financial data—such as "Inscriptions" and "Ordinals"—within the Bitcoin blockchain. Because the vast majority of the mining network did not signal this support, the BIP-110 nodes rejected the blocks produced by the main network, leading to a permanent split in the ledger. However, the lack of miner migration to the new chain has left it in a state of "chain death," where the difficulty of mining a block is far too high for the available computing power.
The Technical Mechanics of the Stall
The failure of the BIP-110 chain to produce blocks is a direct result of Bitcoin’s Difficulty Adjustment Algorithm (DAA). Bitcoin is designed to produce one block approximately every ten minutes. To maintain this cadence, the network adjusts the "difficulty" of the mathematical puzzles miners must solve every 2,016 blocks (roughly every two weeks).
When the BIP-110 fork occurred, the new chain inherited the difficulty level of the main Bitcoin network. However, while the main network retains nearly 100% of the global SHA-256 hashpower, the BIP-110 chain is supported by an estimated 2.53% or less of the network’s total computing resources. Because the difficulty remains set for a massive pool of miners but is being tackled by a tiny fraction of that pool, the time required to find a valid block has expanded from ten minutes to several hours or even days.
According to data from the BIP-110 situation monitor, the new chain would need to complete a full 2,016-block cycle before the difficulty could adjust downward to a level manageable for its small group of miners. At the current rate of production, estimates suggest it would take approximately 350 days to reach that adjustment point. In contrast, the main Bitcoin network is expected to reach its next difficulty adjustment in roughly 14 days. This "difficulty trap" effectively renders the BIP-110 chain unusable for standard transactions, as confirmations are virtually non-existent.
Understanding BIP-110: The "Spam" Debate
BIP-110 was proposed as a solution to what some community members describe as the "clogging" of the Bitcoin network. Since the rise of the Ordinals protocol in early 2023, users have been using the "witness" portion of Bitcoin transactions to store arbitrary data, including images, text, and even simple video games. Proponents of BIP-110 argue that this non-financial data consumes valuable block space, drives up transaction fees for financial users, and increases the storage requirements for node operators (UTXO set bloat).
The proposal sought to implement a temporary, one-year ban on these types of transactions. By requiring miners to signal support for this ban, the authors of BIP-110 hoped to achieve a "User-Activated Soft Fork" (UASF) similar to the successful SegWit activation in 2017. However, unlike the 2017 movement, BIP-110 failed to garner widespread consensus among major exchanges, wallet providers, or the mining industry.
Opponents of the proposal, including many prominent Bitcoin Core developers and large-scale mining pools like AntPool, argue that Bitcoin is designed to be a permissionless network. They contend that if a user pays the market-rate transaction fee, they should have the right to use the block space for any data they choose. Furthermore, critics point out that attempting to filter transactions based on content introduces a layer of censorship that contradicts Bitcoin’s fundamental value proposition as "censorship-resistant money."
Chronology of the Fork
The path to the Saturday split began several weeks ago when the BIP-110 signaling period was announced. The following timeline outlines the key events leading to the current stall:
- Late July 2024: BIP-110 software is released to the public. A small group of "sovereign" node operators begins installing the client, which includes a "mandatory signaling" deadline set for block 961,632.
- August 1–7, 2024: Market observers monitor the "signaling" bit in block headers. Data shows that only 2.53% of blocks produced by the network are signaling support for the proposal. This is far below the 55% threshold typically cited as the minimum necessary to avoid a chain split.
- August 8, 2024: Developers warn of potential "replay attacks" and fund loss if the fork proceeds without significant hashpower.
- Saturday, August 9, 2024 (Block 961,632): The fork activates. AntPool mines a block that does not signal for BIP-110. The main network accepts it. BIP-110 nodes reject it and wait for a signaling block.
- Saturday, August 9, 2024 (Post-Fork): A miner connected to the Ocean mining pool produces a block that signals for BIP-110. This creates the first block of the breakaway chain.
- Eight Hours Post-Fork: Only one additional block is found on the BIP-110 chain. The main Bitcoin network has already progressed by nearly 50 blocks in the same timeframe.
- Sunday, August 10, 2024: The BIP-110 chain remains dormant. No major exchanges have announced support for the fork coin, and its market value remains theoretical and unlisted.
Risks to Users and the Replay Attack Threat
The existence of two chains that share the same transaction format creates a significant security risk known as a "replay attack." Because the BIP-110 fork did not include mandatory replay protection, a transaction signed and broadcast on one chain is also valid on the other.
If a user attempts to sell their "BIP-110 coins" (often referred to speculatively as B110) on a decentralized platform or through a private trade, the buyer could take the signed transaction and "replay" it on the main Bitcoin network. This would result in the seller inadvertently sending their real BTC to the buyer as well.
Security researchers have urged Bitcoin holders to refrain from moving any funds or interacting with BIP-110 software until the situation is resolved. Given the current stall, the risk is somewhat mitigated by the fact that transactions on the BIP-110 chain are not being confirmed, but the danger remains if hashpower were to suddenly increase or if the chain eventually reaches a difficulty adjustment.
Miner Reactions and Pool Involvement
The role of mining pools has been central to the fork’s immediate outcome. AntPool, one of the world’s largest mining collectives, was responsible for mining the first "non-signaling" block that triggered the split for BIP-110 nodes. AntPool has remained vocal in its opposition to protocol changes that are not backed by overwhelming community consensus.
In contrast, the Ocean mining pool, which prides itself on decentralization and allowing individual miners to construct their own block templates, was the source of the first BIP-110 block. It is important to note that Ocean as an entity did not necessarily endorse the fork; rather, a specific miner using Ocean’s infrastructure chose to mine a BIP-110 compliant block.
The lack of sustained mining on the BIP-110 chain suggests that even those who support the proposal’s goals are unwilling to mine at a loss. Mining on a stalled chain is economically irrational, as the electricity costs remain high while the resulting "fork coins" have no liquid market value and the probability of finding a block is extremely low.
Broader Implications for Bitcoin Governance
The BIP-110 event serves as a modern-day case study in Bitcoin governance and the "ossification" of the protocol. It demonstrates that while anyone can propose a change and even launch a fork, the "Network Effect" of the main chain is incredibly difficult to overcome.
For a fork to succeed, it generally requires three pillars of support:
- Economic Support: Exchanges and businesses must recognize the new coin and give it value.
- Mining Support: Miners must dedicate hardware to secure the chain and process transactions.
- User Support: A significant portion of the community must run nodes to validate the new rules.
BIP-110 appears to have lacked all three to a sufficient degree. The failure of this fork may discourage future attempts at "content-based" filtering of the Bitcoin blockchain, reinforcing the idea that Bitcoin’s base layer is destined to remain a neutral, albeit expensive, data carrier.
Future Outlook
The most likely outcome for the BIP-110 chain is "chain death," a scenario where the chain simply ceases to move and is eventually abandoned by the few nodes still running the software. Without a "hard fork" to manually reset the difficulty—a move that would require even more coordination and would likely be viewed as a departure from Bitcoin’s core principles—the 350-day wait for a difficulty adjustment is an insurmountable hurdle.
For the main Bitcoin network, the event has been a non-issue. Transaction processing continues as normal, and the "Inscriptions" that BIP-110 sought to ban continue to be included in blocks. The debate over block space usage will likely continue, but the focus may shift toward Layer 2 solutions or alternative fee-market proposals rather than mandatory protocol splits.
As the gap between the main chain and the BIP-110 chain continues to grow, the "controversial fork" is rapidly transitioning from a live technical threat to a historical footnote in the ongoing evolution of the world’s largest cryptocurrency.
