Two Blocks of Silence: The BIP-110 Fork That Taught Us What Consensus Means

Two blocks. That’s all the BIP-110 fork ever mined. I sat with that number for a long time, trying to understand what kind of failure could be so quiet. In a world where every testnet launch is a party, this particular chain never even got the chance to break. It simply stopped. No dramatic reorg. No 51% attack. Just a slow gasp of difficulty adjustments, a handful of miners who realized their subsidy was worthless, and then nothing. The silence was the story. And like most silences in this industry, it spoke louder than any whitepaper. For those who arrived late, let me set the stage. BIP-110 was never a name you saw in the headlines. It was a proposed improvement to Bitcoin’s consensus rules, one that a small group of developers believed was being unfairly delayed by the slow, ritualistic process of BIP discussions. So they did what dreamers always do—they forked. They copied the Bitcoin codebase, altered a handful of parameters, and declared that BIP-110 could “freely fork” from the main chain. The chain was born on a Sunday. By Tuesday, it had mined two blocks. By Wednesday, it was a corpse. No exchange listings, no mining pools, no community governance. Just a repository, a manifesto, and a ledger with exactly two entries. To understand why this happened, we have to look at what the fork actually contained. The core mechanism was indistinguishable from the Bitcoin mainnet. The same proof-of-work, the same issuance schedule, the same UTXO model. The only difference was a forced activation of a specific BIP—a rule that, in the eyes of the fork authors, should have been adopted long ago. But here’s the thing: a Bitcoin improvement proposal is not a law. It’s a social contract. When you copy the contract but break the covenant, all you have left is a document. I’ve seen this pattern before, in the ICO summer of 2017, when idealists would paste together a Solidity contract and call it a decentralized autonomous organization. The code compiled. The dream didn’t. Based on my experience auditing smart contracts and observing network upgrades, I’ve learned that code is only the beginning. The BIP-110 fork was a textbook example of what happens when we confuse technical correctness with social legitimacy. I spent a week analyzing the fork’s block headers, transaction volume, and difficulty data. The picture that emerged was stark. The fork’s hashrate peaked at a negligible fraction of Bitcoin’s, and nearly all of it came from a single miner who appeared to be running the chain as an ideological experiment. The difficulty adjustment algorithm, inherited from Bitcoin, quickly sent the target difficulty to its lowest possible value, but even that failed to attract hobbyist miners. The reason wasn’t technical. It was economic. Let me be precise. A proof-of-work chain is a sequence of memories written by energy. To write those memories, you need someone willing to burn energy in exchange for future value. In Bitcoin, miners continue to burn energy because they believe the network will retain value. That belief is anchored in liquidity, security, and community. The BIP-110 fork had none of those. Its native asset—let’s call it the BIP-110 token—had no exchange listing, no custody provider, no merchant adoption. It had only a whitepaper and a dream. And as the two blocks were mined, the token’s market cap was effectively zero. Every broken token taught me how to hold value—and this one taught me that value is not something you can force into existence with a header flag. You can’t code your way into people’s hearts. There is a subtle technical detail that often gets overlooked. The BIP-110 fork’s genesis block contained a timestamp that was exactly four minutes after the last Bitcoin block. That was a deliberate gesture, a claim of continuity. But in practice, it meant nothing. The chain didn’t inherit Bitcoin’s history, its security, or its trust. It only inherited a timestamp. When I looked at the transaction history inside those two blocks, I found something telling: the first block contained a single coinbase transaction, and the second block contained the same coinbase amount, spending to the same address. There were no transfers. No messages. No community tokens. Just two coins, sitting in a wallet that was never touched again. That is not a blockchain. That is a monument to isolation. Now, the orthodox takeaway from this story is simple: Bitcoin is so strong that any fork without massive support is doomed. That’s true, but it’s also a dangerous comfort. We’re living in an era where “forking” has become a euphemism for speculative liquidity mining programs and data-availability layers that multiply on the edge of the ecosystem. We tell ourselves that these experiments are harmless—that they’re just code, and code is open. But the BIP-110 fork shows us that even a harmless fork consumes something real: attention, hashrate, narrative, and moral energy. The blind spot is that we celebrate failed forks as tests of decentralization while ignoring the quieter failures of “successful” sidechains that survive only on subsidies. A project that pays users to stay is the same as a fork that pays miners to stay. When the subsidy ends, the silence comes. That’s why I keep coming back to the bear market as my teacher. In the silence of the bear, we heard the truth about which projects were covenants and which were just contracts waiting to be broken. Let me take this a step further. The BIP-110 fork was so obviously doomed that we might dismiss it as irrelevant. But I see it as a mirror. Look at the Layer 2 landscape, where many rollups announce dedicated data-availability layers—as if they were generating more data than a busy weekend of NFT trades. Based on my assessment of their transaction throughput, 99% of them would fit comfortably inside Bitcoin’s block space with room to spare. We are being sold infrastructure for a city that hasn’t been built yet, while the only city that actually exists—Bitcoin’s mainnet—continues to be the most secure and simple chain on Earth. The BIP-110 fork was a failed rebellion against that complexity. And its failure reminds us that innovation is not about changing the rules; it’s about building the community that upholds them. There is also a geopolitical layer that I cannot ignore, even though it feels far from those two lonely blocks. As a founder in Singapore, I watch the regulatory race between Hong Kong and my home base. Hong Kong’s recent push for virtual asset licensing is often framed as a champion of innovation. But when I read the fine print, I see a desire to divert capital flows from the city that already hosts Asia’s largest crypto derivatives market. The BIP-110 fork is, in a strange way, a parable for that rivalry. You can create a licensing regime overnight. You can fork a rulebook. But you cannot force trust. The market—like the miners—will always move toward the jurisdiction that offers not just the clearest laws, but the deepest belief system. Two blocks do not build a city. So what do we do with those two blocks? We bury them as a relic, but we listen to their lesson. Every fork, every chain, every token is a promise to a future community. If the community doesn’t exist, the code is just a corpse. The next hard-won upgrade to Bitcoin will not come from a forced activation or an empty fork. It will come when a group of people, in their slow and messy way, decide to hold a new truth together. And that truth will be written in symbols, but sealed in silence. The last two blocks will remain as headstones for a project that tried to enforce, rather than invite, consensus. My code was the covenant, not just the contract—and the BIP-110 fork never understood the difference. We build in the noise to find the signal; but sometimes the signal is silence.