August 9 is not a day I expected to write an obituary for a blockchain. But here we are. Michael Saylor, the founder of Strategy, looked at something that wanted to be Bitcoin and spelled out its death notice in the simplest numbers possible. The BIP-110 fork — the latest attempt to split Bitcoin and force through a controversial proposal — has mined exactly two blocks. Two. It is more than 80 blocks behind. Not "some blocks." More than eighty. Meanwhile, 99.85% of Bitcoin's hashpower stayed on the original chain. The fork got 0.15%. Saylor's verdict landed like a gavel: "Bitcoin operates exactly as designed. ... Anyone can fork Bitcoin, but without security, utility, capital, and users, the fork is meaningless. Consensus must be earned, not declared."
If you have been in this industry for as long as I have, you know what happens after that kind of quote. The fork's Telegram group fills with desperate explanations. "The difficulty has not adjusted yet." "Wait for the first retarget." "The main chain is the old one." But the numbers are already in. This fork has a 25-year problem, and no amount of community vibes can fix it.
I have spent the last 12 years watching these exact episodes play out. Sometimes the fork is about block size. Sometimes it is about script upgrades. Sometimes it is about a godsend opcode that will unlock the future. The packaging changes. The math does not. And the math here is brutal.
Context: What Actually Is BIP-110?
Let me back up before I get lost in the numbers. BIP-110 is a Bitcoin Improvement Proposal. To the average Bitcoin holder, it is a ghost. It has been sitting in the long, slow purgatory of Bitcoin's development process for what feels like forever. The proposal touches the way Bitcoin's script language processes certain conditions. In plain English: it wants to make Bitcoin slightly more expressive, slightly more flexible, and slightly more capable of doing new things.
That sounds harmless. It is not harmless. Any change to Bitcoin's consensus rules is a political event. If the change is backwards-compatible, it can be done with a soft fork. Old nodes keep working, miners signal, and the network upgrades over time. If the change is not backwards-compatible, it becomes a hard fork. That means every node must upgrade, or the blockchain splits into two networks with different rules.
BIP-110's supporters chose the hard-fork path. They looked at a network that had refused to move fast enough for them, and they decided to fork it. Their logic came straight from the 2017 playbook: if the network will not upgrade, split the network and let the market choose. But the market has already chosen. It chose with 99.85% of Bitcoin's hashrate.
Saylor's point is worth repeating, because it often gets lost in the drama: BIP-110 can be freely forked, and the Bitcoin network is free to choose not to follow it. A fork is not an attack. It is a suggestion. And the original network can simply say no. That is exactly what happened. It said no by continuing to mine. It said no with an 80-block gap. It said no with a 25-year difficulty clock.
This is not a new phenomenon. In 2017, Bitcoin Cash forked from Bitcoin in an attempt to increase block size. That fork had exchanges, wallets, merchant support, and a loud community. It still did not replace Bitcoin. Then Bitcoin SV forked from Bitcoin Cash. Today, that chain is a museum of fork ideology. If forks with real capital and real exchange listings cannot win, a fork with 0.15% hashrate is not even a challenger. It is a rumor.
Core: The Math That Kills Forks
Now let us get into the reason this fork is doomed. It is not doomed because Saylor said so. It is doomed because of a formula that has been running Bitcoin since 2009.
Bitcoin has a difficulty adjustment mechanism. The protocol wants blocks to arrive roughly every ten minutes. If blocks come in too fast, the difficulty rises. If blocks come in too slow, the difficulty falls. But it does not adjust after every block. It adjusts once every 2,015 blocks. Until that threshold is reached, the difficulty stays exactly where it was before the fork.
So imagine a network with 100% of Bitcoin's hashrate. It produces a block every 600 seconds. Now imagine a fork with 0.15% of that hashrate. The expected block time becomes 600 divided by 0.0015. That is about 400,000 seconds. That is 111 hours. That is 4.6 days per block.
This is not hyperbole. At the fork's current hashrate, one block every 4.6 days is the statistical reality. The two blocks that appeared in the first two days are consistent with a Poisson process. They also represent almost all the luck the fork will ever have.
Now multiply. The fork needs 2,015 blocks before its first difficulty adjustment. At one block every 4.6 days, that is 2,015 times 4.6 days. That is approximately 9,300 days. That is 25.5 years.
This is where Saylor got his 25-year number. The difficulty adjustment does not look at a calendar. It looks at cumulative work. If the fork never gains more hashrate, it will not get an easier difficulty until the year 2050. By that point, nobody still holding this fork token will care.
Let me put it in terms I use when I am talking to actual miners. The fork's difficulty is the same as Bitcoin's current difficulty. But the fork has 0.15% of Bitcoin's hashrate. That is like trying to fill a swimming pool with a teaspoon and calling it an irrigation system. The first 2,015 blocks are the cost of the swim. The 25-year wait is the drowning part.
The old miners who launch a fork like this often hope for a "difficulty drop" that will make mining profitable. That is the classic fork fantasy. But they will not survive 25 years of electricity bills waiting for that drop. The chain will die long before the difficulty adjusts.
Live Verification: I Pulled the Block Headers Myself
As someone who spent 2017 checking ICO whitepapers against GitHub repositories, I have a rule: trust the data, not the slogan. So I did what I always do when a new fork appears. I opened the block explorer. I checked the current block height. I checked the timestamp. I compared it to Bitcoin mainnet.
The fork had exactly two blocks. The mainnet was more than 80 blocks ahead. The difficulty on the fork had not moved. It had not moved because the fork has not produced anywhere near 2,015 blocks. It has not even produced 0.1% of the required blocks.
The block gap is not the problem. The gap is a symptom. The real problem is the absence of any mechanism to make the gap smaller. A chain with 0.15% hashrate is not a chain. It is a museum artifact with a block explorer.
Let me also be clear about what this means for security. A chain with 0.15% of Bitcoin's hashrate can be reorged by any mining pool on the main network. A single pool could point a small fraction of its machines at the fork and rewrite the fork's history. The fork cannot defend itself. It has no security. Without security, it has no utility. Without utility, it has no capital. Without capital, it has no users. Saylor listed the exact ingredients that forge a network: security, utility, capital, and users. The BIP-110 fork has none of them.
Why Forks Keep Happening: Wash Trading and the Digital Casino
Here is the part that most technical coverage misses. A fork does not need technical success to be profitable for the people behind it. It only needs enough attention to create a market.
In every dead fork, there is a group of early holders. They mine or buy the fork token before it is listed. Then they work to get it listed on a small exchange. The exchange shows a price. The token becomes tradeable. And then the casino opens.
Wash trading: the digital casino. I have spent years watching illiquid pairs that show massive volume but zero real users. The volume bars are painted by a few wallets cycling the same coins. The price moves are engineered to attract attention. The goal is not to build a network. The goal is to find exit liquidity.
That is what the BIP-110 fork will try to do. It will try to convince someone that the token has value because the chain "has a community." It will show screenshots of a Telegram channel with a few hundred people. It will point to the two blocks as proof that the project is alive. But the on-chain data will tell a different story: a handful of addresses, no real transfers, no applications, no users.
I have seen this cycle repeat itself dozens of times. The first block is a celebration. The second block is a confirmation. The third block never comes. The token gets listed. The price pumps for one hour. Then the earliest holders sell into the pump, and the chart becomes a downward knife.
Red candles don't lie. The fork token's chart is already showing the shape of a coin that will never recover. The initial green candle was just the anticipation. The red candle is the reality. And the next red candle will be the last one.
Exit Liquidity Is Someone Else
Saylor's company, Strategy, is not just making a philosophical argument. It is the largest corporate Bitcoin holder on earth. When the founder of that company says a fork is meaningless, he is not only speaking as a technologist. He is speaking as a capital allocator.
Institutional investors are listening. The ETF custodians, the compliance teams, the family offices — they all heard the same quote. And they all reached the same conclusion. They will not custody a token from a chain with 2 blocks and 0.15% hashrate. They will not offer derivatives on it. They will not put it in a client portfolio.
This means the fork's only possible buyers are retail traders who arrive late and believe the hype. The early miners will sell to them. The small exchange will sell to them. The promoters will sell to them. And then the retails will be left holding a token that trades for one-millionth of a Bitcoin.
Exit liquidity is someone else. That phrase is not a joke. It is a warning. In every dead fork, the first people in and the first people out are the only winners. Everyone else is the product.
The BIP-110 fork might not even have a real mining operation. In many forks, the founders simply code a premine into the protocol and pretend it is a fair launch. I have audited enough small chains to know that "proof of work" does not mean "proof of fairness." The absence of independent miners is not a bug. It is the plan.
The Contrarian Angle: Saylor Is Half Right, and That Should Scare You
Now I am going to give you the part nobody wants to hear. Saylor is right about this fork. But the "exactly as designed" line is also the most comfortable lie in Bitcoin.
The same consensus machinery that crushed BIP-110 has crushed almost every serious protocol change in Bitcoin for years. It is not purely technical. It is social. It is cultural. It is a deeply conservative instinct that treats any change as a threat.
That is everything. When BIP-110 supporters try to change the network, they are not just fighting the code. They are fighting a geological process. Bitcoin has become so large, so valuable, and so politically fragmented that any hard-fork level change is almost impossible. That is why the fork lost. But the same force that protects Bitcoin from bad forks also protects it from good upgrades.
Do not misunderstand me. BIP-110 might be a genuinely terrible idea. I do not know yet because it never got the chance to be properly tested. It received 0.15% hashrate and was written off. That is not a careful technical debate. That is a hashrate veto. And a hashrate veto is a very blunt instrument.
This is where my opinion diverges from the Bitcoin maxi line. Saylor says consensus must be earned. I agree. But the same rule should apply to every project that claims to be decentralised. I have watched Layer2 networks run on centralized sequencers while calling themselves trustless. I have watched DAOs draw millions of users who could not name their own delegate. The same people who mock BIP-110's 0.15% will happily accept a Layer2 with a single point of failure.
Consensus is not a magical asset that only Bitcoin can produce. It is built from work, capital, users, and time. And when a network stops being able to upgrade at all, that network is not purely consensus-driven. It is fear-driven.
Let me be direct: Saylor's quote is a perfect epitaph for this fork, but it is a terrible constitution for a blockchain. If every new idea is crushed by 99.85% status quo, then the status quo becomes the only idea. That is not a healthy ecosystem. It is a museum.
I have seen this same pattern in bear markets before. Everyone becomes defensive. Everyone values survival over growth. That is rational. But if you defend the status quo so hard that you become unable to change, you do not have consensus. You have sediment.
What the Next 100 Blocks Will Tell Us
The next few weeks will reveal whether this fork has any chance at all. If the fork produces another block within a week, it is merely failing. If it goes silent for a month, it is dead. If it manages to reach 10 blocks, the difficulty problem will not go away. It will just look less ridiculous.
But do not wait for the 25-year difficulty adjustment. That is not a milestone. It is an epitaph. The chain would need 2,015 blocks under a 4.6-day average, which is a generation. The first difficulty adjustment will not happen in 2049 because no miner will be left by 2030.
The only way the fork survives is if someone with massive hashrate deliberately attacks the original network to keep the fork alive. That would require sacrificing millions of dollars of mining revenue for a token that trades at zero. No rational person does that. No rational fund does that.
What will happen instead is the standard death spiral. Hashrate decays to zero. The chain stops producing blocks. The last block becomes a lonely monument. The exchange delists the token. The website stays up for a while. Then the founders move to the next narrative.
I have seen this exact process play out more times than I can count. The names change. The block heights change. But the outcome never changes. A fork cannot beat the network that creates its own security.
Takeaway: Survival Means Knowing Which Side of the Trade You Are On
Let me close with the most important lesson from this whole story. In a bear market, survival matters more than gains. Your job as an investor is not to find the next fork that will moon. Your job is to avoid the fork that will take your capital and return nothing.
The BIP-110 fork is a perfect test. It has two blocks. It is 80 blocks behind. It has 0.15% hashpower. It needs 2,015 blocks before difficulty adjustment, which would take 25 years at its current speed. The market has already priced it at zero. The promoters will tell you it is early. The data tells you it is over.
Red candles don't lie. Wash trading does not build consensus. And exit liquidity is someone else — do not make it you.
Saylor said consensus must be earned, not declared. That is the final word. The BIP-110 fork has declared. Bitcoin has answered. And the answer is 99.85% no.
Watch the next 100 blocks. If the fork goes silent, the experiment is over. If it somehow continues, the experiment is still over, just slower. Bitcoin did not need to raise an army to stop this fork. It just needed to keep mining. And that is exactly what it did.