Bitcoin’s BIP-110 experiment produced a short-lived minority chain this weekend: nodes enforcing the Reduced Data Temporary Softfork began rejecting non-signaling blocks at height 961,632, mined two blocks of their own, then effectively stopped while the main chain kept producing blocks as usual.
What happened on-chain
According to CoinDesk and Crypto Briefing, the mandatory signaling window opened when the network reached block 961,632 (around August 7–8, 2026, depending on the clock you use). Software enforcing BIP-110 treats blocks that do not set the required version bit as invalid. When the first such block arrived, those nodes peeled off onto their own tip.
That tip did not go far. The breakaway chain produced blocks 961,632 and 961,633, then stalled. CoinDesk’s early read put the minority tip still at 961,633 while the main chain had already advanced by about 48 blocks; later coverage in the same news cycle described the gap widening further as ordinary mining continued on the dominant proof-of-work chain. In plain terms: almost nobody was mining the BIP-110 branch, so its block times collapsed under the difficulty it inherited from the parent chain.
CoinDesk’s earlier report put miner signaling for BIP-110 near 2.5% as the window opened, far below the 55% threshold the proposal needs to lock in during a 2,016-block period. Crypto Briefing described recent signaling fluctuating roughly between 0.3% and 2.6%, with no major public mining-pool endorsement. Without hash rate, a minority chain does not “win” a culture war; it just sits still.
What BIP-110 was trying to do
BIP-110 (also called RDTS, and sometimes discussed under the older BIP-444 label) is a temporary consensus change: for about one year after activation (~52,416 blocks), new transactions would face tighter limits on how much arbitrary data they can carry. The project’s own explainer frames the goal as reducing non-monetary data on Bitcoin (especially patterns associated with inscriptions and similar embedding tricks) while leaving known monetary uses intact. Pre-activation UTXOs are described as permanently exempt from the new rules.
The activation path is a user-activated soft fork (UASF) style design: early lock-in if miners signal 55% of blocks in a retarget window, otherwise mandatory signaling starting at 961,632, with the data rules themselves intended only after a later lock-in and activation height (the public materials point at activation around 965,664 if lock-in succeeds). That is the opposite of waiting for near-unanimous miner consent before changing the rules. It is also why the weekend looked like a chain split even though miner support never approached the bar.
Primary software carrying enforcement has been Bitcoin Knots builds and related node packages promoted on bip110.org, not a coordinated upgrade of the entire Bitcoin Core user base. If your node was not running those rules, you stayed on the chain everyone still calls Bitcoin. If it was, and you did not turn the rules off, you followed the two-block dead end until you resynced.
Why the minority chain had no air
Two constraints stacked against the fork:
- Hash rate. Soft forks with tiny miner support do not produce a parallel economy. They produce empty mempools and multi-hour block gaps. That is what the monitors showed after the split.
- Economic infrastructure. Unlike the 2017 Bitcoin Cash split, there was no ready exchange market, no ticker liquidity, and no clear incentive for large miners to jump. CoinDesk also flagged replay-style risk for anyone trying to move “fork coins” while spending the same UTXOs on the main chain, a classic minority-fork footgun when wallets do not cleanly separate chains.
Critics of BIP-110 had already argued the proposal was a form of content policy dressed as consensus, and that paid block space should not be rewritten by a temporary rule set. Strategy executive chairman Michael Saylor was among the public opponents; Crypto Briefing notes he treated the effort as already failed and any fork as economically irrelevant. Supporters still cast the limits as defending Bitcoin as money rather than a data dump. The on-chain scoreboard after mandatory signaling began was unambiguous: the enforcing tip froze, the main chain did not.
What users and operators should actually do
For ordinary holders and self-custody setups, this weekend was noise unless you deliberately ran BIP-110 enforcement:
- Standard Bitcoin Core / non-enforcing wallets and nodes: no rule change. Your chain tip is the one with continuous blocks and the overwhelming hash rate.
- Knots / BIP-110-enforcing nodes: if you are stuck two blocks behind reality, disable the enforcement rules and resync to the main chain per the project’s own chain-switch guidance and your package docs. Do not send value you care about on a tip that is not producing blocks.
- Exchanges and custodians: major venues reported normal operations through the episode; treat any “BIP-110 coin” claim as unverified unless a named venue lists and clears it, and even then treat it as a separate, illiquid asset, not a free airdrop of real BTC.
None of this is investment advice. It is operational hygiene: confirm which software you run, which tip it follows, and that your backups and seed phrases are offline where you left them.
Takeaway
BIP-110’s mandatory signaling window opened with roughly 2.5% miner support. Enforcing nodes split at block 961,632, produced two blocks, and stalled. The main Bitcoin chain kept moving. The policy fight over arbitrary data on Bitcoin is not over. Temporary soft-fork designs will resurface whenever fees, inscriptions, or node resource costs flare, but this particular UASF attempt did not move the economic majority.
If you run your own node, know which rules binary you installed. If you only hold keys in a normal wallet, verify your balances on a block explorer you trust and keep your keys offline. Consensus changes that lack hash rate and market support end as footnotes, not new bitcoins.
