The ledger doesn't lie. Right now, it reads 2.6% — the share of Bitcoin miners signaling support for BIP-110 as of the latest measurement. That is not a consensus. That is not a credible minority. That is a rounding error in hashpower terms. Yet the market narrative building around block height 961,632 is behaving as if a constitutional crisis is imminent.
It isn't. But something genuinely dangerous sits inside the activation window. And it has nothing to do with whether the fork actually takes place.
The public sees the spark; I track the fuel lines. The spark is BIP-110, a proposal to strip non-payment data from Bitcoin's transaction set. The fuel lines run through a replay attack vector that will hit users who transact at the wrong moment. The distance between those two observations is the difference between staying whole and losing real BTC.
I learned this distinction in 2017, when I audited the 2Fun ICO. The market saw a roadmap and a promise. I saw $4.2 million in raised capital, 60% of it transferred to unverified wallets with no escrow mechanism. The token lost 40% of its value in 48 hours after my forensic breakdown. The lesson wasn't that fraud exists — it's that the visible event and the structural failure are rarely the same thing. BIP-110 is not fraud. But the misdirection is identical.
Context: A Purification Campaign Dressed as a Proposal
BIP-110 is not a scaling proposal. It is a purification campaign. Its technical intent is narrow: prohibit image, text, and other non-payment data from being embedded in Bitcoin transactions. The target is the Ordinals/inscriptions ecosystem that has congested block space since 2023.
To activate, the proposal requires miner software support. Current signaling: 2.6%. That is not close to any activation threshold. For scale, the 2017 Bitcoin Cash fork carried roughly 15-30% miner support before it split. BIP-110's base of support is roughly a tenth of that. This is not a fork with a constituency. It is a fork with a flag.
This is the latest round of a conflict as old as Bitcoin itself. The Block Size War. The BCH exodus. The BSV fracture. Every iteration has been a philosophical argument about what block space is for. BIP-110's proponents occupy one pole: Bitcoin is a settlement layer, and non-payment data is pollution. The Ordinals movement occupies the other: block space is a market, and if someone pays fees for it, the market has spoken.
Both positions have internal coherence. Neither is a technical breakthrough. On my assessment matrix, BIP-110 scores as micro-innovation at best: it restricts existing transaction formats rather than introducing a new paradigm. Compared with Taproot — which activated through genuine community coordination — BIP-110 is a border-control measure wearing a proposal number.
Core: The Fork Mechanics and the Real Vulnerability
Walking through the technical path: BIP-110 is a hard fork, not a soft fork. Nodes that enforce the new rules will reject non-compliant blocks. If a minority chain emerges, it shares all historical transaction history with the main chain, and every Bitcoin holder carries a duplicate balance on both chains. This is standard fork anatomy. It is not the problem.
The problem is replay protection. In the early life of this fork, neither chain protects transactions from being valid on the other chain. That absence creates a cryptographic footgun.
Trace the attack sequence. A user signs a transaction on the fork chain — selling fork coins, say. The signed transaction broadcasts across the fork network. Because both chains contain identical UTXOs, that same signature is valid on the Bitcoin mainnet. An attacker — or even just a miner relaying transactions — can copy that transaction onto the mainnet. The user receives proceeds on the fork chain while simultaneously moving an equal amount of real BTC on the mainnet. Without authorizing it. Without even knowing it happened until the confirmation lands.
The mechanism is simple enough to diagram in three lines. The consequences are not abstract. In 2022, after Terra collapsed, I spent four weeks reconstructing the UST death spiral. That was a structural failure of seigniorage incentives and oracle design. This is different. It is a signature-level failure, and it will be borne entirely by users who choose to interact during the risk window. The asymmetry is brutal: holders who do nothing are safe; traders who seek value from the fork expose their principal.
Key facts anchor this analysis. Activation begins — if it begins at all — at block height 961,632, where enforcing nodes reject non-compliant blocks. The fork chain would carry a small fraction of Bitcoin's hashpower. Under Bitcoin's difficulty adjustment algorithm, that means unstable block times and unpredictable difficulty swings. A low-hashpower chain is not merely slow; it is a 51% attack waiting for a buyer. Security on that chain is not degraded — it is absent.
A minority chain at 2.6% of hashrate faces a brutal economic bind. The block subsidy is paid in a coin with no market value. The difficulty will adjust downward, but over a cadence measured in days, not blocks. In that vacuum, block production becomes erratic — ten blocks in an hour, then nothing for a day. Applications cannot build on that. Exchanges cannot clear on that. Custodians will not touch that. The chain does not fail because of censorship or attack; it dies of economic irrelevance. I have seen this cycle in every low-hashpower fork since 2016. The pattern is invariant.
The token economics amplify the hazard. Every BTC holder receives a 1:1 balance on both chains. In form, it is an airdrop. In substance, it is a negative-sum event. The fork coin has no independent issuance schedule, no ecosystem, no revenue, no value capture mechanism. It is a shell token on a chain that cannot protect itself. Its theoretical market depth would be minimal; any sell order of meaningful size would face extreme slippage or no buyer at all. The only way to realize value is to transact — and transacting is exactly what opens the replay vector.
Supply-side analysis produces the same conclusion from a different angle. The main chain's 21 million cap is untouched; the fork changes nothing about Bitcoin's monetary schedule. But both chains will claim the Bitcoin name. That nomenclature collision is not a technical problem — it is a credibility problem. Exchanges will have to label ambiguous assets, custodians will need to segregate balances, and users will face confusion about which "BTC" they hold. These costs are real, even if they are unmetered in the current analysis. A fork does not need to succeed economically to create accounting overhead across the industry.
I have stress-tested similar incentive structures before. In 2020, I reverse-engineered Compound's rate models and ran liquidation simulations against a 50% market crash. The finding — that over-collateralization ratios were dangerous for volatile collateral — was structural, not anecdotal. The same method applies here. Model the incentives: a rational actor on the fork chain has almost no upside and a clearly defined downside. The trade only makes sense if the user believes the fork chain will somehow achieve independent economic viability. With 2.6% hashrate support, that belief is not an investment thesis. It is a hope.
Market impact, meanwhile, should remain contained. My estimate is that 30-50% of the event risk has already been priced into volatility expectations. BTC price deviation from the fork window should stay within roughly ±2% to 3%. The fundamental ledger does not change; the supply cap of 21 million remains intact on the main chain; the digital gold narrative is untouched by a minority split. Historical precedent supports this. The 2017 BCH split generated short-term swings and arbitrage flows, but it did not derail Bitcoin. The 2016 ETC fork produced initial confusion, then receded into a footnote. BIP-110's miner support is a fraction of what those events carried. Market attention on "Bitcoin forks" is exhausted — BCH, BSV, BTG all failed to displace the core chain, and the audience has learned to look away.
The more dangerous market scenario is not the fork itself. It is the first publicly reported case of real BTC theft via replay. One verified incident — screenshots, a transaction hash, a victim's story — would amplify FUD far beyond what the 2.6% support number justifies. Event-driven volatility spikes in the 24 hours before block 961,632 should not be mistaken for fundamental repricing. If BTC price flashes an abnormal wick near that height, read it as positioning noise, not a change in the ledger's integrity.
The ecosystem impact is concentrated at the infrastructure layer. Exchanges must decide whether to pause deposits and withdrawals during the window or deploy replay protection tooling. Wallet providers need splitting scripts and user-facing warnings. The responsible ones will move within hours to days of any actual split. The risk window is not infinite — it is measurable in hours, possibly days. But within that window, the cost of a single mistaken transaction is denominated in real BTC.
Contrarian: What the Skeptics Get Right, Unintentionally
It would be easy to file BIP-110 under noise. The support level is trivial. The fork likely will not form. The market impact will be modest. All of that is true. And all of that misses the signal inside the noise.
The developers pushing this proposal are not irrational. They are responding to a genuine governance gap: Bitcoin has no native mechanism to price externalities on block space. Ordinals demonstrated that arbitrary data can be embedded in fee-paying transactions, and no on-chain mechanism stops it without a rule change. That question is not settled. It will resurface — under different proposal numbers, possibly with broader support — every time block congestion spikes.
The public warning itself carries a second-order effect worth noting: it reduces the attack surface. The more the replay risk is broadcast, the fewer users will trade fork coins, the fewer signed messages exist to copy, and the less frequently the attack actually fires. The warning operates like a protocol-level immune response. It does not repair the vulnerability; it reduces the number of susceptible hosts.
One caveat on the proposal's identity: "BIP-110" may itself be a misnumbering. The Bitcoin community has more commonly referenced alternate numbers for inscription-restriction proposals, and the reporting could carry a labeling artifact. I assign that low-to-medium confidence. But the number matters less than the mechanics. I would rather audit the replay vector than argue over the proposal ID.
Takeaway: The Ledger Does Not Forgive Careless Signatures
Position for the resolution, not the noise. The probability that BIP-110 produces a viable fork chain is low. The probability that some user loses real BTC to a replay attack while transacting in the window is materially higher. That asymmetry is the entire story. Stay on the main chain. Move nothing during the activation window. Your balance is untouched; your exposure is zero.
The ledger does not forgive careless signatures. It does not read narratives, proposal numbers, or philosophical manifestos. It records what is signed and broadcasts where that signature is valid. In a fork without replay protection, that validity extends to two chains at once — and the price of that ambiguity is paid in BTC.
The public sees a fork. I see a vector. The data says the fork is improbable. The data also says the vector is real. The only question that matters: when block 961,632 arrives, will your signature be on the right side of the split?