Block 961,632. That is where the fiction ended.
At that height, a subset of Bitcoin nodes running BIP-110 rules did something remarkable: they started rejecting blocks that did not carry their activation signal. No negotiation. No long community review. No miner consensus at the 55% threshold the proposal itself demanded. Just an enforced rule change, dropped on the network like a hammer on a glass table.
The fork was live. And instantly dead.
Eight hours later, the BIP-110 chain had produced exactly two blocks. Block 961,633. Then silence. Bitcoin's main chain, meanwhile, kept humming along — block 961,681 and counting. For context: in eight hours, at Bitcoin's ten-minute average block time, the network should produce roughly forty-eight blocks. The fork managed two. That is about 4% of the network's hash rate. Not a faction. Not a movement. A rounding error wearing a flag.
This was not a civil war. This was a parking ticket.
Let me skip the polite version of events. A proposal called BIP-110 tried to forcibly redefine what Bitcoin's block space is for — to prohibit so-called "non-financial data writes," which is a polite way of saying it would have strangled Ordinals inscriptions and BRC-20 tokens in their cribs. The proposal failed. It failed hard. It failed in eight hours. And the way it failed tells you more about Bitcoin's real governance than a thousand essays on decentralization ever will.
I have spent 28 years watching markets try to impose order on chaos. I have audited smart contracts for ICOs in 2017, run yield farming strategies through the 2020 DeFi summer, and shorted Luna's fragility before the death spiral. I have a standing rule: speculation ends where strategy begins. This event is a masterclass in why you must understand the difference between a technical proposal and an economic weapon.
Meet BIP-110
Let us get the mechanics straight.
BIP-110 — formally a Bitcoin Improvement Proposal — was designed to restrict what could be written into Bitcoin's block space. Its target was obvious. The Ordinals protocol had turned Bitcoin's chain into a data layer. Inscriptions. BRC-20 tokens. NFT-adjacent artifacts rendered on the most secure ledger on Earth. For a certain kind of Bitcoin maximalist — the kind who believes the chain exists for monetary settlement and nothing else — this was an abomination. Digital graffiti. Rent extraction. A vibe tax on the protocol.
Their solution was to change the rules so this data no longer had a home. No inscriptions. No BRC-20. No "non-financial data writes." A clean, blank, financial Bitcoin.
The mechanism mattered more than the goal. BIP-110's backers did not wait for the standard BIP-9 activation process — the signaling mechanism where miners vote over a difficulty period and a rule activates only at a high threshold, typically 95%. Instead, they executed a variant of a User-Activated Soft Fork (UASF). In this design, node operators unilaterally enforce a new rule at a predetermined point. Flag day. No more waiting for consensus. You reject every block that does not comply, and you dare the miners to argue.
The signal history was embarrassing before the fork even happened. BIP-110 needed 55% miner support to activate through the standard path. In the prior period, it had received 51 signals out of 2016 blocks. Let me do the math for you: that is 2.53%.
Two point five three percent.
The proposal demanded 55% and arrived with 2.53%. That is not a contested election. That is a man holding a press conference in an empty stadium. No one came. Not the miners. Not the exchanges. Not the core development community. Not the users. The only thing BIP-110 had on its side was a client, some nodes, and a willingness to force the issue.
This is where my muscle memory kicks in. In 2017, I reverse-engineered the Solidity code behind the Golem ICO contract and found an integer overflow vulnerability in the token distribution logic that could have drained 15% of the raised funds. I went through the code line by line and found the bug was not in the math — it was in the assumptions. The code assumed everyone shared the same incentive to behave. The same disease lives in BIP-110. Its implementation was not the problem. Its premise was: that a minority of nodes could override the economic reality of the network by sheer will.
The first lesson: code is law, but only when the enforcers are willing to enforce it.
The Hashrate Math Nobody Wanted to Do
Let us get brutal about the numbers.
Bitcoin's security model is a simple auction: the chain with the most accumulated proof-of-work wins. When BIP-110 activated at block height 961,632, its fork chain inherited exactly the hash rate of the miners who chose to run its rules. The result: two blocks in eight hours.
Let me be precise. The main chain produced roughly forty-eight blocks in the same window. The fork produced two. That means the fork's hash rate was somewhere in the neighborhood of 4% of the network — and possibly far less, because block production is a Poisson process and two blocks in eight hours could also mean a tiny pool got lucky, then abandoned the chain.
Either way, the conclusion is the same. A chain with 4% of the network's hash rate is not a chain. It is an orphan waiting for a grave. It would be trivial for the main chain to reorg those two blocks. It has happened to bigger forks. It will happen again.
Know the risk surface. A fork chain with negligible hash rate is exposed to:
Reorg attacks. Any miner with meaningful hash rate can rewrite the fork's short history. Fifty blocks, two blocks, one block — the work required is trivial compared to the main chain's accumulated weight.
Double spends. With no exchange liquidity and no users, there is nothing to spend today. But if some exchange made the catastrophic mistake of listing the fork token, the attack surface becomes real and juicy. The chain's security assumption is broken from birth.
Infrastructure parasites. The fork's RPC endpoints, indexes, and wallets could be configured incorrectly by unsuspecting users, leading to "Bitcoin" that is not Bitcoin. Fund segregation becomes a real operational risk for sloppy operators.
Notice that none of this depends on the code quality of BIP-110. I cannot tell you if the protocol logic was sound, because no one bothered to conduct a meaningful audit cycle before activation. And that is the point. The failure was not a bug in the software. The failure was a bug in the business model. The proposal assumed enforcement could replace consensus.
Every time you trade, you price an incentive. In Bitcoin, the incentive that matters is hashrate. BIP-110 priced it at zero and got exactly what it paid for.
This brings me to the part most commentary got wrong. The BIP-110 failure is often framed as a victory for the free market or for user sovereignty — the nodes spoke, the market rejected censorship, Ordinals lives on, and so on. That narrative is partially true and completely misleading. Let me show you what actually happened.
The Economic Veto: Miners Voted with Their Wallets
Walk through the incentive structure with me.
Bitcoin miners are not ideological crusaders. They are businesses with electricity contracts, hardware loans, and payrolls. They mine what pays. In the post-2023 world, Ordinals inscriptions and BRC-20 activity created a new and meaningful revenue stream: transaction fees. Fee spikes from inscription activity injected hundreds of millions of dollars into the miner revenue model over the cycle. For a miner running thousands of ASICs at brutal electricity costs, those fees are not "digital graffiti." They are the difference between solvency and insolvency.
Now comes BIP-110. What does it promise the miner? It promises to erase that fee revenue. It promises to reduce their income. It promises a Bitcoin with fewer paying customers. And it does all of this while demanding that the miner signal support — 55% of them, no less.
Why would any rational miner support that? They would not. They did not.
The 2.53% support signal was not a polling error. It was an economic verdict. The miners looked at the proposal, looked at their income statements, and walked away. When the fork activated anyway, the miners did not fight it. They did not mobilize a resistance campaign. They just did not show up. That is the most devastating rejection possible in proof-of-work: not a battle, but an absence. Miners exercised a veto not by attacking the fork, but by ignoring it entirely.
This is an important nuance. In 2017, the Bitcoin Cash fork had real ideological backing, real exchange support, real user communities. It was a genuine civil war that required massive coordination to resolve. In this cycle, BIP-110 was a skirmish that ended because one side had better things to do with its electricity. There was no drama because there was no economic case. The market did what markets do: priced the fork's revenue expectations at zero, and the fork complied.
I ran a $20,000 personal DeFi yield farming experiment in 2020, chasing rebalancing strategies across Compound and Uniswap V2. The single biggest lesson I took from that brutal exercise in impermanent loss was this: if the incentive structure rewards you for doing nothing, the market finds you and does nothing. BIP-110 created an incentive to mine a chain nobody valued. The rational response was to mine the chain everybody valued. Miners, being rational, chose revenue. Shocking.
Take a step further into the territory that the Ordinals crowd does not want to hear. The fact that miners protected Ordinals fees does not mean miners love Ordinals. It means miners love fees. If tomorrow a different use case generates better revenues, miners will drop Ordinals like a hot brick. This "victory" is not a permanent charter for L1 asset issuance. It is a rent payment being collected by the cheapest protector available.
Miner support is not a vote of ideology. It is a vote on whose fees pay the electricity bill.
The Governance Autopsy
Now let us talk about governance, because this is where the BIP-110 story does real damage to the people who still believe Bitcoin's governance is a clean, orderly process of technical review and community consensus.
The BIP process exists to create order. Proposals are discussed, refined, tested, and eventually adopted — or abandoned. The standard activation path for soft forks, BIP-9, requires miners to signal their support over a difficulty adjustment period, and the rule only activates once a high threshold, often 95%, is reached. BIP-110 did not go that route. It demanded 55% support in the prior period and received 2.53%. Then it activated anyway through node-rule enforcement.
That is not a process failure. That is a deliberate bypass.
Someone looked at the numbers, understood there was no chance of reaching 55%, and decided to force the issue at the network level. They bet that the weight of nodes — the BIP-110-compatible clients, the infrastructure operators who run them, the self-proclaimed defenders of "clean" Bitcoin — could pressure miners into submission. They were wrong. The nodes did exactly what the nodes were programmed to do; the miners did exactly what the economics demanded. The fork collapsed.
The governance lesson is the ugliest one in this entire story: Bitcoin's governance does not run on code review, on memes, on ideology, or even on node count. It runs on hash power. The BIP-110 failure is a proof of that proposition.
This is uncomfortable because decentralization's mythology says otherwise. We want to believe that Bitcoin is governed by its users, by node operators, by the community. BIP-110 tested that theory. A small but real set of nodes activated a rule change without miner support. The miners shrugged. The fork died. Now ask yourself: if the nodes tried this with a truly disruptive rule — say, a hard cap on block rewards, or a miner tax, or a change to the issuance schedule — would the result be different? You already know the answer.
I audited enough ICO contracts in 2017 to have a dark sense of humor about this. In the Golem contract, the integer overflow was hiding in plain sight: a token distribution function that could wrap its arithmetic and mint more tokens than intended. The line of code did not kill anyone. The assumption that no one would exploit it was the killer. BIP-110 is the same pattern. Its authors assumed that activating a rule would be enough to make it real. They forgot the variable that matters: hashrate. And hashrate has no respect for assumptions.
The Ordinals Tail Risk: Reduced, Not Removed
For the Ordinals and BRC-20 ecosystem, the BIP-110 death was a short-term blessing. The tail risk most feared by that community — a protocol-layer ban, enforced at consensus level — has now been demonstrated to be non-viable without miner support. The 2.53% signal kills the standard activation path for at least the next cycle. The two-block chain kills the UASF path. Anyone who wants to re-lobby this idea will spend the next two years fighting an uphill battle with a fresh and embarrassing data point against them.
But do not mistake a failed attack for a treaty.
The next wave of attacks will not come through a BIP. It will come through mempool policy and miner-side filtering. It is technically straightforward for a major miner or pool to announce that it will no longer include transactions carrying inscription data. It is also economically risky. A pool that filters inscriptions is voluntarily rejecting fee revenue, and in a competitive market, another pool will happily process those transactions.
And yet. If the inscription fee stream ever becomes large enough to attract regulatory attention — or if a government demands that pools censor certain content — the economics change. The BIP-110 failure did not eliminate the threat; it pushed it into a channel where you cannot vote on it. Watch the mempool rules, not just the BIPs.
The Contrarian Read: Nothing Got Decentralized
Let me give you the contrarian angle no one in either camp wants.
The BIP-110 failure was not a victory for decentralization. It was a demonstration of the opposite.
Here is the uncomfortable truth: the only actors with enough power to veto this proposal were the miners. Not the users. Not the nodes. Not the exchanges. The miners blinked, and a consensus-level change died. That is not a system where power is diffused. That is a system where hash power holds a veto over protocol evolution. It was always thus. Events like this just make it visible.
This makes my skin crawl as a trader. When I shorted Luna in the months before its collapse, I was not betting on the UST peg math alone. I was betting that the human coordination required to preserve the peg would break under stress. The same analytic lens applies here: Bitcoin's "decentralized governance" is only as safe as the coordination assumptions underneath it. The miners coordinated, passively, to kill a fork. They could coordinate, actively, to push a change through. A cartel of the top five pools can do a lot. The defense against this is the same as ever: full nodes, open software, and the ability to exit the network. But BIP-110's death by hashrate shows which side of the table actually holds the cards.
The second contrarian point is for the Ordinals crowd. Their relief is justified; their smugness is not. If the next bear market hits and inscription fees dry up, the Ordinals floor on Bitcoin will look very different. The market does not reward use cases. It rewards revenue. When revenue fades, so does the miner coalition protecting it.
The third point is for the maximalists. You lost with dignity — 2.53% of the vote, a two-block chain, and a protocol rule nobody adopted. But you lost because your proposal had no economic theory. Prohibition does not work on a global, permissionless network. You cannot ban inscriptions by fiat. If you want to make inscription activity unprofitable, you need to compete in the market, not rig the protocol. That is a humbling suggestion, and I suspect it is the one the movement will refuse.
A trader reads the same playbook everywhere. Volatility is not risk. It is information. The information here is that Bitcoin's change process is an economic engine wearing a decentralized costume. That is not a criticism. It is a survival briefing.
The Risk Catalog
Since my job is translating this into tradeable information, here are the risk markers with no sugar coating.
Fork chain token delusion. If any exchange is foolish enough to list the BIP-110 fork token, understand that you are holding a token with 4% hashrate, no users, and no economic traffic. It will trend toward zero. Avoid listing announcements like you would avoid a burning building. In my 2024 ETF arbitrage work, I learned to read the difference between real liquidity and phantom liquidity. This is phantom.
Zombie chain risk. It is possible, though unlikely, that a handful of ideological miners keep the fork chain alive at a trickle. A zombie chain is a narrative weapon, not a market. Watch the block count over the next 48 hours. If it stays at two, the corpse is buried.
Infrastructure misconfiguration. Some wallets and indexers might auto-switch to the fork chain if fed the wrong RPC endpoint. Fund segregation matters. Double-check your node configuration before sending anything.
Narrative overhang. The "pure Bitcoin" camp will not dissolve. They will return with a different proposal, or with miner-side filtering. The BIP-110 death does not end the era of anti-Ordinals sentiment; it starts a new phase of it. Do not confuse short-term price relief with a structural change.
Future forking attempts. If a future BIP with real economic backing — something that actually shifts miner revenue rather than cutting it — emerges, the same mechanism that killed BIP-110 could be used to legitimize it. There is no guardrail against a profitable proposal. That is the double-edged sword of hashrate voting.
Takeaway: Where the War Moves Next
Speculation ends where strategy begins.
Let us land the plane. From a trading perspective, the BIP-110 death is a nothing burger for BTC's price. The main chain did not blink. ETF flows and macro liquidity still drive the tape. A two-block fork is a rounding error in a trillion-dollar asset's price discovery. Do not trade the noise.
From a structural perspective, though, this event matters deeply. It defines the boundaries of what is possible in Bitcoin governance. Protocol-layer bans on L1 data issuance are off the table without miner support. The economic case for Ordinals as a fee source is now encoded into miner behavior. And the uncomfortable fact of hashrate's veto power is visible to anyone willing to look.
So what changes? The battlefield moves. Expect the next anti-inscription push to be economic, not procedural — fee market reforms, miner mempool policies, and regulatory pressure layered on top. The fight over Bitcoin's block space is not over. It is just getting smarter.
I have held through drawdowns that would break most portfolios. I have watched a 340% APY farming position dilute into dust. I have seen a $1.2 million CryptoPunks position survive a bear market because discipline beat hype. Holding through the dip requires a spine of steel, and holding a conviction in crypto requires something even harder: the willingness to audit your own thesis with the same coldness you audit a smart contract.
BIP-110's authors wrote code for a Bitcoin that does not exist. The miners responded with a two-block summary of reality. The market has already told you what it values. The only question is whether you are reading the tape or the manifesto.
Risk is the only currency that never depreciates. Watch the blocks. Watch the fees. Ignore the speeches.
