The BIP-110 Fork Is Not a Bitcoin Fork. It Is a 25-Year Wait

Two blocks. That is the entire on-chain output of BIP-110's attempt to fork Bitcoin since its launch. Not two thousand. Not two hundred. Two. And as of August 9, the fork is more than 80 blocks behind the canonical network, carrying less than 0.15 percent of total Bitcoin hash rate. Michael Saylor may have said it publicly, but the numbers had already said it privately. BIP-110 can be forked freely. The Bitcoin network is free not to follow. Almost all of it chose not to. The result is a chain that does not even have enough mining power to produce one block per day on average. Let me translate that into language the market understands: this fork has not been adopted. It has not been validated. It is a node on life support, and no difficulty adjustment can save it for roughly a quarter of a century. I have spent a decade and a half watching forks die. I have audited chain splits, tracked orphan rates, read the post-mortems of projects that thought a blockchain could be built on press releases. The BIP-110 episode is not an exception. It is the rule. Forking code is the easiest part of a cryptocurrency. Forking consensus is the hardest. The code doesn't care about your roadmap. The code doesn't care about your Telegram group. The code only responds to hash power, difficulty, and the economic reality of who is willing to lose money securing a ledger. In this case, almost nobody. Saylor's statement was brief. But the arithmetic underneath it is not. It deserves a full dissection. Because the market is full of people who will look at a fork and mistake its existence for relevance. They will see a ticker, a network, a website, and they will assume it is a contender. It is not. The data says it is a corpse. And the data was available before Saylor said a word. The first number is hash rate share. BIP-110 has about 0.15 percent of Bitcoin's total hash power. That is not a rounding error; it is a statistical absence. In proof-of-work systems, hash power is the budget for security. It pays for the cost of producing blocks, and it pays for the cost of preventing rewrites. With 0.15 percent, the fork has no meaningful defense against a reorg. Any entity with a rented GPU cluster could overwhelm the chain. Any miner from the main network could point a tiny fraction of hash power at the fork and bisect it. The chain is not secured. It is merely hosted. The second number is the block height gap. The BIP-110 fork is 80 blocks behind Bitcoin. That sounds modest until you understand how long it took to fall behind. A chain with 0.15 percent of Bitcoin's hash power does not produce blocks at Bitcoin's rate. It produces blocks at roughly 0.15 percent of Bitcoin's rate. Bitcoin targets one block every ten minutes, which is 144 blocks per day. At 0.15 percent of that network, the fork would produce roughly 0.216 blocks per day. That is one block every 4.6 days. In a month, the fork would produce about six blocks. In a year, about 78 blocks. So being 80 blocks behind after some weeks of existence is not failure. It is expected physics. It is also the reason the difficulty adjustment problem becomes absurd. Here is the third number, the one that should stop anyone from ever taking this fork seriously. Bitcoin's difficulty adjustment requires 2,016 blocks. Because the BIP-110 fork has already mined two blocks, it needs 2,015 more blocks before difficulty can adjust downward. At its current block production rate, that will take about 25 years. Let me repeat that slowly. The first difficulty adjustment on this fork is scheduled for roughly 25 years from now, if nothing changes. No funding round can wait 25 years. No developer grant can wait 25 years. No user onboarding campaign can wait 25 years. The chain's first meaningful block reward expansion—the moment mining becomes economically viable for small miners—is a quarter-century away. This is not a scaling solution. It is an archaeological artifact that hasn't been buried yet. Saylor did not need to raise his voice to make this point. He simply stated that anyone can fork Bitcoin, but without security, utility, capital, and users, the fork is meaningless. He said: “Consensus must be earned, not declared.” That sentence is not a slogan. It is a technical observation. Consensus in proof-of-work is not a social agreement typed into a README. It is the ongoing expenditure of electricity. It is the continuous settlement of blocks according to a shared rule set. It is measured by the number of nodes and miners who choose to extend one particular history. Declaring a fork is like declaring yourself the CEO of a company no one works for. It produces an org chart, not a product. But to understand why BIP-110 collapsed, you have to understand what a fork actually is. In software terms, a fork is a copy of the codebase. Anyone can copy Bitcoin Core. Anyone can modify a parameter. Anyone can add an opcode. Anyone can change the block size. The code is open source. The act of copying is trivial. The act of deployment is not trivial. Deployment requires a network. A network requires peers. Peers require a shared narrative about chain history. That narrative has to include proof of work, because proof of work is the only mechanism that makes history expensive to falsify. When a fork uses the same proof-of-work algorithm but has less hash power, it is not just smaller. It is qualitatively different. It is a calendar problem. It is a security problem. It is an incentive problem. Every block takes longer. Every transaction takes longer to confirm. Every reorg risk multiplies. The economics of mining collapse because difficulty remains at the original level, blocks are scarce, and rewards are spread across a tiny pool of participants. Miners on a low-hash fork are not miners. They are philanthropists paying for electricity to maintain a ledger nobody uses. I saw this pattern during the SegWit2x episode of 2017. The idea was to fork Bitcoin with a block size increase. The market hyped it. Exchanges listed the token. A certain class of miners signed an agreement. But when the fork date approached, the hash power did not show up. The coordinated miners who had claimed they would support the larger blocks quietly stepped back because the economics did not work. They understood that a fork without economic support is not a fork. It is a sacrifice. The same thing happened with Bitcoin Cash later. Bitcoin Cash has survived for years, but it has never approached Bitcoin's security, and its difficulty adjustment algorithm exists precisely to avoid the sort of catastrophic wait BIP-110 now faces. Bitcoin Cash learned that lesson. BIP-110 did not, or could not, avoid it. The BIP-110 fork's fatal flaw is not political. It is structural. It inherited Bitcoin's difficulty at the moment of its split. Bitcoin's difficulty is tuned to the massive global hashrate that secures the network. When a minority fork retains that difficulty but loses 99.85 percent of the total hash power, the target block interval becomes untenable. Instead of one block every ten minutes, the fork produces one block every few days. During that period, the chain cannot process real economic transactions. It cannot support layer-2 protocols. It cannot provide finality in any practically useful sense. And because it needs 2,015 blocks before its first retarget, it cannot escape that prison for decades. The difficulty adjustment formula on Bitcoin is deliberately slow. It was designed to prevent miners from gaming the timestamp rules. It requires 2,016 blocks to create a statistically meaningful sample of inter-block times. That design is excellent for Bitcoin. It is catastrophic for a minority fork. Bitcoin's patience is the fork's tombstone. Every day that passes, the main network extends further ahead. Every day, the fork's block height gap grows. Every day, the difficulty stays absurdly high relative to the hash rate available. The fork is not just behind; it is stuck in a loop where the mechanism that would save it cannot execute until long after its relevance has evaporated. Now, there is a counterargument. It is worth taking seriously, because I make my living taking counterarguments seriously. The bulls will say that BIP-110's low hash rate does not matter, because a fork can gain hash power later. They will say that the first difficulty adjustment will eventually arrive, and once it does, mining will become profitable, and the network will grow. They will say that Bitcoin itself was once a tiny network. They will say that a fork is an option, not a conclusion. They will point out that the ability to fork Bitcoin without permission is a feature. It is an escape hatch against oppressive governance, a mechanism for users and miners to coordinate a different set of rules without asking a central party for approval. They are right. They are mostly right. And that is exactly why the BIP-110 fork is not interesting. Forking is the safety valve. It is the proof that Bitcoin's consensus rules are not controlled by any single entity. The open-source ecosystem makes exit possible. That is not a bug. But the existence of an exit ramp does not mean every exit ramp is populated. A fork that cannot attract hash power, capital, or users is like a lifeboat that has no oars. It may be an option, but it is not a destination. The Bitcoin bulls who celebrate permissionless innovation are right to defend the right to fork. They are wrong to defend every fork as if it were inherently valuable. The right to speak is not the same as being worth listening to. The right to fork is not the same as building a network. Let me be more precise about what BIP-110 would need to become viable. It would need to attract enough hash power that the time between blocks becomes tolerable. It would need to reach its next difficulty adjustment. At the current rate, that is 25 years away. So it would need a massive, instantaneous, and sustained increase in hash rate. That means someone would have to pay millions of dollars in electricity costs to run mining hardware without any expectation of return. Because transactions on a 0.15 percent fork are worthless. Because the token has no liquidity. Because exchanges are not going to list a chain that produces fewer than one block a day. Because users do not wait four hours for a transaction confirmation. The capital expenditure required to bootstrap BIP-110 to the first difficulty adjustment is enormous, and the payoff is speculative at best. They built on sand; I built on skepticism. That is the sentence I have repeated since the days of ICO mania. In 2017, while the market was throwing money at white papers, I spent forty hours manually auditing the withdrawal logic of a decentralized exchange protocol. I found a reentrancy vulnerability that the founders had shipped to production. I wrote the patch in a GitHub pull request and refused the token reward they offered. I did not do it for charity. I did it because the code told the truth, and the white paper was lying. That experience taught me the only reliable way to evaluate a blockchain project: ignore the announcements and trace the incentives. For BIP-110, the incentives are catastrophic. There is no path to profitability. There is no path to security. There is only a long, slow, arithmetic decline. Some people will say that the BIP-110 fork is not about mining economics. It is about preserving a particular ideological interpretation of Bitcoin. They will say that the fork is a protest, a symbol, a statement. That may be true. But symbols do not produce blocks. Protests do not update mempools. A network that takes four days to produce a block cannot secure even a symbolic transaction, because the window for a reorganization attack is enormous. If a 0.15 percent fork ever becomes newsworthy enough to attract attention, it will also attract attackers. An attacker with a few percent of Bitcoin's hash power could reorg the fork repeatedly, erase transactions, double-spend any coin that gained value, and destroy the chain's credibility in a matter of hours. The fork would be not an island, but a target. This is the point that gets lost in the fork debate. Hash power is not just a popularity metric. It is the quantitative expression of finality. It is the answer to the question: how much work does an attacker need to reverse the ledger? If the answer is “two hundred terahashes,” the ledger is a draft spreadsheet. If the answer is “the majority of a continental power grid,” the ledger is a settlement system. BIP-110's answer is “two office chairs.” It is a tabletop exercise, not an accounting system. Let me also address the phrase “free to choose not to follow it.” Saylor used that sentence to describe Bitcoin's response to BIP-110. The network is free to choose. That is not an abstraction. In proof-of-work, a node chooses which blocks to acknowledge. A miner chooses which chain to extend. An exchange chooses which branch of transaction history to count. A user chooses which chain to hold. Bitcoin's 99.85 percent hash power remained on the original chain. That is not a single decision. It is the aggregate of millions of independent decisions made by node operators, miners, and institutions. The fact that nearly all of those decisions landed on the original network is the strongest possible evidence that BIP-110's rule change did not solve a real problem. If the problem were real, at least a few large miners would have switched. They did not. They saw the proposal, checked the code, checked the economics, and stayed. Cold logic cuts through the noise of FOMO. I have seen this happened enough times that it no longer surprises me. In 2020, during DeFi Summer, I deployed a small position in a lending protocol. When the price feed failed in a sudden liquidity crunch, I traced the oracle latency back to a flawed rounding mechanism in the smart contract. I published a technical breakdown, with transaction hashes and line numbers, long before the media arrived. The market was panicking. My report was not angry. It was concise. It traced the failure to a missing decimal guard. That calm, surgical approach is what I bring to every analysis. And it is what tells me that BIP-110 is not a rival. It is a teaching example. It shows what happens when people mistake code availability for consensus and deployment for adoption. There is another lesson here, and it is about the difficulty adjustment itself. Bitcoin's difficulty adjustment is often called one of its most beautiful design features. It is self-correcting, it is simple, and it protects the integrity of the block time. But the design assumes the network is big enough to reach a retarget in a reasonable period. It assumes a large, steady supply of hash power. When that assumption breaks, as it does in a minority fork, the same mechanism that stabilizes Bitcoin becomes an anchor that drowns the fork. A 25-year wait for a retarget is not a quirk. It is a design prediction. The code knows that minority forks will struggle, and it does nothing to help them. It does not need to. The code doesn't take sides. It lets arithmetic do the work. Saylor has been criticized for his company's Bitcoin accumulation strategy. He has been called a maximalist. He has been called a whale. I do not care about any of those labels. What matters is that his August 9 statement is technically accurate. Anyone can fork Bitcoin. The fork is meaningless without security, utility, capital, and users. These are not rhetorical categories. Security is measured in exahashes. Utility is measured in transactions per day. Capital is measured in the willingness of holders to accept settlement risk. Users are measured by the number of nodes and wallets that actively validate a chain. BIP-110 scores near zero on all four metrics. That is not an opinion. It is an observation. Let me walk through those four tests one by one, because they are useful for any future fork. Security: BIP-110 has 0.15 percent of hash power. To reorg the chain to a depth of one block, an attacker needs more hash power than the entire fork. Any solo miner on Bitcoin's network could probably do it. Utility: The fork produces a block every four or five days. No payment system can function at that rate. No exchange can provide a meaningful withdrawal experience. No smart contract platform can sequence actions. Capital: The fork's native token has negligible value, negligible liquidity, and no serious market participant has allocated treasury capital to it. Users: The fork has mined two blocks. Two blocks means essentially no user has ever transacted on the chain in any meaningful volume. By every measurable standard, it is not a network. It is a block-producing device that has been accidentally left switched on. The comparison to Bitcoin's early days is false. Early Bitcoin had a tiny hash rate, but it had no competitor at its level of design, no established network with which to compete, and no difficulty level inherited from a trillion-dollar settlement system. Bitcoin was starting from zero. BIP-110 is starting from a handicap. It has to outcompete Bitcoin while carrying Bitcoin's difficulty, with less than one fifth of one percent of Bitcoin's mining power. That is not a startup. That is a suicide mission. What should the market do with this information? For most investors, the answer is simple. Ignore the fork. Do not trade its token. Do not support its narrative. Do not mistake a bureaucratic announcement for a protocol upgrade. For the larger industry, the answer is more structural. This is a reminder that consensus is a physical process. It is not a social media consensus. It is not a GitHub discussion. It is the condition in which a plurality of economically significant actors repeatedly chooses to extend the same ledger because they believe that ledger is the most secure representation of their claims. Declarations do not create consensus. Work does. I have a personal rule. When I evaluate a contentious hard fork, I look at the first retarget. If the fork cannot reach its first retarget, it is not a project. It is a meme. If it takes longer than a year to reach a retarget, it is not a project. It is a fossil. BIP-110 is expected to take 25 years to reach its first retarget. By that time, Bitcoin may have undergone several halvings, multiple soft fork upgrades, and a complete change in its economic landscape. The BIP-110 fork will still be waiting, and it will still be irrelevant. Some will ask whether a faster difficulty adjustment algorithm would fix the problem. It would. Emergent consensus adjustment mechanisms can shorten retarget periods. But that is not the point. The point is that BIP-110 did not choose to adopt such a mechanism. It imported Bitcoin's exact difficulty rules and then expected a different outcome. That is not a technical strategy. It is a logical contradiction. If you cannot accept that a low-hash fork is doomed under your own consensus rules, you have not designed a fork. You have designed a fantasy. In my due diligence work, I often encounter teams who present a fork as a “healthy disagreement” in the community. They point to a few names, a few tweets, a few commits. They say the network is a “movement.” I ask to see the block production rate. I ask to see the number of active miners. I ask to see the exchange liquidity. The answer is usually silence. That silence is the actual due diligence. BIP-110 has spoken with two blocks. The market should hear the silence. There is, of course, a subtle irony. The ability to fork Bitcoin is what gives Bitcoin its adaptability. If no one could fork Bitcoin, the original network would become complacent. The threat of exit disciplines the core developers. It disciplines miners. It disciplines the community. In that sense, BIP-110 is doing its job even by failing. It demonstrates that the exit option exists, but it also demonstrates that exit alone is insufficient. A successful exit requires not just a door, but a destination. BIP-110 opened the door and found no floor. Saylor’s phrase “consensus must be earned, not declared” is worth engraving above every crypto whitepaper. I have been in this industry long enough to see countless projects declare consensus. They declared it in their token distribution. They declared it in their governance forum. They declared it in their transparent roadmap. And then the market checked their on-chain data, and the consensus collapsed. Declaration is cheap because it costs nothing. Earning is expensive because it requires expenditure of energy, time, and capital. The BIP-110 fork did not want to pay that cost. It wanted a shortcut. It received a lesson. The next time someone tells you that a new Bitcoin fork is a threat, ask them for the fork’s current block height. Ask them for its hash rate share. Ask them for the number of blocks mined since launch and the estimated time to its first difficulty adjustment. If the answer is “two blocks,” “0.15 percent,” and “25 years,” you have your analysis. The code doesn’t smooth over those facts. It simply waits. And in the world of proof-of-work, waiting is the most expensive thing there is. This is the lens through which all future forks should be examined. I have applied it to smart contract protocols and found business models that collapse under the lightest audit. I have applied it to oracle networks and found rounding mistakes that would eventually drain every treasury. I have applied it now to BIP-110, and the conclusion is no less clear. This fork is not a competitor. It is a probability distribution that has collapsed to zero. The only unknown is how long it will continue to produce blocks in its own mausoleum. That is the quiet truth of the BIP-110 story. Michael Saylor said it in a few sentences. The blockchain said it in two blocks. The difficulty adjustment said it in a 25-year wait. The market should listen to the arithmetic. It is the only voice that has no incentive to lie.