Block height 961,632 now carries a governance deadline. The data: BIP-110 — the temporary soft fork proposal imposing seven consensus restrictions on non-payment data — has secured 2.6% of miner signaling support. That is not a negotiating position. It is not a close call. Under BIP-9's version-bit mechanism, activation requires 90% of blocks within a 2,016-block difficulty period to carry the signal. 2.6% is roughly 34 times below the threshold. The proposal carries a one-year sunset clause. It will expire before it can activate. The failure is deterministic.
But the number is not the story. The story is that the number exists at all. BIP-110's vote is the first formal, on-chain measurement of a governance fracture that has been widening since inscriptions began occupying Bitcoin blocks in 2023. The monetary purists, led by Michael Saylor, want data off the base layer. The inscription ecosystem wants Taproot's script space preserved as an open data market. The miners — the only actors whose signal actually counts — have responded with a number that looks like rejection but reads, on closer inspection, as disinterest.
This is the lesson of every governance dispute I have dissected since 2018: when a proposal's technical substance is weak, its political signal is strong. BIP-110's seven restrictions are a policy preference wearing the costume of a consensus rule. The failure mode is not the vote; it is the precedent. A failed soft fork leaves behind a quantified measure of how the network's most critical stakeholders view data competition for block space. That measurement is now public. It cannot be unrecorded.
The collision is between a 2021 upgrade and a 2023 phenomenon. Taproot, defined in BIP-341, activated in November 2021, expanding Bitcoin Script with merkleized abstract syntax trees. The upgrade was sold as a privacy and scalability improvement: complex spending conditions rendered as single-looking transactions. What it also enabled was arbitrary data embedding. In December 2022, the Ordinals protocol formalized a method to inscribe data into the witness portion of Taproot outputs. By early 2023, images, text, and audio were permanently etched into the ledger.
BIP-110 is the backlash, formalized. Its sponsors propose seven consensus restrictions on non-payment data, effective for roughly one year. The mechanism is a temporary soft fork, signaled by miners through BIP-9. Old nodes still validate the new blocks; new rules reject blocks carrying restricted data. No permanent consensus change. No hard fork. An experiment in enforcement, testing whether the network can police its own block space. The probability of activation is effectively zero. That conclusion is not a prediction; it is arithmetic.
The definitional problem is the proposal's soft underbelly. Bitcoin does not classify transactions by intent. Every satoshi is a bearer instrument; every transaction is a transfer. "Non-payment data" is not a consensus-level category; it is an interpretive one. The same bytes that carry an image can carry a notarized document, a timestamped hash, or a legal contract. BIP-110's sponsors are asking the network to draw a line the protocol was never designed to draw. That is a structural objection, not a technical one.
Michael Saylor has become the public face of the purist camp. His argument is actuarial: block space is a shared resource, and data blobs impose a congestion tax on every payment. Inscriptions are not free expression; they are subsidized pollution. The counter-argument, from the inscription ecosystem, is equally principled: Taproot made the data path legal, and retroactive restriction is centralization by another name. Core maintainers have stayed publicly neutral, which is itself a signal: the dispute is being left to miners and node operators to resolve.
The governance fracture is real. What BIP-110's 2.6% reveals is how that fracture maps onto economic incentives — and where the next battle will be fought.
The math of a stillborn proposal
Start with what 2.6% actually means. During the most recent difficulty period, 2.6% of mined blocks carried BIP-110's version bit — roughly 52 blocks out of 2,016, likely concentrated in a single pool or a small cluster. Concentration matters. A signaling figure this low is not ecosystem consensus; it is a corporate preference photographed at a particular moment.
BIP-9's history provides context. Successful deployments — BIP-34, BIP-66, BIP-65 — activated quickly because support was early and overwhelming. Controversial proposals have languished because signaling is cheap to withhold and expensive to retract. Miners do not signal for rules they do not intend to enforce. The version bit is a commitment; committing to an unproven rule without community consensus risks producing blocks a significant share of the network rejects. That risk explains silence better than ideology.
Based on my three-month audit of 0x Protocol v2 in 2018, I learned to treat self-reported signals the way I treat unverified function calls: as claims to be checked, not statements to be trusted. The version bit is a claim. The block hash is the proof. Here, the claim is barely visible.
Code speaks louder than promises.
The fee market contradiction
Miners are revenue-maximizing agents. Block subsidies halve every four years; the April 2024 halving reduced the subsidy to 3.125 BTC. Fee income is no longer a rounding error — it is the growth component of miner revenue. During congestion windows, non-payment data — inscriptions, BRC-20 transfers, and other Taproot-embedded payloads — can account for a substantial share of total fees. The exact percentage fluctuates, but the trajectory is structural: the fee market has developed a demand segment that did not exist before 2023.
That segment is price-insensitive in ways payment traffic is not. An inscription waits. A payment cannot. When block space is scarce, every byte of inscription data displaces a byte of payment data. The auction mechanism does the rest: fees rise, and the marginal payment transaction is priced out. Miners capture the increase regardless of which side wins. That is the uncomfortable symmetry — miners profit from the dispute either way, which is precisely why their signal is so hard to read. Their silence is a hedge.
Name the precedent: this is the first consensus proposal in Bitcoin's history to target a data class rather than a bug or an upgrade path. That novelty alone explains why the governance machinery is struggling to process it. I wrote in 2020 that Compound's yield-farming incentives were mathematically unsustainable — emissions outpacing locked value guaranteed a depeg. The market laughed; the arithmetic won. The same arithmetic applies here. A proposal that asks miners to ban a fastest-growing revenue stream asks them to vote against future income. No governance mechanism survives that contradiction.
Follow the gas, not the narrative. The gas says inscriptions subsidize the transition to a fee-driven miner economy.
The block 961,632 ambiguity
The most underreported risk is not at the voting booth; it is at the execution layer. BIP-110 states that, at the designated block height, "nodes will reject blocks that do not signal." For a consensus commitment, that phrasing is dangerously underspecified.
Which nodes? Which client versions? What exactly is the validation rule? The spec provides no unambiguous predicate. In consensus code, ambiguity is not a documentation issue; it is a fork vector. A small cohort of node operators running a modified client could produce a transient chain split at block 961,632 — not because the proposal activated, but because partial enforcement created divergent validation behavior.
I have seen this pattern before. In 2022, I audited Terra's algorithmic stablecoin mechanism and concluded that the death spiral was not a black swan but a deterministic outcome of the peg maintenance logic. The same lens applies here. When a rule is underspecified, the outcome is predictable divergence. The only question is whether enough operators act on the ambiguity to make it visible.
This is also the institutional blind spot. After the 2024 ETF compliance review — where I found centralization risks in multi-signature custody key management — I learned that institutions prepare for known failure modes, not undefined ones. Exchanges will not be ready for a rejection rule that no one can precisely define.
A blunt instrument
Examine the seven restrictions. BIP-110 cannot distinguish between an image inscription and a legitimate data commitment. Timestamping services, notarization protocols, and authenticated metadata all use Taproot's witness space. The blanket approach either catches them all or is bypassed by all of them.
Circumvention is trivial. Data can be compressed, encoded into key-spend paths, or split across transactions. A rule that can be evaded by changing the encoding scheme is not a rule; it is a speed bump. And speed bumps in consensus code force the next proposal to be more aggressive. A failed soft restriction often seeds a harder one — a ratchet effect that pushes the base layer away from its neutrality principle.
I am not arguing that inscriptions are valuable. I am arguing that consensus-rule enforcement is a catastrophic tool for expressing preference. The ledger is not a legislative chamber.
What this means for inscription assets
For holders of inscription-linked assets — ORDI and its analogues — the low support number is a double-edged sword. Short-term, it removes the regulatory overhang: the enforcement shoe will not drop through BIP-110, and the market can price a temporary reprieve. But failure of one instrument does not eliminate exposure. Inscription assets remain hostage to a debate that will be re-litigated because the structural tension — data competing with payment for block space — is unresolved.
The ninety-day window is the relevant trading horizon. If no alternative proposal emerges and support stays in single digits, the regulatory overhang is cleared for the quarter. That is a tactical trade on a specific clock, not an endorsement of the asset class. From my 2021 investigation into NFT wash trading, I learned that on-chain volume is not a proxy for value. The same caution applies.
The observation protocol
The signals are public; the thresholds are falsifiable.
First, miner signaling. Weekly data from mempool.space and pool announcements shows whether support drifts. The trigger is 10%. At that level, BIP-110 re-enters serious discussion and inscription assets price future restriction risk. Below it, treat the proposal as inert.
Second, alternative proposals. The Bitcoin-Dev mailing list and Bitcoin Optech are where the next BIP will appear. A better-designed restriction — with clear validation rules and a precise definition of restricted data — is the real threat to the status quo.
Third, node behavior at 961,632. One week before the height, monitor node operation reports. Public rejections of non-signaling blocks would signal that partial enforcement has materialized. That is the event that could produce a transient split.
Fourth — the fee ratio. Track non-payment data's share of block weight and fees. If that ratio crosses 50% and stays there, the miner economic base has shifted. BIP-110's 2.6% will be remembered as the opening bid in a longer negotiation.
The contrarian read
The inscription bulls are celebrating a premature victory. They point to 2.6% and declare the purists defeated. They are correct about the vote count and wrong about the signal's meaning.
Silence from miners is not endorsement of the status quo; it is the stance of actors not yet forced to choose. That choice will be forced. If inscription traffic keeps growing, miners will align with one camp or the other — either protect the revenue stream, or conclude that the political risk of defending bloat outweighs the fee income. Neither outcome is priced into inscription assets today.
There is also a legitimate core in Saylor's position. Block space is a shared resource. Congestion externalities are real; payment users do subsidize data blobs during fee spikes. That is a measurable cost, not a fiction. BIP-110 was the wrong instrument, but the accounting problem will not disappear because the proposal failed.
And the bulls' deeper point deserves credit: a failed soft fork demonstrates the base layer's conservatism. Bitcoin's reluctance to change is the feature that gives it credibility. BIP-110's failure — if it fails cleanly — is a proof-of-stability no marketing campaign could manufacture. The question is whether it fails cleanly, or leaves behind an enforcement ambiguity that muddies that proof.
Logic outlives the hype cycle. What predicts the next proposal is the ratio of data fees to payment fees six months from now. Watch that ratio.
Takeaway
Set the watch list. Over 60 days, track whether an alternative BIP emerges with precise validation rules. At block 961,632, monitor node behavior for partial enforcement. Over 6 to 12 months, watch the fee ratio — the share of non-payment data in miner revenue will determine the next round of governance moves.
Trust is verified, not given. The verification is already on-chain: 2.6% is a fact. What it means — for miners, for inscriptions, for the base layer's neutrality — is the question Bitcoin's governance layer has yet to answer. The clarifying question is whether the reaction to 2.6% will be discipline or drift. Discipline means precise language in the next proposal and honest acknowledgment of fee-market tradeoffs. Drift means more underspecified rules and more ambiguity at critical block heights. The clock runs to block 961,632. The ledger will record which path is chosen.