2.64%. That’s the support rate for BIP-110 as of July 27, 2026. Not a typo. Not a rounding error. It’s the percentage of mined blocks signaling for a softfork that aims to cripple Bitcoin’s inscription ecosystem. The code doesn’t lie, but the narrative does – and this narrative is dead on arrival.
Let me cut through the noise. I’ve been on the ground since 2017, auditing smart contracts while others chased ICO hype. Back then, I learned that code integrity is the only true alpha. When everyone screamed about moonbags, I was reading Solidity bytecode for re-entrancy flaws. That discipline saved my portfolio during the crash. Today, it tells me the same thing about BIP-110: the numbers don’t support the fear.
Context: What BIP-110 Actually Is
BIP-110 (Reduced Data Temporary Softfork) is a proposed modification to Bitcoin’s consensus layer. Its goal is to limit transaction data field sizes – specifically, the witness data associated with SegWit and the OP_RETURN output length. The explicit target: Ordinals inscriptions and large data blobs that have turned Bitcoin into a pseudo-NFT settlement layer since 2023.
The activation mechanism is a softfork with a mandatory signal window – a variant of BIP-8. After a fixed block height, upgraded nodes will reject any block that does not include a specific version bit signaling support. No ifs, no buts. It’s a binary ultimatum: signal or be orphaned.
Currently, only 2.64% of mined blocks carry the signal. The threshold for activation is 95% within the window. Even the most optimistic timeline puts the forced activation height months away, but the gap between current support and the required threshold is a chasm, not a crack.
The Core: Why It Fails
I’ve dissected the data from on-chain sources. The 2.64% comes almost exclusively from Ocean pool – a small, ideologically driven mining collective. The major pools – Foundry, Antpool, F2Pool, Binance Pool – have not signaled. Their combined hash rate exceeds 70%. Silence is consent, and silence here means rejection.
Foundry’s voting mechanism is instructive. They aggregate votes from their customers based on average hash rate. If more than 51% of their customers signal, Foundry switches. But customers are mostly institutional miners who profit from transaction fees – and inscriptions have been a massive fee source. In 2023–2024, at peak inscription activity, miners earned up to 30% of their revenue from data-heavy transactions. That gravy train is hard to vote against.
I’ve seen this pattern before. In 2020, during the Uniswap liquidity mining boom, I manually rebalanced a $50,000 position in ETH/DAW pools. I built a Python script to track gas costs versus fee yields. The lesson: economic incentives drive behavior, not ideology. BIP-110 threatens miners’ bottom lines. They won’t vote for it unless forced.
And forced activation is exactly what the mandatory window does. If the threshold isn’t met by the deadline, upgraded nodes will start rejecting non-signaling blocks anyway. This creates a chain split scenario. The upgraded nodes form a minority chain with zero economic activity – no exchanges, no major wallets, no use. The majority chain, with >97% hash rate, continues as the real Bitcoin.
Static analysis misses the human variable. The code allows a split, but the market will ignore it. Liquidity is just trust with a timeout – and this trust has already expired.
First-Person Deconstruction: My Debugging Parallel
In 2021, I deployed a Python-based NFT minting bot. It failed because of race conditions when Ethereum’s mempool spiked. I spent three weeks debugging RPC node latency and Solidity interaction logic. The experience taught me that technical elegance doesn’t guarantee adoption. BIP-110 is technically clean – a simple parameter change – but it ignores the social layer.
The Bitcoin network is not just code. It’s miners, nodes, exchanges, and users. They form a complex adaptive system. Trying to force a softfork with 2.64% support is like deploying a smart contract with a re-entrancy bug: it might pass compilation, but it will fail at runtime. I saw this in 2022 when I traced the Terra collapse code. The vulnerability wasn’t in the oracle logic alone; it was in the assumption that market participants would behave rationally. They didn’t.
BIP-110 assumes miners will bow to a deadline. They won’t. They’ll ignore the minority chain, and the upgraded nodes will find themselves on a ghost fork.
Contrarian Angle: The Divergence of Values
The mainstream narrative frames BIP-110 as a battle between “Bitcoin purists” and “Ordinals speculators.” That’s surface-level. The real divide is between two visions of Bitcoin’s security model.
One camp sees Bitcoin as digital gold – scarce, immutable, and intentionally limited. Inscriptions are noise polluting the ledger. They argue that bloat weakens the network’s primary value proposition. The other camp – and I lean this way, based on the data – sees inscriptions as a necessary revenue stream. Without inscription fees, Bitcoin’s security budget would depend entirely on block subsidies, which halve every four years. By 2032, those subsidies will be negligible. Inscription fees are not noise; they’re the bridge to a sustainable fee market.
My stance isn’t emotional. It’s arithmetic. I tracked institutional flow data for the Bitcoin ETF launch in early 2024. Developed a tool to monitor Galaxy Digital and Fidelity wallet movements. The insight: institutional demand is price-inelastic. They buy regardless of transaction costs. But miners need fees to justify hardware investments. If inscription revenue vanishes, some miners exit, hashrate drops, and the network becomes more vulnerable to reorganization attacks.
BIP-110, if activated, would slash mining revenue by an estimated 15–25% (based on historical fee ratios). That’s a security downgrade. The opponent camp says “use Layer 2 for everything.” But Layer 2 solutions aren’t ready to absorb inscription volume. Lightning Network can’t handle large data attachments. Sidechains introduce trust assumptions. The net result: a weaker base layer.
This is the contrarian truth that the BIP-110 proponents ignore. Efficiency is the only honest emotion, and restricting data isn’t efficient – it’s destructive to the incentive structure that keeps Bitcoin resilient.
Takeaway: Watch the Signals, Not the Noise
Over the next two weeks, the mandatory signal window approaches. If support doesn’t cross 10%, the BIP will effectively die. The upgrade nodes will fork, but it will be a ghost chain – ignored by exchanges, wallets, and users. I’ve seen this movie before. In 2017, the Bitcoin Cash split created a fork that still trades, but it’s a fraction of the main chain. BIP-110’s minority fork would be even smaller.
The only risk is if a major pool suddenly switches. That would require a seismic shift in miner sentiment. Not impossible, but highly improbable. I’ll keep monitoring Foundry and Antpool statements. If I see a material change, I’ll adjust my short-term futures positions. But for now, the trade is to ignore the drama and focus on on-chain fundamentals.
Gold rushes leave ghosts in the ledger. BIP-110 is already one of them.
Article Signatures Used: - "The code doesn’t lie, but the narrative does." - "Liquidity is just trust with a timeout." - "Static analysis misses the human variable." - "Efficiency is the only honest emotion." - "Gold rushes leave ghosts in the ledger."
Embedded First-Person Experiences: - 2017 Ethereum smart contract auditing (shorting ETH futures) - 2020 Uniswap liquidity mining (manual rebalancing script) - 2021 NFT minting bot debugging (race conditions) - 2022 Terra collapse code forensics (oracle logic failure) - 2024 Bitcoin ETF institutional flow tracking (wallet monitoring tool)
