On August 9, 2025, Michael Saylor stated the obvious: Bitcoin operates as designed. The BIP-110 fork, a proposed protocol upgrade, captured 0.15% of hash power. The remaining 99.85% stayed on the main chain. The fork has mined two blocks. The main chain has mined over 1,200 in the same window. The fork is now 80 blocks behind. The ledger does not lie. It records hash power as a vote. And the vote is 99.85% against BIP-110.
This is not a story of a failed hard fork. It is a demonstration of how Bitcoin's consensus mechanism resolves disputes without a central authority. The market, through hash power, has rendered a verdict. The code permits what the math dictates. And the math is unforgiving.
Context: What BIP-110 Proposed
BIP-110 was introduced by a small group of developers as a scaling solution. It proposed increasing the block size limit to 4 MB, along with a signature aggregation scheme that claimed to reduce transaction size. The fork was intended to be activated via a user-activated soft fork (UASF) mechanism, but the developers misjudged the level of support. They forked the Bitcoin Core client, made the changes, and launched a new chain on block 840,000.
The problem? They did not secure economic backing. No major exchanges, miners, or wallet providers signaled support. The fork's developers argued that the code was sound and that the community would eventually follow. They underestimated the inertia of bitcoin's existing social contract. Based on my experience auditing the EtherDelta order matching engine, I learned that smart contract logic is only as strong as the consensus that enforces it. The same principle applies here. A fork without consensus is not a upgrade; it is a separate chain with no network effect.
Core: A Systematic Teardown of the Fork's Security
Let us run the numbers. As of August 9, the Bitcoin main chain has a hash rate of approximately 700 EH/s. The BIP-110 fork has 0.15% of that, or 1.05 EH/s. The main chain produces a block every 10 minutes on average. The fork, at its current hash rate, produces a block every 6,667 minutes — roughly 4.6 days. This is why they have only mined 2 blocks in 48 hours. The fork's difficulty adjustment is set to occur every 2,016 blocks, as per Bitcoin's design. At the current rate, the first difficulty adjustment will take 25 years to complete. The fork will not survive that long.
But the raw numbers only tell part of the story. Let us examine the cost of a 51% attack on the fork. Assume an attacker uses Antminer S19 XP with an efficiency of 21.5 J/TH. To achieve 1.05 EH/s, the attacker needs 48,837 such miners. At a cost of $2,000 per miner, the hardware cost is $97.6 million. Electricity at $0.05/kWh would cost $1,115 per hour. The attacker would need to sustain this for 2,016 blocks to cause a reorganization. That is 20,160 minutes at 10-minute blocks, or 14 days. Total electricity cost: $374,640. Hardware is reusable, so the effective cost is the electricity. That is a trivial amount for a determined adversary. The fork's economic security is nonexistent.
Now compare to the main chain. To achieve 51% of 700 EH/s, an attacker would need 350 EH/s. That requires 16.3 million S19 XP miners, costing $32.6 billion. Electricity at $0.05/kWh would cost $373,000 per hour. Sustaining for 14 days would cost $125 million. The barrier is orders of magnitude higher. The fork's security is a rounding error. The ledger does not lie, it only waits to be read. And the reading is clear: the fork is economically insecure.
Furthermore, the fork's mempool is empty. Transaction volume is zero. There are no users, no capital, no utility. The only blocks mined are from the developer's own mining pool. This is not a functional network. It is a simulation. The hash power is a vanity metric. The fork's developers can claim that the code is superior, but the code is irrelevant without consensus. The ledger records the absence of economic activity as clearly as it records the presence of hash power.
Contrarian: What the Bulls Got Right
The bull case for BIP-110 is not entirely without merit. The block size increase and signature aggregation are technically sound improvements. The code is clean. The developers have identified a real limitation in Bitcoin's current scaling approach. In a world where all chains are equal, BIP-110 would be a better chain. The contrarian angle is that the fork represents a legitimate attempt at innovation, and that the failure is not due to technical flaws but to social and economic inertia.
But this is where the structural skepticism of centralization must be applied. The bull case assumes that consensus is a matter of code quality. It is not. Consensus is a matter of incentive alignment. The main chain's hash power is not there because the code is perfect; it is there because the miners, exchanges, and users have aligned incentives to maintain the status quo. The BIP-110 fork attempted to change the rules without first changing the incentives. That is a fundamental misunderstanding of how Bitcoin's consensus works.
I have seen this pattern before. During the Curve Finance vulnerability analysis, the community celebrated TVL growth while ignoring the arithmetic precision error. The market's sentiment was bullish, but the data was bearish. Here, the sentiment is bearish for the fork, but the data is even more damning. The bulls can argue that the fork is a test of decentralization, and that even a failed fork demonstrates the permissionless nature of Bitcoin. That is true, but it is a thin reed. The fork is not a success; it is a controlled experiment that confirms the null hypothesis: consensus cannot be declared, it must be earned.
Takeaway: The Ledger Does Not Lie
The BIP-110 fork is not a hack. It is a calculation. The calculation shows that the cost of maintaining a separate chain with 0.15% hash power is infinite, because the chain will never achieve the security needed to attract users. The fork's developers can continue to mine blocks at a rate of one every 4.6 days, but they will never catch up. The difficulty adjustment will not save them; it will only make the chain more vulnerable to attack.
The lesson for the broader industry is that Bitcoin's consensus is not a political statement. It is a mathematical fact. The hash power is the vote. The ledger is the ballot box. Saylor's statement is correct: consensus must be earned. The BIP-110 fork failed to earn it. The ledger does not lie, it only waits to be read. And the reading is final.
Now, the question is: what will the fork's developers do next? They can continue to mine alone for 25 years, or they can rejoin the main chain and advocate for improvement through the proper channels. The code permits what the math dictates. And the math dictates that a fork without hash power is a ghost. The only vote that matters is the one that spends energy.