BIP-110 enforcing branch stalls after two blocks

What happened

The supplied record says the BIP-110 enforcing branch mined two blocks following a failed soft fork, then stalled. It characterizes the fork as effectively dead rather than presenting it as an active competing branch.

The record attributes the stall to roughly 2.53% hashpower on the enforcing branch. At that reported level, it says the branch was roughly 350 days from a difficulty adjustment.

Why it matters

This is a concrete reported outcome in a Bitcoin mining and chain-split dispute: enforcement did not gain enough support to continue producing blocks at a workable pace. The episode may serve as a reference point for how miner participation can determine whether an enforcing branch remains viable.

The record also notes a silent miner boycott. One miner reportedly rejected the rule despite mining through a pool described as supportive, underscoring that pool affiliation alone may not show support for a proposed rule.

What to watch

The next useful receipt is whether the enforcing branch resumes block production or gains materially more hashpower. The supplied record does not provide later blocks, additional participation data, or a formal resolution beyond the reported stall.