BIP-110 reaches activation with under 3% of miners on board, and the forks could be the real story

At block 961,632, mined on Friday 7 August 2026, the BIP-110 proposal began mandatory signaling on bitcoin's mainnet. The headline that followed is not the usual industry choreography. Fewer than 3% of miners had publicly committed to the change before the tap turned on, Coindesk reported, and the proposal will continue to march toward its activation window regardless.

That mismatch is the story. A user-activated soft fork (UASF) was always designed to ignore miner sentiment and let node operators dictate consensus. BIP-110, a proposal to limit the data that can travel inside bitcoin transactions, has been treated as a stress test of that mechanism: if the nodes can sustain a change while miners refuse to enforce it, the rule book has been rewritten in practice. Whether that is a feature or a hazard depends on which camp the reader listens to.

The numbers behind a near-empty endorsement

The headline figure is the gap between enforcement and consent. Coindesk's 7 August frame story reported that miner support sat at less than 3% as of the deployment milestone and that "influential commentators have also voiced their opposition." Cointelegraph's coverage of the same activation window framed the situation as a test of "whether enforcing nodes can sustain the change amid limited miner signaling and discussion of a hard-fork fallback."

Behind those numbers is a deeper question about what bitcoin governance actually is. Mining pools signal intent by embedding bits in the blocks they produce. Full-node operators enforce consensus by rejecting blocks that violate the new rules once a fork has activated. BIP-110's designers built a mechanism in which the second group can act without permission from the first. The proposal's persistence, Coindesk observed in a 6 August explainer, "has attracted only a sliver of miner support, yet its user-activated design means the proposal continues toward its activation date and (most likely) beyond."

What the developer warning actually says

On 8 August, Coindesk carried a developer caution that has been less prominent in coverage of the activation itself. According to the report, holders "risk losing real BTC if they sell coins from BIP-110 fork," because a minority chain could allow signed transactions to be replayed on the surviving network. In plain terms: if a minority chain emerges from the activation window, a sale signed against the forked coin could also be valid on the main chain. The developer quoted in the article argued that "doing nothing is the safest move until the chains can be separated."

The risk is not new to bitcoin's history. The 2017 split that produced bitcoin cash is the clearest cited precedent for replay friction between two live chains. Coindesk's reporting on the developer warning frames this case as comparable, with the key difference that the BIP-110 chain would arrive with far less miner backing than BCH did and is therefore likelier to be a short-lived artefact than a lasting alternative. That cuts both ways: a quick death for the minority chain leaves little surface to replay against, but it also means the experiment compresses into a window where users may not have time to separate their coins.

The price tape, which has its own mind

While governance drama has played out, the spot market has behaved as if it were a different asset. Bitcoin tagged an August high above $65,300 on 7 August, Cointelegraph reported, after a soft US nonfarm payrolls print cooled expectations of further Federal Reserve tightening. Brent crude climbed the same morning on stalled Strait of Hormuz talks, Coindesk noted in its day-ahead live coverage, reviving the inflation worry that has capped the asset all summer.

By Friday afternoon, the bid had cooled. Investing.com's live coverage put bitcoin "stalling at $65,156 resistance," with the Average Directional Index flashing a warning that the move could be a bull trap. A separate Investing.com piece on 8 August placed the price "toward $65,000" under a different headline: "fresh security risks hit infrastructure." The activation event and the price tape have, so far, decoupled. Whether the replay risk, if it materialises, drags the spot price into the governance debate is the open question.

What to watch over the next 72 hours

Three things matter in the immediate window. First, hash rate on the BIP-110 chain. If pools begin to mine on the new rules, the fork consolidates; if they continue to ignore it, the chain stalls. Second, exchange posture. The cited reporting does not specify whether major venues have declared how they will credit both chains or treat one as bitcoin proper; their decisions will determine who actually has to act and who can simply wait. Third, the macro tape. The 7 August US payrolls print has already cleared, and the next inflation release will set the floor under all of this in a different room from the protocol debate.

The structural read is straightforward. UASFs have always been bitcoin's pressure valve for governance deadlock, and BIP-110 is the most aggressive use of that valve since the 2017 SegWit episode. The experiment will tell node operators something about their actual leverage. It will tell miners something about whether ignoring a soft fork is costless. It will tell holders something about whether doing nothing is, as the developer argued, the only safe move in a contested fork.

Desk note: This publication led with the activation block and the developer warning rather than the macro price print, because the replay risk is the higher-consequence story and has received the least attention in the cited coverage.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://cointelegraph.com/news/bitcoin-bip-110-mandatory-signaling
• https://www.coindesk.com/tech/2026/08/07/frame-bitcoin-s-bip-110-enters-mandatory-signaling-with-less-than-3-miner-support
• https://www.coindesk.com/tech/2026/08/08/bitcoin-holders-risk-losing-real-btc-if-they-sell-coins-from-bip-110-fork-says-developer
• https://www.coindesk.com/tech/2026/08/06/why-bitcoin-s-bip-110-refuses-to-die-despite-near-zero-miner-support
• https://www.investing.com/news/cryptocurrency-news/bitcoin-rises-toward-65000-as-fresh-security-risks-hit-infrastructure-4847628
• https://www.investing.com/news/cryptocurrency-news/bitcoin-tests-62k-support-with-breakout-looming-live-levels-93CH-4829888
• https://cointelegraph.com/markets/bitcoin-price-tags-653k-august-high-as-low-us-jobs-numbers-cool-fed-rate-bets
• https://www.coindesk.com/markets/2026/08/07/live-updates-bitcoin-flat-at-usd64-300-before-us-jobs-report-with-oil-back-as-a-headwind