The BIP-110 branch of Bitcoin has stalled after producing just two blocks. The enforcing fork is now stuck at the network's full mining difficulty, and while mandatory signaling is proceeding, it's drawing little hashpower support. That leaves the branch in a precarious spot — unable to advance and with few miners visibly committed to it.
How the fork got stuck
BIP-110 is a Bitcoin improvement proposal, and this branch is meant to enforce it. But after two blocks, no third block has been found. The difficulty hasn't adjusted downward — it's sitting at Bitcoin's full mining difficulty, which is a heavy lift for a branch that clearly isn't attracting the network's main hashpower.
In practice, that means the branch is competing for blocks on the same difficulty curve as the main chain, but without the same mining muscle behind it. Two blocks might be a start, but a chain that can't clear a third block isn't really moving.
The signaling picture
Mandatory signaling is active on the branch — that part is working as designed. But the signal is coming from a very small slice of the network. The facts don't give a percentage, but they do say support is thin. When mandatory signaling proceeds without meaningful hashpower behind it, the signal is mostly symbolic.
It's not a vote of confidence. Miners who aren't signaling are essentially ignoring the fork, and that's a problem for any branch that needs to secure itself against reorgs or just keep producing blocks.
The immediate question is whether the branch can find a third block at all. If it can't, it will remain stuck at the same height, and the enforcing fork will have effectively frozen. If it does find one, the same problem repeats — each block is a slog at full difficulty.
There's no timeline in the facts for when the difficulty might adjust or whether the branch's backers plan to recalibrate. For now, the branch is in limbo, and the lack of hashpower support doesn't point to a quick resolution.
