The Eight-Hour Corpse
The fork produced two blocks in eight hours. Two. Not forty-eight. Not twenty-four. Two.
At block height 961,632, a set of Bitcoin nodes running BIP-110 decided they had enough. They rejected any block that did not carry an activation signal. That is the classic user-activated soft fork move: force the rule change through node-side enforcement, not miner-side consensus. Eight hours later, the new chain had mined exactly one more block. Block 961,633. The main chain, meanwhile, had already moved to 961,681. In the same window, the Bitcoin network normally produces forty-eight blocks. The fork produced two. That is a hashrate share of roughly four percent. That is not a fork. That is a stillbirth.
I have seen many chain splits. I spent 72 hours in 2017 reverse-engineering a vulnerable Solidity contract in a CTF that mimicked the DAO hack vector. I learned then that code can be perfect on paper and dead on arrival in production. BIP-110 is that lesson, applied to the largest proof-of-work network on earth. The code did what it was written to do. The network refused to carry it.
This article is not a eulogy. It is a post-mortem. And the first finding is simple: Bitcoin does not fork by code. Bitcoin forks by capital. Capital, in this system, is hashrate. And hashrate did not show up.
What BIP-110 Actually Wanted
BIP-110 was not a consensus upgrade in the usual sense. It was not trying to increase throughput, improve privacy, or fix a cryptographic bug. It was trying to restrict block space usage. It wanted to limit non-financial data writes. In plain English: it wanted to kill Ordinals inscriptions, BRC-20 token experiments, and every data-heavy use of Bitcoin's block space that is not a pure financial transaction.
This puts BIP-110 in a specific ideological bucket. The "Bitcoin as money only" camp. The maximalist wing that sees the block chain as a settlement layer, not a data availability layer. From that perspective, Ordinals are not innovation. They are rent extraction. They clog blocks, drive up fees, and turn the world's most secure ledger into a server for binary blobs, text, and metadata. The exact content does not matter. The point is that BIP-110 wanted Bitcoin to be a payment network, not a database.
The mechanism matters. BIP-110 was not activated through the standard BIP-9 miner signaling process. BIP-9 requires miners to lock in support over a difficulty retarget period, usually reaching a 95% threshold for soft forks. BIP-110 wanted a 55% signal threshold, which is already lower than Bitcoin's historical norm. But even that lower threshold was never close. In the previous difficulty cycle, only 51 of 2,016 blocks carried a BIP-110 signal. That is 2.53%. Not 55%. Not even 10%. It is a rounding error in a network with tens of thousands of nodes and a multi-million-dollar mining industry.
What BIP-110 did not get in miner support, it tried to take through node enforcement. If a node refuses to accept blocks without the signal, miners are forced to choose: adopt the signal, lose block rewards on the old chain, or ignore the nodes. The nodes were a minority, the miners ignored them. That is the whole story in one sentence. But the implications are much deeper than the headline.
The UASF Scar Tissue
Let's talk about activation history, because BIP-110 was not the first attempted forced fork. It will not be the last. In 2017, the user-activated soft fork concept was used as a weapon in the block size war. UASF was the threat that the community would force Segregated Witness activation without miner support. It was dangerous because it threatened a chain split. It worked, eventually, because enough miners and businesses backed down and supported SegWit. But the scar tissue remained.
BIP-110 took the same weapon and fired it without loading the chamber. It did not have a major exchange coalition behind it. It did not have a loud miner voice. It did not have a months-long consensus process. It had a flag day. And a flag day without a flag bearer is just a piece of code running into a wall.
In 2017, the battle was about block size. The split between Bitcoin and Bitcoin Cash was a real civil war. BCH had A-list miners, exchange listings, even a dedicated futures market. It survived as a network, even if it became a zombie. BIP-110 had none of that. It could not even produce a block per hour. If an exchange had listed the fork chain's token, that token would be dead by listing time. The listing review process would fail on every health check: no hashrate, no transactions, no community, no clear legal owner.
This is why the BIP-110 fork feels eerie. It is not a battle. It is a suicide note left on a public key. There was no hash war. There was no social media war. There was just a whimper in block time.
Hashrate Math Is a Governance Audit
Let's get technical, because the numbers are the only thing that matters.
Bitcoin's average block interval is ten minutes. Eight hours is 480 minutes. Expected blocks in eight hours: forty-eight, assuming no variance. Actual blocks on the BIP-110 chain: two. So, observed hashrate share relative to the main chain is roughly 2/48, about 4.2%. Even taking into account Poisson variance and the possibility that the fork chain's block times were not independent, 4% is far below the threshold for a chain to remain secure.
A chain with 4% of Bitcoin's hash can be reorged by the main chain at will. Any miner with a fraction of mainnet hash can spend coins on BIP-110 chain and reverse them. There is no economic security there. This is not a competing network; it is a honeypot. Anyone who sends value to that chain is donating it to whoever eventually decides to mine a longer branch.
But the more interesting number is not the hashrate math. It is the signal ratio. 51 blocks out of 2,016. That is a governance audit, not a popularity poll. In Bitcoin, miners do not "vote" in the sense of a democracy. They signal their willingness to enforce rules. A low signal does not mean disagreement; it means indifference. Most miners did not even bother to say no. They simply did not say yes. And in a system where rule changes require active enforcement, indifference is the strongest possible rejection.
I have seen this pattern before. In May 2022, as TerraUSD depegged, I did not wait for institutional reports. I shorted the UST pair via derivatives and watched the cascade take out leveraged positions. The lesson there was not that Terra was a house of cards built on hope — that was obvious. The lesson was that when leverage snaps, the silence is loud. BIP-110's eight-hour silence is the same phenomenon. The network did not debate the proposal. It just refused to spend energy on it. The fork chain's block interval is the audio recording of that refusal.
The technical failure was never a flaw in the BIP-110 code. There is no evidence of a cryptographic bug. The failure was the absence of the one resource that makes proof-of-work real: energy. BIP-110 was like a smart contract that compiles correctly but has no callers. It exists, but it has no state. It bleeds, but the liquidity stays cold.
What a Real Fork Needs
Let's compare BIP-110 to the only forks that ever mattered. Bitcoin Cash in 2017 had a clear economic base: big mining pools, major exchanges, a visible developer crew, and a vocal user base. Bitcoin SV in 2018 had a wealthy sponsor, a legal team, and a set of miners willing to fight for a larger block size. Both forks were controversial. Both produced sustained block production. Both had a market price, even if that price decayed.
BIP-110 had none of those. It was a proposal with a minority signal, an anonymous or opaque developer group, no exchange commitment, and no sustained mining pool. It was less like a fork and more like a failed smart contract deployment. In my audit experience, if a contract is deployed with no user, no liquidity, and no maintainer, it is not an asset. It is a liability.
A real fork also needs a narrative that at least a fraction of the hashrate believes in enough to spend money on. BIP-110's narrative was "block space purity." That is a noble idea for a blog post, but it is not a business model. Miners do not mine ideology. They mine the chain that pays them the most after electricity and capex. If BIP-110 wanted miners to abandon the main chain, it should have offered a clear fee upside. It offered the opposite. It threatened to delete a fee stream. No miner would ever sign up for a pay cut.
The result was an eight-hour death. Even the three-minute interval of a difficulty adjustment could not save it. The chain simply stopped growing because no one was willing to spend electricity on it. That is the ultimate market vote. Not a poll, not a tweet, not a conference panel. A block. Or, in this case, the absence of one.
The Miner Veto and Token Economics
Nowhere was BIP-110's miscalculation more visible than in token economics. This was never a neutral protocol tweak. It was a direct assault on miner revenue.
Since 2023, Ordinals-related transactions have become a meaningful part of Bitcoin's fee market. The exact percentage fluctuates. Some weeks, inscription traffic pushes fees to multi-year highs. For miners, that fee income is not noise. It is a second revenue stream beyond the subsidy. BIP-110 would shut that down. It would turn off the spigot. Of course miners did not support it. The proposal was asking the people who secure the network to vote for a pay cut.
This is the part that many technical purists miss: Bitcoin miners are not philanthropists. They are capital allocators. They rent expensive machines, negotiate power contracts, and hedge their production. They will not voluntarily destroy a fee stream to satisfy an ideological preference about block space purity. Incentives align only when the risk is priced in. BIP-110 priced the miners' risk at zero. It assumed they would follow the code because the code was "correct." In reality, miners follow the chain that pays the bills.
The token economics also illuminate why BIP-110 failed so quickly. The fork chain's "BTC" was code-identical to mainnet Bitcoin, at least initially. But a coin's value is not in its code; it is in the settlement security behind it. A chain with 4% hashrate has negligible security. The fork coin's economic value is near zero. Anyone who mistakes it for Bitcoin is making a category error. This is not a stablecoin depeg; it is a separate dead ledger.
And there is a secondary effect: BIP-110's failure is a tail-risk removal for the Ordinals ecosystem. For any BRC-20 holder, the nightmare scenario was a protocol-level ban on non-financial data. That scenario was not just defeated; it was crushed by miner indifference. The Ordinals stack can keep building. The "Bitcoin as pure money" narrative just suffered a massive technical defeat. Not because the narrative is wrong, but because the implementation path is structurally impossible without majority hashrate consent.
But do not celebrate too fast. The failure of BIP-110 should also be read as a warning. It proves that miners, not users, are the gatekeepers of Bitcoin's use cases. A group that is large enough to block changes is also large enough to facilitate them. If a future mining cartel decides that data-heavy blocks are bad for their business, they do not need a BIP. They can simply orphan non-Ordinals blocks. The same power that just protected Ordinals can later destroy it. The protection is not ideological. It is based on fee revenue. If the fee revenue disappears, the protection disappears with it.
Market Reaction: A Non-Event That Changes Everything
The market response to BIP-110's death was the least surprising part. The main chain kept producing blocks. There was no systemic Bitcoin price event. There was no ETF inflow shock. There was no Solana migration wave. The Bitcoin main chain is priced by macro liquidity, ETF flows, and global dollar policy. A two-block fork is not even a rounding error on that chart.
But the non-reaction is itself the analysis. It tells us how small BIP-110's support was. In 2017, when Bitcoin Cash forked, the market fought a real war: futures, exchange listings, hash wars, public feuds. BCH had major miners, exchanges, and voices. It survived as a network, even if it became a zombie. BIP-110 had none of that. If an exchange had listed the fork chain's token, that token would be dead by listing time.
For Ordinals and BRC-20 assets, the event is a short-term positive. The tail risk of a core-protocol ban was removed. But short-term price effects are likely to be noisy. ORDI and other inscriptions may see a relief bounce. It is also possible the market shrugs completely, because the average trader never heard of BIP-110. In a sideways market, chop does not resolve; it just moves to a new range. Do not expect a clean trend from a governance failure no one was watching.
The deeper market insight is about the miners' position. BIP-110's failure reassures anyone long the main chain: miners will defend their revenue, so the chain will not adopt destructive changes. It also raises the cost of future "block space purity" proposals. A proposal that has no miner support will be ignored. A proposal with partial miner support will create a fork war. Either way, the market should start treating miner signaling data as a first-class indicator, not a lagging curiosity. When you see signal rates below 5%, do not expect a fork. When you see signal rates above 40%, start hedging. The gap between 2.53% and 55% is not a technical threshold. It is a volatility trigger.
The Governance Deadlock: Code Is Not Law
Now we get to the uncomfortable part. BIP-110 was an attempted "code is law" intervention. It treated the protocol as something a minority can enforce by writing better code and running it. But the events of those eight hours prove the opposite: code is not law. Hashrate is law. The only thing that binds miners is the economic consequence of not mining the longest chain.
In smart contract land, code can be law because the execution environment is deterministic. A contract's logic is enforced by all nodes. No one can choose to ignore it unless they fork. But in Bitcoin, the rules are enforced by miners. A miner can choose to build on a block that violates the node's rules. If that block wins the race, the node's "law" is irrelevant. BIP-110 nodes found this out in real time. They rejected blocks; miners rejected their rejection. The signal was not a war of ideas. It was a proof-of-work referendum, and it was unanimous.
I have been making this point since my 2020 Uniswap V2 liquidity mining days. I ran liquidity positions and arbitrage bots through the DeFi summer. Flash loans were new. Vulnerabilities were everywhere. I learned to trust only code that had been stress-tested under live conditions. But even that bias has a limit. Stress-tested code does not survive if the people running the network have no incentive to run it. The Ethereum chain went through something similar with EIP-999 and the Parity wallet rescue attempt. The miners and the community refused to change the state to save stolen funds. The code of the proposal was fine. The social layer rejected it. Same pattern, different network.
BIP-110's governance path was also a violation of Bitcoin's unwritten rules. The BIP process exists to build consensus before a code change is merged. BIP-110 appears to have skipped the consensus stage and jumped straight to activation. This is the "flag day" approach: on a certain date, reject all blocks without the signal, regardless of threshold. The result was predictable. The fork chain is a monument to hubris. The deeper problem is that BIP-110's failure will not stop the ideological war. It will push it into other channels. Future attempts to stop Ordinals will likely focus on economic disincentives: miners refusing to mine high-fee data transactions, or a fee-market restructuring that makes inscriptions too expensive. That is harder to fight because it does not require a BIP. It just requires a cartel.
The Uncomfortable Role of Node Operators
There is a myth in Bitcoin that nodes are the ultimate check on miners. Nodes validate blocks; miners must serve them. If nodes refuse a rule, miners must comply or leave. BIP-110 tried to deploy that myth. But the myth has a hole: nodes are voluntary, and they are not adversarial by default. Most node operators run the latest Bitcoin Core, not an obscure BIP branch. A minority node branch can reject the majority chain, but it cannot force the majority chain to stop. It can only isolate itself.
That is exactly what happened. The BIP-110 nodes isolated themselves. They refused to validate main-chain blocks after the fork, so they fell behind. They saw a blockchain with two blocks; the rest of the world saw a blockchain with 48 blocks. The honest technical description is that BIP-110 nodes became a network fork, not a Bitcoin upgrade. They were running a different chain. The economic reality followed immediately: no miners, no transactions, no market.
If code really were law, BIP-110 would have won. The rules were written. The nodes were running. The blocks without signals were invalidated. But law without enforcement is a suggestion. The only enforcer that matters in proof-of-work is electricity spent extending a chain. BIP-110 could not find enough electricity. It had no case.
Contrarian Angle: The Real Winner Is Rent Extraction
Here is the take most commentary will miss. The BIP-110 failure is widely framed as a victory for the free market and for Ordinals. In reality, it is a victory for rent extraction. Miners now know they can block any protocol change that threatens their fee income. They also know they can impose de facto policy without a BIP, as long as they coordinate. That is not open source governance. That is veto power.
Consider the incentive alignment. Miners supported Ordinals not because they care about digital artifacts, but because inscription fees are revenue. If Ordinals fees disappear, the miner position may flip overnight. The same hashrate that protected BIP-110's target could be the hashrate that enforces a "no non-financial data" rule by simply refusing to build on blocks that contain inscriptions. No BIP. No signal. Just a quiet shift in block template policy. That is much harder to fight because there is no centralized rule to protest. The blocks would simply stop existing for data-heavy transactions. Users would adapt, and the network would become what BIP-110 wanted, without ever voting on BIP-110.
So the real lesson is not that "Bitcoin will always allow Ordinals." The real lesson is that miners are the ultimate arbiter of block space policy, and they are mercenaries. The phrase "code is law" has a corollary: only if code has miners. And miners rent their loyalty to the highest fee stream.
This creates a dangerous feedback loop. Every successful Ordinals mint sends more fees to miners. Those fees entrench miners' financial interest in allowing Ordinals. That entrenchment makes the anti-Ordinals faction weaker. But it also makes Bitcoin less like a neutral settlement layer and more like a fee-maximizing platform. The incentive is not for miners to maximize Bitcoin's utility; it is to maximize Bitcoin's fee generation. That distinction matters. It means future protocol changes will be judged by a simple question: does this increase my ticket? If it does not, it will be ignored. That is not "code is law." That is "fees are law."
And there is a second contrarian point: BIP-110's failure is not a defeat for its ideology. It is a delayed detour. The "Bitcoin as money only" story still exists. It is just temporarily bankrupt as a fork strategy. The same people who supported BIP-110 will continue to build and push for fee-market changes. They will write opinion pieces. They will create node software that filters Ordinals transactions. They will pressure exchanges to delist BRC-20 assets. The fork was the bluntest tool in their toolbox, and it broke. But the smithy is still open. Watch the mining pool block templates. If a large pool starts excluding Ordinals transactions from its template, that is BIP-110's ghost arriving through a backdoor.
Risk Matrix: The Zombie Chain and Other Traps
Let's run through the risks, because this event has potential victims even after the dust settles.
First, the fork chain itself. It is likely dead or near-dead. But a dead chain is not harmless. If exchanges list its token, naive users may buy it, thinking it is "Bitcoin 2.0." It is not. It is a token with no security. Any transfer to that chain can be rolled back by a miner with a tiny fraction of global hashrate. Do not mine it. Do not trade it. Do not send funds to it. This is the same rule I applied in 2022 when Terra's LUNA was in free fall: don't catch knives that have no floor. Liquidity is a mirror, not a floor.
Second, the BIP-110 node software might still be running. Some nodes may continue to reject non-signal blocks, but on the main chain they are irrelevant. They will simply sync to fewer blocks, or they will become useless. The risk is not to the network; it is to the operators. If someone misconfigures an RPC endpoint to the fork chain, they can lose funds. I have seen this in my own infrastructure work: a wrong chain ID, a wrong port, a wrong fork. It is the same category of operational error that cost traders money in multi-chain bridges. Check your connections. Verify the chain before you sign.
Third, the Ordinals price sector may see volatility. Some traders will interpret BIP-110's death as a bull signal for BRC-20. Others will sell the news. In a sideways market, that creates chop, not trend. If you are long-term, do nothing. If you are short-term, be ready to scalp. But do not confuse the removal of a tail risk with a fundamental shift in demand. Ordinals still face scalability, indexing, and regulatory challenges. BIP-110 is only one threat.
Fourth, regulatory risk remains. BIP-110 failed, so Ordinals assets continue to exist. For U.S. regulators, this means the "Bitcoin NFT" question remains open. The SEC has been investigating NFTs for years. Some projects have already been labeled securities. BIP-110 would have solved the problem by eliminating the asset class. Its failure means the problem stays on the regulators' desks. Do not assume that a two-block fork changes the legal landscape. It changes nothing.
Fifth, future proposals. The BIP-110 failure sets a precedent: no miner support, no fork. But it does not set a precedent of "zero anti-Ordinals action." The next attack will be economic. Watch for changes in mining pool policy, transaction relay rules, and fee market design. The risk is not a hard fork; it is a soft filter. It will be much harder to detect because the blocks will still be valid, just empty of certain transactions.
The Information Gain Nobody Is Talking About
Most coverage of BIP-110 will stop at "fork fails, miners win." But there is a deeper information signal in the 51-of-2016 signal number. That number is not random. It tells us how many independent economic actors actually wanted this change. 51 out of 2016 is roughly 2.5%. That is below the noise floor for a "proposal" in a protocol with thousands of node operators and hundreds of pools. It means BIP-110 did not fail at the miner level. It failed at the human level. No one besides a small group of operators thought it was worth the risk.
In my 2017 audit sprint, I learned that a vulnerability's severity matters less than its exploitability. A bug in a function no one calls is not a bug. A proposal with no hashrate support is not a proposal. It is a wish. The on-chain signal is the exploitability score for governance. BIP-110's score was 2.53 out of 100. It was not even a credible threat.
There is also an informational asymmetry here. The market had almost no reaction to BIP-110's failure. That means the market did not price the event, either as a risk or as an opportunity. For an options trader, that is interesting. The next time a low-signal BIP is announced, there is no volatility premium. That is an opportunity to buy cheap convexity on Ordinals-related assets or on Bitcoin itself, depending on the proposal's content. BIP-110 taught us that governance tail risk is underpriced, especially when it involves miner fee income. Incentives align only when the risk is priced in. Right now, the risk is not priced in, because the market just saw an easy failure. The next one may not be so easy.
What to Watch Next
If I were still running a live P&L and not just an observation desk, I would put the following on my dashboard:
First, mining pool block templates. Do any of the top pools start excluding OP_RETURN-or-heavy-data transactions? If yes, that is the ghost of BIP-110.
Second, the fork chain's hashrate on a hash-tracking monitor. If it stays below 1 petahash, it is dead. If it suddenly spikes, something is being staged. Don't trade it. Just watch.
Third, BRC-20 trading volume. If volume remains sticky after this news, the Ordinals ecosystem is even more resilient than thought. If volume drops, BIP-110's failure was not the catalyst; it was just a headline.
Fourth, miner comments. If a major mining pool publishes a statement about "block space purity," the ideological war is far from over. If they stay silent, they are treating this as a business event, which is the best outcome for the main chain.
Fifth, futures open interest on BTC. A governance failure of this type is usually not a macro driver. But if the next "anti-Ordinals" proposal gets more than 20% signaling, expect a spike in volatility. Do you know which options chain is the cheapest to hedge? Nobody does. That is the opportunity.
The Last Word
The BIP-110 fork produced two blocks. The main chain did not flinch. The miners did not blink. The Ordinals users did not notice. The market did not move. It was, by every measure, a null event for the Bitcoin economy. And that is exactly why it matters. It proves that Bitcoin's governance is not led by code, not led by ideology, and not led by nodes. It is led by hashrate. The code bleeds, but the liquidity stays cold.
The failure was clean. The next attack will not be. Look for the backdoor. Look for the fee cartel. Look for the quiet mining pool policy change. The fork chain is dead, but the fight over block space is not. Volatility is the only constant truth.
I will be watching. I do not need to choose a side. I only need to see the order flow. And right now, the order flow says: nothing happened. That is the most dangerous kind of nothing.