At block height 961,632, a minority of Bitcoin miners will gain the technical authority to reject blocks that contain non-payment data. Public signaling today stands at 2.6%. That is not a base for a fork. That is a rounding error.
I have been tracking this proposal since the Ordinals wave first congested Bitcoin blocks in early 2023. Let me state my conclusion at the outset: the fork itself is not the risk. The replay attack window that opens at the moment of the fork is the risk. If you do not sign a transaction during that window, you are untouched. If you sign one on the wrong network, you can lose real Bitcoin while receiving a worthless fork coin.
This is not hyperbole. It is an engineering fact. And the market is mispricing the probability.
I spent the 2017 cycle auditing ICO contracts for a Shanghai fintech firm. I built a Python verification script that cross-checked token distribution logic against whitepaper claims. It found three critical calculation errors in a prominent exchange token launch. The experience taught me that the most dangerous part of any protocol event is not the event itself. It is the gap between what people believe and what the code allows.
Exit strategies are written in ice, not in hope. This report is written from that position.
Context: The Block Space Wars
BIP-110 is a proposed change to Bitcoin's consensus rules. Its core intention is to restrict the inclusion of non-payment data within Bitcoin transactions. The proposal does not create a new asset class. It does not improve privacy. It is, in essence, a rule that says: blocks are for payments, not for art.
The historical trigger is ordinals. Starting in 2023, a process called inscription allowed users to embed digital artifacts directly into Bitcoin block space. This was made feasible by the Taproot upgrade, which expanded the data capacity of transaction witnesses. The result was a wave of NFT-like assets on the Bitcoin network. The result was also congestion. Block space prices rose. Ordinary payment transactions felt the effect.
The philosophical split is older than ordinals. Bitcoin has always had two competing visions. One vision sees a peer-to-peer electronic cash system. The other sees a settlement layer for the global economy. Over time, the latter has dominated. The block size war of 2015-2017 produced Bitcoin Cash. The immutability debate of 2016 produced Ethereum Classic. In each case, the minority faction chose a separate chain over consensus change.
BIP-110 fits squarely into that historical pattern. It is a minority proposal. The miner support rate is 2.6%. That is far below even the low levels seen during the BCH split, where between 15% and 30% of miners initially signaled support. The proposal has not been integrated into any major client as a default. It has no formal activation pathway.
I need to flag a data-quality issue. The numbering "BIP-110" is questionable. In the Bitcoin community, proposals to restrict data storage are more commonly associated with other numbers, such as a proposal known informally as BIP-420. The available information points do not allow me to cross-validate the reported number. My confidence in the specific number is low.
Why does the number matter? Because a misattributed number indicates a lack of process maturity. If an opposition group is using an ambiguous identifier to generate public attention, the proposal is not ready for engineering review. The warning issued by developer Kevin Loaec is therefore best understood as a rehearsal, a pre-enactment of a potential public safety event. My confidence in that interpretation is medium, but the pattern is familiar. I have seen the same dynamic in other markets: someone raises the flag before the storm, and the market yawns until the first casualty.
Analytical Framework
I structure my assessments through a standardized liquidity-cycle matrix, which I built during the 2020 DeFi liquidity stress test. That framework combines three dimensions: on-chain protocol risk, token supply mechanics, and macro liquidity flows. It is not a predictive model. It is a risk classification system.
The BIP-110 event fits into a specific cell of the matrix: protocol-layer operational risk with low miner consensus and finite technical exposure. This is not a balance-sheet risk. It is not a counterparty risk. It is a transaction-window risk. That classification determines the entire response protocol.
All conclusions in this report are stated with confidence levels. Where the source data is insufficient, I state the assessment as N/A rather than fabricate metrics. Discipline matters more than completeness.
Core Insight I: Technical Analysis of a Minority Fork
Consensus Mechanics
BIP-110 requires miner software support. The rule change is a hard fork, not a soft fork. Nodes that enforce the rule reject blocks containing prohibited data. Nodes that do not enforce it accept those blocks. The two chains share the same historical ledger, but they diverge at the activation block.
The critical detail is that both chains lack replay protection at the moment of divergence. Replay protection is a technical mechanism that makes transactions valid on only one chain. Without it, a signature created on one chain is valid on the other. This is not a theoretical risk. It is the standard outcome of a hard fork that does not implement a chain-identifier system.
The activation threshold in Bitcoin's consensus process is not a single signal. It is a cumulative convergence of miner signaling, node support, and economic adoption. A signal rate of 2.6% means the proposal has not even registered on the measurement scale. It is not close to the threshold. The probability of successful activation is extremely low.
But low probability is not zero probability. The proposal's mechanism does not require industry-wide support to trigger an event. A sufficiently determined group of miners can begin rejecting non-compliant blocks at the specified height. That is the meaning of the 961,632 block number. It is not a target for consensus. It is a potential unilateral enforcement point.
Replay Attack Engineering
The replay attack mechanism requires no advanced tooling. The sequence is straightforward.
A user signs a transaction to sell a fork coin on the fork network. The signature references specific UTXOs. The same UTXOs exist on the Bitcoin main chain. The network and the main chain share the exact same transaction history up to the fork point. The signature does not carry a chain identifier. Therefore, when the user broadcasts the transaction to the fork network, a miner or attacker can copy the raw transaction and rebroadcast it to the main chain.
The result is asymmetric. The user receives whatever proceeds the fork coin offers, which is likely negligible due to low liquidity. At the same time, the user's Bitcoin main chain balance is reduced because the same signature spends the same UTXO.
I want to be explicit about who is affected. The attack only succeeds if the user signs a transaction during the window when replay protection is absent. If a user simply holds coins and does not sign anything, there is no transaction to replay. An idle key is immune. This is the single most important technical fact in this entire report.
I have seen this dynamic before. During the 2020 DeFi summer, I spent hundreds of hours scraping data to model liquidity fragmentation across Uniswap and Curve. I correlated global M2 expansion with on-chain volume spikes. The result was a unified metric I called "DeFi Leverage Risk." The lesson from that exercise was the same: the system's risk is concentrated in user action windows, not in the protocol's static structure.
Activation Probability and Difficulty Adjustment
If a minority fork forms, the fork chain inherits Bitcoin's difficulty adjustment algorithm. That algorithm targets a ten-minute block interval. It does not adjust instantly. It recalibrates every 2,016 blocks.
A chain with 2.6% of the original hashrate will initially produce blocks much slower than ten-minute intervals. Until the difficulty adjusts, block times could stretch to hours. That instability damages utility. No rational market participant wants to transact on a chain that takes four hours to settle a single payment.
The difficulty adjustment eventually recalibrates downward, but the interim period is chaotic. The Bitcoin main chain remains unaffected. Its difficulty is recalculated based on its own hashrate. The minority chain's problem is not the main chain's problem.
There is an additional security consequence. A fork chain with 2.6% hashrate is trivially vulnerable to 51% attacks. Even a moderate mining operation could overwhelm it. This is not a matter of advanced state-level adversaries. It is an economic fact. The fork chain's security budget is structurally inadequate.
Infrastructure Response Timeline
The good news is that infrastructure responds to forks faster than the public expects. Wallets, exchanges, and custody providers have developed replay protection tools over the course of many forks. Split scripts, dedicated wallet routing, and asset isolation mechanisms exist. They are not a new invention. They are a commodity.
From BCH in 2017 to BSV in 2018, infrastructure teams consistently delivered replay protection and asset segregation within hours to days. My confidence in this timeline is medium, but the historical evidence supports it. The risk window is finite.
The implication is operational, not structural. The danger is not a permanent threat. It is a short, concentrated window during which user behavior determines exposure. The market should plan for that window, not for the fork itself.
Core Insight II: Token Economics of a Negative-Sum Fork
Supply Mirroring
A hard fork that shares history creates a 1:1 mirror of all balances. Every Bitcoin holder receives an equivalent balance on the fork chain. This is not an airdrop in the marketing sense. It is a mechanical consequence of the shared history.
Bitcoin's total supply cap of 21 million is unaffected. The fork chain does not create new coins beyond the original supply schedule. It inherits the same monetary policy, the same halving schedule, and the same issuance curve. The two chains differ only in the rule that triggers the fork.
The token economics are therefore not about new supply. They are about demand fragmentation. A third-rate ledger with an identical supply schedule and no ecosystem has a fair value near zero.
Incentive Decay
The fork chain's economics are a negative feedback loop. Here is the sequence:
- Low hashrate leads to irregular block production.
- Irregular block production leads to poor transaction experience.
- Poor transaction experience leads to low user adoption.
- Low user adoption leads to low miner revenue.
- Low miner revenue leads to declining hashrate.
- Declining hashrate leads to further instability.
This is not a sustainable economy. It is a decaying orbit. The only scenario that breaks the loop is coordinated infrastructure support - all major exchanges listing the fork coin, all major wallets routing it, all major custodians storing it. That scenario requires a 2.6% support rate to generate a 95% infrastructure response. The probability is not zero, but it is not a probability I would model at any meaningful confidence.
Liquidity Analysis
The fork coin's liquidity will be extremely thin. Market-making depth will be minimal. Spreads will be wide. Slippage will be extreme. Even in the unlikely event that a major exchange lists the fork coin, the order book will not support institutional-sized transactions.
There is a second-order effect. Exchange distribution of fork coins to holders would incentivize users to sell. Those sales would create a temporary transaction flow on the fork chain. That transaction flow expands the replay attack surface. The more users transact, the more signatures are broadcast, and the more opportunities exist for replay.
My confidence that the fork coin's liquidity will be inadequate is high. My confidence that exchange distribution would amplify replay exposure is medium. Both point in the same direction: do not trade this coin.
The Airdrop Trap
The theoretical availability of fork coins creates a trap. The value of the fork coin is near zero. The cost of attempting to claim it is the risk of losing real Bitcoin. Expected value calculation:
- Value of fork coin: approximately zero.
- Value of real Bitcoin at risk: significant.
- Probability of replay loss: non-trivial if transacting.
This is the definition of a negative-sum game. The rational move is to decline the free money.
I will refer you to my 2022 experience. When the Terra-Luna collapse triggered a market-wide crash, I executed a pre-defined emergency risk management protocol. I advised clients to reduce leverage by 30% and move to stablecoins. The advice was not based on a prediction of the bottom. It was based on the structural reality that leverage amplifies downside. The same logic applies here. Not trading is the highest-return activity available during the fork window.
The broader token economic picture remains unchanged for the main chain. The 21 million cap is fixed. The issuance schedule is immutable. The fork is a noise event in the monetary base, not a supply event.
Core Insight III: Market Impact and Macro Liquidity
Event Classification and Pricing
The market treats BIP-110 as an event-driven risk, not a fundamental change. I agree. This is a risk alert, not a repricing of Bitcoin's investment thesis.
How much is priced in? A rough estimate: 30% to 50% of the scenario is already reflected, because developer discussions have been circulating for some time. Uncertainty about the actual fork formation suppresses the percentage. The historical volatility around fear-inducing events suggests a price deviation in the range of ±2% to 3%. The fork coin, if quoted, will exhibit far larger swings, but that is not a Bitcoin signal.
Historical Precedents
The 2017 Bitcoin Cash fork is the closest precedent. Before the split, arbitrage expectations pushed BTC higher. During the split, hashrate switching produced short-term volatility. After the split, the main chain absorbed the shock.
The 2016 Ethereum Classic fork was more chaotic at the beginning, but its long-term impact on Ethereum was minimal. Both precedents involved far higher miner support than BIP-110 currently enjoys. The expected market shock is correspondingly smaller.
During my 2024 ETF regulatory framework analysis, I collaborated with three major Shanghai banks to model the correlation between spot Bitcoin ETF flows and traditional market volatility. The study, which was cited by five major financial news outlets, quantified how ETF structures changed market depth. The key finding was that institutional flows behave differently from retail flows. They are slower, larger, and more sensitive to macro variables. They are not sensitive to a 2.6% fork proposal.
Liquidity Cycle Context
The macro context is the North Star. Bitcoin's price is increasingly a function of global dollar liquidity, real interest rates, and the dispersion of M2 across the financial system. I built this thesis during the 2020 liquidity stress test, when I correlated global M2 expansion with on-chain volume spikes.
In the current bull market, the dominant driver is liquidity expansion. A minority fork is a rounding error on that scale.
Let me put the numbers in perspective. A fork with 2.6% miner support represents a negligible fraction of the network's security budget. Even if the fork succeeded in capturing 10% of that negligible hashrate, the economic impact would be invisible against the daily volume of the global Bitcoin market. Institutional investors will not reprice a global reserve asset because of a technical dissent.
Arbitrary Risk Pricing
I want to make a broader point about how markets price tail risk. They do it badly.
I have studied the interest rate models used by Aave and Compound. The models are not derived from real market supply and demand. They are governance-approved approximations that only accidentally track utilization. The same flaw applies to fork risk pricing. The market extrapolates from prior fork events without accounting for structural differences.
The structural difference here is dramatic. BCH and ETC had meaningful miner support at launch. BIP-110 has 2.6%. The prior forks also had a clearer product narrative. This fork's narrative is a restriction. You cannot build a marketing campaign around "we will exclude data."
The market's mispricing creates opportunity only for the cautious. If you hold Bitcoin, the correct answer is to do nothing. If you are a market maker, the correct answer is to widen spreads and reduce inventory in the hours around the activation block. If you are a speculator, the correct answer is to observe, not participate.
The market's attention span is short. BCH, BSV, BTG, and a dozen minor forks failed to dislodge BTC. Attention will shift within 48 hours. The only scenario that would break the pattern is a confirmed first case of real BTC loss due to replay. A widely reported theft would reignite FUD and channelize fear. The probability is not zero. But it is conditional on user behavior, not on the fork itself.
Core Insight IV: Ecosystem and Regulatory Positioning
Miner Economics
Miners decide fork outcomes. The signaling data is unambiguous: 97.4% of miners are not signaling support. This is not an accident. It is an economic decision.
Bitcoin miners operate on narrow margins. Their revenue is generated by block rewards and transaction fees. A fork that reduces block space usage by excluding inscriptions would reduce transaction fee revenue from inscription-heavy blocks. That is not an attractive incentive. The miner's rational choice is to remain on the dominant chain.
The ~2.6% signaling group is likely a political gesture rather than a profit-maximizing strategy. In a fork scenario, that group would face immediate difficulty overestimation, unstable block production, and reduced transaction fee revenue. Their economics are worse on the fork chain.
The upstream signal is therefore clear. The main chain will retain the overwhelming share of hashrate. The fork chain, if it forms, will be a political artifact.
Infrastructure Burden
The downstream burden falls on exchanges, wallets, and custody providers. They must decide whether to support the fork coin. The historical default is conditional support: list the coin if there is enough market demand, but do not allocate engineering resources unless required.
There is a cost asymmetry. The engineering cost of replay protection is real but bounded. The legal cost of failing to protect users is higher. This asymmetry pushes infrastructure toward protective action, even for a fork with negligible support.
The result is a predictable sequence: exchanges announce monitoring, wallets publish warnings, and security firms issue guidance. The market yawns. The fork passes. The infrastructure team collects the lessons.
Regulatory Competition: Hong Kong vs Singapore
Regulators are not neutral observers. They are competitors.
Hong Kong's virtual asset licensing framework is often described as an embrace of innovation. I do not accept that description. Hong Kong's licensing regime is designed to displace Singapore as Asia's financial hub. Singapore was earlier in the game. Hong Kong is late. The licensing race is about jurisdiction capture, not technical innovation.
A fork event becomes a stress test of regulatory positioning. Exchanges licensed in Hong Kong will prioritize stability to avoid regulatory questions. Exchanges in Singapore will do the same. Neither regulator will seize on a minority fork as evidence of a need for new rules. But the event will be monitored for market disruption. Any first-major replay theft will become a data point in the global regulatory argument for tighter wallet oversight.
In my 2026 work on standardizing trust in AI-crypto economies, I developed a framework for "Proof-of-AI-Origin" using zero-knowledge proofs. The principle is that data integrity must be established before market participation. The same principle applies here: the market must establish replay protection before fork coin listing. Standardization is not a compliance burden. It is a risk-reduction tool.
Institutional Absence
Institutions are absent from this event. That is the most telling signal.
During my 2024 ETF analysis, I found that institutional flows respond to macro variables, regulatory clarity, and custody robustness. They do not respond to consensus proposals with 2.6% support. No allocation committee will reconsider Bitcoin because of BIP-110.
The institutional absence is, in itself, a calibration. It tells us the market is pricing this risk as an operational nuisance, not a structural threat. The implication for retail participants is clear: there is no edge in being early to a fork coin. The edge belongs to those who avoid the replay window.
Developer and User Signal Gaps
The available information set does not include GitHub activity, contributor counts, or commit frequency. The developer signal is insufficient for quantitative assessment. The user signal is also absent. No DAU/MAU data, retention curves, or new-user statistics are available.
I will not fabricate metrics. I will state the assessment as N/A. In the absence of data, prudence dictates caution.
Contrarian Angle: The Fork Is a Diagnostic, Not a Threat
The market treats a Bitcoin fork as a danger. I think the opposite. A minority fork is a diagnostic. It is a controlled experiment that reveals the settlement layer's robustness.
A fork with 2.6% support does not threaten the main chain. It demonstrates the difficulty of challenging a dominant consensus. The more forks are attempted, the more the main chain's network effect is proven. This is the decoupling thesis: the macro asset is insulated from protocol-level noise.
The real threat is not the fork. It is the user's own hand. The moment a user reaches for a fork coin, they expose themselves to replay risk. Idle keys are safe. Curious fingers are not.
I also want to highlight the rehearsal dynamic. Kevin Loaec's warning is not an emergency broadcast. It is a pre-enactment of a public safety event. The warning itself reduces the probability of mass casualty because it suppresses emotional trading. The market should be grateful for such warnings, even as it ignores them.
At the macro level, Bitcoin's price is determined by the liquidity cycle, the institutional adoption curve, and the dollar system. Not by a BIP number, disputed or otherwise. The fork is an incident report. It is not the main story.
The main story is the same as it was in 2017, 2020, and 2022. Global dollar liquidity expands and contracts. Bitcoin responds to that rhythm. A 2.6% fork is noise within that rhythm.
There is one more contrarian observation. The market should actually welcome a fork attempt. It is a stress test that incurs minimal cost and produces maximum information. The data gained from observing the replay window, the infrastructure response, and the miner migration will calibrate future risk models. This is how the settlement layer proves itself.
Scenario Matrix
I present four scenarios with indicative probabilities. These are not rigorous statistical estimates. They are calibrated judgment based on the available information.
Scenario 1: No fork forms. Miner support stays below any meaningful threshold. Probability: 85%. Market impact: negligible.
Scenario 2: A fork forms but is ignored by infrastructure. No major exchange lists the fork coin. Replay risk is low because no one transacts. Probability: 10%. Market impact: minor, confined to derivatives.
Scenario 3: A fork forms and is listed by a minor exchange. A small number of users attempt to sell. A replay attack occurs on a handful of transactions. Headlines amplify the event. Probability: 4%. Market impact: short-term volatility around 2-3%.
Scenario 4: A fork forms and is listed by a major exchange. Significant user participation. Multiple replay losses. Regulatory statements issued. Probability: 1%. Market impact: possible 5% drawdown followed by recovery.
In all scenarios, the main chain survives. The supply cap remains. The global consensus asset narrative remains.
Preparedness Protocol
This is the prescriptive section. If you are reading this report before block height 961,632, follow these steps.
Step 1: Inventory your keys. Know which wallets hold Bitcoin. If you have not moved coins in the last 90 days, leave them alone.
Step 2: Freeze transaction activity during the window. Do not send Bitcoin. Do not receive Bitcoin unless the sender has confirmed the fork status. Do not use DEXs that might route through unstable bridges.
Step 3: Do not claim the fork coin. The expected value is zero. The replay risk is real. If an exchange offers a credit, ignore it.
Step 4: Monitor official infrastructure announcements. Exchanges will issue clear instructions if replay protection is deployed. Wait for confirmation from at least two independent sources before any action.
Step 5: After the window closes, verify that replay protection exists. If both chains are still active and you must transact, use a wallet that implements chain-specific signing.
This protocol is deliberately boring. It is designed to prevent action, not generate it. The most dangerous behavior during a replay window is curiosity.
Takeaway
The fork window is hours, not weeks. The sequence is binary. If you move nothing, you survive. If you move once, you risk everything.
Do not claim the fork coin. Do not sell the fork coin. Do not enter your seed phrase into a split tool. The expected value of the fork coin is zero. The expected cost of a replay loss is real.
Your capital is your principal. The bull market creates the illusion that every technical event is a buying opportunity. This one is not. It is an operational hazard.
Exit strategies are written in ice, not in hope. The same applies to non-action during the fork window. The disciplined answer is the boring answer: do nothing.
When the block passes and the replay window closes, the market will remember this as an experiment. The experiment will confirm that Bitcoin's settlement layer is more robust than its critics believe. The macro cycle will continue. The institutional flow will continue. And your portfolio, if it is still intact, will continue with them.
The next real signal will not be a BIP number. It will be the next expansion or contraction of global dollar liquidity. That is where the macro watcher's attention belongs.