Minority Bitcoin Fork Collapses Quickly After Mining Only Two Blocks, Raising Questions About Censorship and Consensus
Table of Contents
You might want to know
• Could a proposal that blocks non-financial data in transactions change how Bitcoin is governed?
• What practical limits prevent a low-hashpower fork from sustaining itself against the main Bitcoin chain?
Main Topic
The recent chain split initiated by proponents of BIP-110 produced a short-lived alternative Bitcoin chain that mined only two blocks in roughly eight hours before coming to a near halt. The fork started at block 961,632, when nodes running software implementing BIP-110 began to reject blocks that did not signal support for the proposal. The competing branch was created after one miner produced a block that lacked the BIP-110 signal and was accepted by the main network but rejected by the nodes enforcing the proposal, while another miner produced the signal and continued on the minority chain. Within hours, the split branch lagged the main network by dozens of blocks, demonstrating how quickly a low-support fork can become nonviable.
The primary technical reason the minority chain stalled is the way Bitcoin handles mining difficulty. The protocol adjusts difficulty every 2,016 blocks to target an average block time of about ten minutes. When the fork formed, it inherited the existing difficulty level yet controlled only a small fraction of the network's total hashpower. Recent signaling data showed approximately 2.53% of mined blocks signaled for BIP-110—far below the 55% threshold that would have allowed activation without a split. With that low hash rate, the minority chain faces an expected time to the next difficulty adjustment measured in many months rather than the roughly two weeks the main chain requires, so its block times stretched to hours instead of minutes.
Substantively, BIP-110 is presented by supporters as an "anti-spam" measure intended to block non-financial payloads—such as images, text, and other arbitrary data—that have been embedded in transactions by services including Ordinals inscriptions. Backers argue that such usage consumes block space, contributes to higher fees, and could create legal exposure for node operators who persistently host non-financial content. Critics reject the proposal on principle, viewing it as an effort to allow miners and node operators to police transaction content and thereby weaken Bitcoin's resistance to censorship. Opponents emphasize that transaction fee-payers have a right to buy block space, and that consensus changes to limit usage set a concerning precedent for centralized control over what can be included in transactions.
After the split, prominent figures in the Bitcoin ecosystem framed the outcome as confirmation of the network's design. Michael Saylor noted that the fork demonstrated voluntary coordination: BIP-110 advocates were free to fork, and the broader network was free not to follow. He highlighted that around 99.85% of hashpower remained on the main Bitcoin chain and that the BIP-110 branch fell behind by more than 80 blocks shortly after the split. Others, such as Jameson Lopp, responded with sharper criticism, arguing that supporters of the proposal demonstrated susceptibility to misleading narratives and that some had harassed long-time contributors to Bitcoin’s development.
Another practical concern arising from the split is replay risk. Because both chains accepted the same transaction format at the moment of the split, a transaction broadcast on the minority chain could be replayed on the main chain if appropriate protections were not in place. That creates potential financial risk for users transacting on the minority chain: a sale completed on the fork could be replayed and thus produce the same effect on the main chain, effectively transferring the seller’s holdings twice. The signaling window for mandatory BIP-110 activation closed at block 963,647, a milestone the minority chain was not realistically positioned to reach given its slow block production.
From a governance and social perspective, the episode highlights how changes that would alter fundamental properties of Bitcoin—such as the nature of transaction inclusion and censorship resistance—face formidable resistance. Even proposals framed in pragmatic terms, like the desire to reduce non-financial data and potential legal exposure, must contend with a decentralized community that places a high value on neutrality and permissionless use. The split also illustrates that support in discussion forums, social media, or among a subset of miners does not directly translate into operational power unless that support manifests as sustained hashpower and broad node adoption.
Technically, the forks that lack sufficient mining support are constrained not only by difficulty retargeting but also by economic incentives. Miners are paid in block rewards and fees; they will typically follow the chain that maximizes expected returns. A chain that produces blocks infrequently due to inherited difficulty and low hashpower reduces miners’ expected revenue per unit time, making it unattractive for hashpower in the absence of assured long-term value or traceable user demand. The main Bitcoin chain, by contrast, maintained regular block cadence and broad economic activity, reinforcing miner incentives to stay with the majority chain.
In sum, the BIP-110 fork’s rapid stall demonstrates both the technical mechanics and the socio-economic dynamics that preserve Bitcoin’s continuity. Difficulty adjustment intervals, miner incentives, replay risk, and strong community norms about censorship resistance combine to make short-lived minority chains unlikely to supplant or seriously disrupt the main network unless they secure sizable and sustained backing.
Key Insights Table
| Aspect | Description |
|---|---|
| Trigger | BIP-110 nodes rejected blocks without its signal starting at block 961,632, producing a minority chain. |
| Hashpower | Approximately 2.53% of recent blocks signaled for BIP-110—insufficient for activation without a split. |
| Difficulty | The fork inherited existing difficulty and lacked enough hashpower to reach the next adjustment soon, slowing block times drastically. |
| Outcome | The minority chain mined only two blocks in about eight hours and fell dozens of blocks behind the main chain. |
| Replay risk | Transactions on the minority chain could be replayed on the main chain, exposing users to double-spend-like scenarios. |
| Governance implications | The event underscored strong community resistance to transaction censorship and the limits of changing network rules without broad support. |
Afterwards...
Looking ahead, the episode will likely be referenced in future debates about protocol changes that touch on censorship, content policy, and the role of miners and nodes in policing transactions. Proposals that seek to limit certain uses of block space face both technical constraints and social hurdles: without broad consensus and significant economic incentives, forks intended to alter core behaviors are unlikely to persist. Developers, miners, and users will continue to navigate these tensions, balancing concerns about network health and legal exposure against commitments to permissionless use and censorship resistance.
For users and service providers, the incident is a reminder to be mindful of replay protection and the economic realities of mining when interacting with split chains. For the community at large, it reinforces that meaningful protocol changes require not just technical proposals but demonstrable, widespread coordination among miners, node operators, and ecosystem participants.
