Particle.news
Download on the App Store

BIP-110 Enforcing Fork Stalls After Mining Just Two Blocks

The split has left a minority chain far behind the main Bitcoin network and exposed slow difficulty mechanics and replay risks that miners and services must manage.

Overview

  • The proposal entered mandatory signaling at block 961,632 and enforcing nodes began rejecting non‑signaling blocks, producing a separate chain that mined only two blocks and halted at block 961,633.
  • The main Bitcoin chain continued to advance, leaving the BIP-110 branch dozens to more than 100 blocks behind and preventing the fork from completing a full 2,016-block period needed for a difficulty reset.
  • A pseudonymous group called Roughnecks mined the two enforcing blocks using Ocean’s DATUM endpoint, which showed roughly 257 PH/s, and Michael Saylor estimates the fork controls about 0.15% of total hashpower.
  • At the fork’s current mining rate it would take on the order of decades to reach the first difficulty adjustment, and BIP-110 contains no built-in replay protection, creating custody and transaction risks for users and exchanges.
  • Support was weak before enforcement, with only 51 of 2,016 prior blocks signaling (about 2.5%) and essentially no miner signaling since mandatory mode began, underscoring that protocol changes need broad miner and ecosystem backing to be effective.