The number is the whole story: 2.6 percent. In early August, Michael Saylor — the most prominent corporate holder of bitcoin on earth — stood before the market and confirmed what the hashrate had already whispered. BIP-110, the temporary soft fork proposal crafted to throttle Ordinals-style data embedded in Bitcoin's block space, has not attracted miner support. It will stall, he said. It will become irrelevant. The timing is precise. The proposal's own mechanics reference block height 961,632, a checkpoint at which enforcing nodes would begin rejecting blocks carrying no activation signal. That height is roughly a month away. The proposal is already a corpse. As someone who spent his evenings in 2017 auditing ICO crowdsale contracts line by line — and once found a reentrancy bug that would have drained two million dollars from a project's withdrawal logic — I found the number less surprising than the method of death. Not a dramatic rejection. Not a contentious philosophical war. A quiet, economic shrug. Tracing the static in the protocol's genesis block reveals that Bitcoin does not kill bad ideas with noise. It starves them.
To understand what died, you must understand what never quite lived. The BIP-110 designation is itself a problem. In the official repository, BIP-110 is a relic of the 2015-2016 era, a proposal that lived in the shadow of SegWit's activation drama. The inscription-limiting soft fork that markets have been debating since early 2025 — a roughly twelve-month sunset measure imposing seven consensus constraints on non-payment data — does not cleanly map to that number. The discrepancy is telling. Either the community has circulated an informal label that never passed through the BIP editors' review, or a redefinition exists that no one has properly documented. Every bug is a story the system tried to hide, and the murky numbering of this proposal is the first bug in its narrative. In my experience, a protocol change that cannot keep its own identifier straight has not matured into a serious proposal. It is a placeholder wearing a costume.
The debate itself is older than the label. Since the first inscription wave in 2023, Bitcoin's block space has hosted two competing identities: a settlement layer for monetary value, and a permanent, permissionless storage medium for arbitrary data. The purists argue that data-carrying transactions bloat nodes, distort the fee market, and dilute the network's monetary clarity. The pragmatists respond that if someone is willing to pay for the bytes, the market has spoken. BIP-110 was the purists' formal answer: compress the ceiling on non-payment data, let nodes reject blocks that failed to signal support, and run the whole experiment on a one-year timer. A temporary rule, seven constraints, and an early grave.
The seven constraints themselves were modest on the surface — caps on script sizes, limits on data-carrying outputs, a compression of the envelope for non-payment payloads. But modesty did not translate into support. The proposal's sunset design was its quiet undoing: a rule designed to expire asks the network to coordinate twice, once to switch on and once to switch off. In a protocol where change is deliberately expensive, asking for two changes where one permanent decision would do is a structural weakness that no amount of good intentions could overcome.
The substance, nonetheless, is legible. The proposed soft fork would have compressed the ceiling on non-payment data, limiting the inscriptions that have effectively turned Bitcoin's blocks into a low-cost storage medium. Nodes running the new rules would reject blocks that failed to signal support. The stated aims: relieve storage and bandwidth pressure, restore the network's focus to value transfer. The activation standard: miner signaling, historically set at 95% of hashrate under the BIP9 version-bits regime. The actual support: 2.6%.
That gap — 2.6 against 95 — is not a margin. It is a verdict.
History offers a useful contrast. SegWit, the last major soft fork, also endured a long signal drought; at its lowest point, support hovered in the twenties and thirties, and it took the credible threat of a user-activated soft fork to push miners to 95%. But even SegWit never lived at 2.6%. A proposal sitting at that level weeks before its own checkpoint is not in a negotiation. It is in hospice. The activation math does not allow for a last-minute surge: coordinated hashrate signals take months of software deployment, mining pool policy changes, and operational coordination across thousands of sites. None of that infrastructure has been built.
I have spent enough time around mining operations to know that miners are not ideological. They are industrial. Their hash power is a physical asset with an electricity bill attached. When they decline to signal for a proposal that would suppress data-carrying transactions, they are not making a statement about Bitcoin's "purity." They are reading their own profit-and-loss statements. Since the inscription wave began, a meaningful slice of transaction fees has come from data rather than payments. The 2020 research I conducted into MakerDAO's stability mechanisms taught me that incentives write behavior more reliably than manifestos do; the same logic governs hashrate. Yields do not vanish; they merely change form. The yield here is the quiet accretion of fees from low-value, high-volume data transactions — and miners have decided that this yield is worth the philosophical discomfort of the purists.
This is the insight the market keeps missing: the 2.6% figure is not miner apathy. It is miner preference. The economics of the modern Bitcoin block have shifted so far toward data storage that the network's own security apparatus now holds a financial stake in the very thing the proposal sought to ban. Every block carrying inscriptions pays the miner who mines it. A miner who supports BIP-110 is voting to reduce his own future revenue stream. The fact that only 2.6% of hashrate is willing to do that is not a governance failure. It is a rational market clearing.
The silence is the signal. In protocol governance, a proposal that fails because of active opposition is one thing; a proposal that fails because no one bothered to signal is another. The latter is a revealed preference. Miners have not merely declined to support the restriction; they have declined to even participate in the vote. That is the difference between a contested election and a coronation. The hashrate has chosen its side not by shouting but by staying home.
There is a second layer, less visible but more important. Miners may be rejecting the mechanism, not merely the measure. A temporary soft fork with a sunset clause sets a precedent that organized hash power can, under the right narrative pressure, rewrite consensus rules on a limited-time basis. Once that precedent exists, it can be reused. Every subsequent cultural panic — a memecoin wave, a new data format, a controversial transaction encoding — becomes an excuse for another "temporary" fork. Miners understand that the permanent thing about temporary rules is the habit of making them. They also understand the operational burden: a one-year sunset rule forces node operators to upgrade twice, once to enforce the restriction and again to remove it, multiplying coordination risk for a transient gain. By declining to signal, miners are defending not the Ordinals market but the stability of the rule set itself. Security is a silent promise kept between nodes; the promise here is that consensus changes remain rare, difficult, and permanent when they finally come.
Saylor's declaration, read in this light, is not a cause but a confirmation. He leads Strategy, the publicly traded vehicle holding hundreds of thousands of bitcoin, and he cannot move three percent of hashrate. That is the healthiest governance signal Bitcoin has produced in years: no single balance sheet, no matter how large, dictates protocol direction. The image is not the asset; the belief is. And the belief that Bitcoin's rules bend to whale sentiment is the one asset the network refuses to issue.
The market's reaction is worth a footnote. The news was roughly sixty to eighty percent priced in before Saylor spoke; the proposal's failure had been visible in the signaling charts for weeks. The statement's real function was to certify the obvious and to calm institutional nerves — a declaration that no fork, no split, and no chaos would arrive at the checkpoint. For a market conditioned by the Merge, by Terra, by every consensus-level drama of the last cycle, the message was reassuring precisely because it was boring.
For the Ordinals ecosystem, the confirmation is a reprieve with a clock. Short-term, the threat of protocol-level censorship has vanished, and projects can build without looking over their shoulders at a consensus rule change. Miners, meanwhile, continue to pocket the fees from data-heavy blocks, and their shares trade on the promise that the fee stream persists. But a reprieve is not a settlement. Every party in this arrangement now knows that the question was raised, and that the answer can be revisited.
The contrarian reading cuts deeper. The death of BIP-110 is being celebrated by Ordinals proponents as a victory for open block space, and by conservatives as proof that Bitcoin remains serious money. Both are missing the actual outcome. The proposal's failure does not preserve the status quo; it ratifies a slow mutation. Bitcoin's fee market has already been structurally rewritten. The block is no longer exclusively a settlement space for payments — it is a storage bazaar where data competes against value for scarce bytes. If the inscription flow continues, the 2028 halving will push fee revenue to a larger share of miner income, locking the network's security budget to the health of the data market rather than the payment market. The mining industry is acquiring a dependency it cannot easily unwind. What looks like stability — no fork, no change, no drama — is actually the quiet compounding of a new economic constitution. Stability is the quiet architecture of trust, but the foundation is no longer made of payments alone.
There is also the question of what a failed proposal leaves behind. Even a corpse shapes the room. BIP-110 has shifted the Overton window of Bitcoin governance: the question is no longer whether the network should address data-driven congestion, but when and by what mechanism. The purists lost this battle, but they successfully planted the proposition that block space is a finite public resource with a policy problem. That framing will outlive the proposal itself. Every future fee spike will cite it; every future panic over a new inscription wave will resurrect it.
Something else was lost in this quiet failure: the purity of the monetary narrative. Bitcoin's "digital gold" thesis rests on the claim that the network is focused, disciplined, and singular in purpose. A block space increasingly occupied by jpegs and data blobs complicates that story. The failure of BIP-110 does not restore the old narrative; it forces the market to accept a new one, in which Bitcoin's security is subsidized by activities the maximalists despise. The monetary premium and the storage economy are now locked in the same block, whether either side likes it or not.
There is a timing nuance worth surfacing as well. Saylor chose August 8, roughly five weeks before the referenced checkpoint, to deliver the eulogy. In my experience coordinating crisis communications during the Terra collapse of 2022, the timing of a public statement during a panic told you which fires someone wanted to prevent. Here, the window is calm, the markets are consolidating, and the statement functions as a sedative: no fork, no split, no disruption. It is a message aimed at institutional holders who fear protocol drama, not at the miners themselves. The tactical effect is negligible; the symbolic effect is to close the narrative chapter so that attention can move elsewhere. Attention, as I documented in my 2021 research on NFT provenance and secondary-market liquidity, is the true reserve currency of this industry. Value flows where attention decides to rest — and BIP-110 was never where the smartest attention was going to settle.
The next iteration will not look like this one. It will not carry a borrowed number, nor will it rely on formal activation thresholds. It will arrive either as a miner policy — an unofficial, behavior-level filter that never touches a BIP — or as a more aggressive formal proposal after the 2028 halving, when fee pressure has become impossible to ignore. The question is not whether Bitcoin will ever limit its data appetite. The question is whether the limit, when it comes, will be negotiated by the miners who profit from the status quo or imposed by a user base grown tired of paying for other people's jpegs. I suspect the former. Miners do not surrender revenue; they lease it to whoever pays the highest price. Based on my audit experience, the safest prediction in this industry is that rational actors follow their profit-and-loss statements until someone changes the game theory — and nobody has changed it yet.
The deeper question is whether a network built for final settlement can afford to be everything. Bitcoin has survived every attempt to redefine it, and it will survive this one. But survival is not the same as clarity. The next decade will test whether a blockspace shared by payments, files, and financial ephemera can remain both scarce and legible. I suspect the answer is yes — but the price of that answer will be paid in complexity, and complexity is always the tax that decentralization silently collects.
So watch the fee market, not the fork. Watch the mempool composition in the months after block 961,632 passes. Watch the share of block space consumed by data rather than payments, and watch whether the next proposal arrives with a clean number and a full implementation. If it does, it will be because the economics finally aligned, not because a billionaire said so. The natural death of BIP-110 is not the end of the argument. It is the first confirmed data point in Bitcoin's next decade of quiet negotiation between what a block is for and who gets to decide.

