The BIP-110 Countdown at Block 961,632: A Trader Reads the Signaling Tape

The signal vanished before it ever arrived. Across 392 blocks, BIP-110 attracted exactly eight new mining signals. The support rate dropped from 2.70% to 2.60% while activation approached. Not momentum. A leak bleeding out in public. The window closes in under 290 blocks. Support is collapsing toward the deadline, not building into it. Three people describe the same event at block 961,632 and reach opposite conclusions. Dathon Ohm, BIP-110's pseudonymous author, tells users to abandon Bitcoin Core because it becomes "insecure" once mandatory signaling begins. Michael Saylor tells the proposal's backers to stand down. Luke Dashjr, Bitcoin Knots maintainer, says the outcome is already settled. Three verdicts. One mechanism. Only one reads the tape correctly. Chaos is opportunity. Compile the data. BIP-110 is a temporary soft fork capping the data payload a single Bitcoin transaction can carry. It ships in Bitcoin Knots, not Bitcoin Core. That distribution detail matters more than the policy debate. Ohm's warning is blunt. When mandatory signaling begins at block 961,632, miners must set versionbit 4 in the block header. BIP-110 nodes discard blocks without the flag. Miners pulling templates from Core, he argues, will produce invalid blocks on a chain that keeps getting wiped out. Block rewards evaporate. Node operators run blind. The project's own website never calls Core insecure. It frames BIP-110 as a curb on arbitrary data — the blockspace spam argument. No mention of "critical vulnerabilities," despite Ohm's claim this fork patches them. The marketing page reads like a policy initiative. The author's timeline reads like a security emergency. One narrative is false. I've audited protocols where public copy diverges from the threat model. The code doesn't lie. The narrative does. The mechanism is elementary. Versionbit 4. A flag in the block header. Set it and you signal readiness. Ignore it and BIP-110 nodes reject your block. Lock-in requires 1,109 signaling blocks. The math turns hostile here. Read the numbers from BIP-110's own monitor. At block 961,022 on August 4: 38 signaling blocks of roughly 1,407 — 2.70%. By block 961,421: 47 of 1,806 — 2.60%. Eight new signals across 392 blocks. The period rate slipped rather than climbed. No completed two-week stretch since December has finished above 1.29%. Now the constraint. Early lock-in needs 1,109 signaling blocks. With 217 blocks left in the window, the maximum reachable total is 263. Lock-in: 1,109. Maximum possible: 263. That gap is not a margin. It is a gulf. Translate into trader terms. This is a governance vote where turnout collapsed and the deadline is hours away. The author screams "THIS IS NOT A DRILL" while his own tape shows the opposite. When the messenger gets louder than the metric, the trade sits on the other side. Dashjr insists the outcome is settled. Refusing miners lose block rewards, he says. Their invalid blocks mislead only nodes that haven't updated. Shipping a Knots release without BIP-110 changes nothing. No material opposition, he claims. That phrase carries weight. "No material opposition" — measured against what? The public monitor is opposition. The slide from 2.70% to 2.60% is opposition. The absence of a single two-week stretch above 1.29% since December is opposition. When your own metric contradicts your own claim, the market prices the contradiction. Saylor reads the same mechanism and reverses the verdict. At block 961,632, BIP-110 nodes reject non-signaling blocks. Unless major miners flip, Bitcoin continues normally while BIP-110 stalls or forks into irrelevance. Backers should stand down. Adam Back flags split risk over the low threshold — a "stupid idea" that "completely fails at technical consensus." The SegWit contrast is instructive: it had technical and ecosystem consensus before activation. This has neither. Voluntary activation is dead. BeInCrypto confirmed it. With about a day and a half left, the question is binary: miners capitulate, or BIP-110 nodes end up mining alone on a chain of their own design. Map the mechanics. A BIP-110 node treats non-signaling blocks as invalid. It builds only on versionbit-4 blocks. A Core node accepts both. At 2.6% hashrate, the BIP-110 minority occasionally extends its own chain. Then the majority finds the next block — usually several — and the minority chain reorgs. Confirmations vanish. Deposits roll back. That is the damage vector. Exchanges that confirmed deposits inside the reorg window face double-spend exposure. That risk alone forces cautious behavior. I ran this scenario during the SegWit activation fights of 2017. The pattern repeats: a minority client enforces a rule the majority rejects, then tries to enforce it by separation. The difference is support. SegWit had real hashrate behind it. BIP-110 has a rounding error. The retail playbook says "split" equals free assets. Chain splits print tokens on both sides. This is not 2017. This is not Bitcoin Cash. A chain that cannot cross 3% signaling support has no claim on the Bitcoin name, the ticker, or exchange liquidity. If the Knots chain materializes, it does not compete. It exists for one purpose: a narrative weapon. A 2.6% fork with a loud author claims Bitcoin legitimacy for its own upgrade agenda. It forces Core to respond, burns engineering hours, drains narrative capital. Stalling into irrelevance costs the backers nothing. Splitting hands them an asset they control outright. Either way, the push succeeds — as long as everyone keeps talking about it. Miners read the incentive. No hashrate majority. No economic majority. No exchange support. No listing. No wallet integration. The fork dies in the gap between announcement and relevance. Just a versionbit and a countdown. Narrative broken. Shorting the dip. The actual danger is not the fork. It is the confusion window around block 961,632. Exchange announcements. Withdrawal pauses. Nodes feeding invalid blocks to the unprepared. Liquidity thins exactly when uncertainty peaks. Funding whipsaws as leverage picks the wrong side. The first 200 blocks after the transition point are a desert. That is where capital gets destroyed — not by the fork, but by the chaos around it. Block 961,632 looks binary. It isn't. The trade lives in the aftermath — reorg depth, exchange confirmation times, node fragmentation. Watch hashrate distribution in the first stretch after transition. Watch withdrawal confirmations stretch. Watch the reorg depth. Liquidity dries up. Watch the spreads. If miners capitulate, BIP-110 locks in and the spam war shifts. If they hold, the Knots chain orphans itself. Either way, capital relocates. Position for the confusion, not the block.