The data shows a hard fork with 2.6% miner support. At block height 961,632, a thin minority of miners can begin rejecting blocks that do not enforce BIP-110, a proposal written to strip images, text, and other non-payment data from Bitcoin transactions. The market has treated this as gossip. It is not gossip. It is a replay attack waiting for a signature. Systemic risk hides in the complexity of the code.
BIP-110 Is a Hard Fork by Default
BIP-110 is a narrow technical response to a messy cultural conflict. Since 2023, Ordinals inscriptions have embedded image and text content in witness data, competing with payment transactions for scarce block space. The proposal says, in effect, that Bitcoin blocks should settle value, not host media. The mechanism is blunt: nodes supporting BIP-110 would reject blocks containing non-payment data. That makes this a protocol parameter change at the L1 consensus layer.
It is not a soft fork. A soft fork tightens rules and maintains compatibility. BIP-110, enforced by a minority that rejects the majority's blocks, creates a node-version split. That is a hard fork by default. The proposal has not passed formal review, and its public activation threshold is unresolved. What is clear is that a minority can define a separate validity rule at a specific block height.
The Activation Math
The activation math is not close. BIP-110 requires miner software support. Current signaling sits at 2.6%. That is below any threshold that could be described as consensus. For comparison, the 2017 Bitcoin Cash split had meaningful miner and community support. The 2016 Ethereum Classic split emerged from a live hacking event. This proposal has neither an emergency nor a constituency. It is a technical dissident's branch attempt.
| Metric | Bitcoin Main Chain | Hypothetical BIP-110 Fork | |---|---|---| | Miner support | ~97.4% | ~2.6% | | Consensus position | Existing standard | Minority enforcement | | Replay protection | Native to ecosystem | Missing at launch | | Economic value | Global reserve asset | Near zero without liquidity | | Risk to passive holder | None if idle | None if idle | | Risk to active trader | Low | High until protected |
The table should be uncomfortable for anyone who thinks a theoretical fork coin is free money. The minority chain carries the same UTXO set as Bitcoin, but it does not carry the same security budget. Every transaction on that chain is a transaction that can be replayed on the main chain.
The Replay Attack Is Not Theoretical
But the fork probability is not the relevant risk. The relevant risk is the window created if a minority chain exists at all. Let me state the transaction path exactly. A user signs a transaction to sell the fork coin on the minority chain. The transaction references a UTXO that exists on both chains because both chains share identical history. A third party copies that signed transaction onto the Bitcoin main chain. The main-chain UTXO moves to the buyer's address. The seller receives the fork coin and simultaneously loses real Bitcoin.
The seller made no coding error. The seller simply tried to exit a worthless asset without replay protection. In the 2018 ICO audit cycle, I reviewed contracts where integer overflow was dismissed as theoretical until someone packaged it into a transaction. Replay risk has the same profile. It looks like a wallet display problem until it is a settlement problem. Proof is required, not promise. Before any interaction with a fork coin, the user must verify that the wallet separates chain identifiers and uses replay-safe signatures. Most wallets will not offer that verification in the first hours.
The Economics Reinforce the Hazard
The economics reinforce the hazard. A fork chain running on roughly 2.6% of total hash power will not settle blocks at a predictable interval. Bitcoin's difficulty adjustment does not instantly recalibrate for a minority fork; the chain will limp until the next retarget. Irregular block times mean poor user experience, weak liquidity, and no developer incentive. The fork coin inherits the 21 million supply cap, but inherited supply is not value. It has no revenue, no ecosystem, and no independent issuance schedule.
Once liquidity fails, the fork enters a negative feedback loop: less hash power, slower blocks, worse markets, less hash power. The theoretical airdrop value approaches zero, while the potential loss of main-chain BTC remains real. This is negative-sum. There is no admin key and no legal entity to hold accountable for the fork. That makes the split structurally decentralized but operationally dangerous.
The Market Has Priced the Wrong Variable
Market pricing already discounts most of this. I estimate the BIP-110 debate is 30 to 50% priced if it has reached institutional flows. A base case move in Bitcoin of plus or minus 2-3% is reasonable. Historical splits support that ceiling. The 2017 BCH fork had more support and more infrastructure, and it produced short-term volatility without ending Bitcoin. The 2016 ETC split caused confusion but did not permanently damage Ethereum's price path.
BIP-110 is an order of magnitude weaker on every dimension. Market attention spans for forks are spent. BCH, BSV, and BTG all failed to displace the main chain. The narrative will fade unless a new data point arrives. That data point is the one thing the market is not pricing. If a credible report appears of a real replay theft near block 961,632, the event will be treated as a Bitcoin security failure, not a user error. Exchanges will pause withdrawals, fear, uncertainty, and doubt will spike, and the short-term liquidity of exchange-held BTC will drop. I am not predicting a price crash. I am predicting a structural reaction that resembles a crash even though the underlying ledger is unharmed.
The Bulls Are Right About the Fork
Here is the contrarian point: the bulls are right that the fork will almost certainly fail. 2.6% support is not a movement; it is a rounding error. Bitcoin has survived more legitimate forks with more resources and better timing. Market fatigue is a genuine protective factor. It stops exchanges from rushing to list a fork coin out of competitive fear. It also suppresses speculative demand.
A note on terminology. The number BIP-110 is itself disputed in public forums; some observers expected an inscription-rules debate under BIP-420 or another identifier. That discrepancy is unresolved. My assessment does not depend on the number. The structure is what matters. In this specific setup, the main risk is not the chain split. The risk is the user who treats a fork as an opportunity to claim free value. The fork coin will be described as an airdrop. It is not an airdrop. It is an attack surface.
From my 2024 ETF prospectus audit, I learned that disclosure timing determines customer harm. The prospectuses that described custody and fee differences clearly caused fewer disputes. The ones that deferred the questions caused the losses. BIP-110 follows the same logic. If exchanges publish replay protection plans before the fork, the damage window narrows. If they wait for a theft, the window expands. The test is not whether the fork happens. The test is whether the industry has prepared the controls before the first transaction.
Immediate Action Items
Immediate action items are straightforward. Monitor hash-rate distribution around block 961,632. Do not send transactions from fork-chain wallets to exchanges until replay protection is publicly confirmed. Treat any tutorial that instructs splitting without technical verification as hostile. Require exchanges to state their fork policy before block height, not after. The protocol does not care about intent, and risk management should not either.
Final Assessment
The final assessment is blunt. If BIP-110 produces a chain, that chain is not a competitor to Bitcoin. It is a protocol-level hazard. The supply side is weak, the infrastructure side is unprepared, and the user side is uninformed. The only stable position is the one that requires no transaction. The market will not wait for a clean solution. It will price the first victim.
Systemic risk hides in the complexity of the code. The code in this case is simple enough to kill. Proof is required, not promise. Decentralization is not a slogan; it is a distribution of hash power. The proof of safety will come from replay protection, audited wallet behavior, and exchange disclosures made before the fork. Without those, every optimistic headline about a free fork coin is a future liability.
