BIP-110 revolt tests BTC governance

TLDR

BIP-110, a controversial Bitcoin (BTC) soft fork proposal to restrict non-financial data in transactions, is now highlighting how Bitcoin governance handles disagreement and potential forks.

1. BIP-110 would temporarily limit Ordinals-style data for one year, but is pushing ahead with mandatory enforcement despite miner support stuck around 23 percent.
2. The clash between developers, a small set of mining pools, and large holders like Michael Saylor shows Bitcoin governance as a multi-stakeholder negotiation, not simple miner voting.
3. The main near-term risk is a small minority BIP-110 chain; watch mining pool signaling, exchange support, and node adoption to see whether this becomes a niche experiment or a messy split.

Deep Dive

1. BIP-110s Rules And Revolt

BIP-110, formally the Reduced Data Temporary Softfork, would cap certain data fields in Bitcoin transactions for about one year, targeting Ordinals and token protocols while leaving normal payments and Lightning largely unaffected. Supporters, concentrated around Bitcoin Knots and pools like OCEAN/DATUM, argue this slows blockchain bloat and lowers node costs, refocusing Bitcoin on payments. Critics say it asks the protocol to judge what counts as spam, breaking Bitcoins neutrality.

The revolt angle comes from BIP-110 enforcing nodes planning to start rejecting non-signaling blocks at block 961,632 despite miner signaling sitting near 23 percent, far below the 55 percent threshold for voluntary lock-in, according to multiple tallies and analysis by Michael Saylor. That creates an intentional minority rule-set that can branch off into a side chain with slower block production and limited infrastructure if major miners and exchanges stay on the main chain.

2. How Bitcoin Governance Is Being Tested

This episode shows Bitcoin governance as a balance among developers, node operators, miners, exchanges, and large holders, rather than a formal on-chain vote. BIP-110 lives in Bitcoin Knots, not Bitcoin Core, so its reach depends on how many operators choose that client. Large pools like Foundry, AntPool, F2Pool, and ViaBTC have refused to signal, while EMCD and Foundry are polling their miners before deciding how to vote.

On the big holder side, Strategy executive chairman Michael Saylor, whose firm controls a large BTC treasury, has urged BIP-110 supporters to stand down, arguing that intent-based filtering sets a dangerous precedent and risks an unnecessary split. Major exchanges and custodians have so far given little explicit guidance on whether they would recognize a BIP-110 asset, a critical missing piece for investors.

3. Fork Scenarios And What To Watch

Most sources expect BIP-110 to fail as a main-chain upgrade and, at most, create a minority chain if enforcing nodes do not back down. Key checkpoints are the mandatory signaling start around block 961,632 and subsequent lock-in blocks; if signaling remains tiny and major pools ignore the rules, BIP-110 blocks will form a side chain with limited hashpower and support.

For BTC users, the practical risks are short-term operational disruption (some smaller services plan to pause transfers during the fork window) and confusion about any forked coins that may appear. The most important signals to watch are: 1) whether large pools change stance, 2) whether major exchanges announce support or non-support for a BIP-110 asset, and 3) whether Knots/BIP-110 node counts grow meaningfully.

Conclusion

BIP-110 is unlikely to rewrite Bitcoins main rules, but it is forcing the ecosystem to confront who actually decides protocol changes in practice. The combination of low miner support, strong opposition from influential holders, and silence from major exchanges makes a dominant BIP-110 chain improbable, yet the willingness of a small group to enforce new rules anyway is an important governance signal. The outcome will clarify how far minority node operators can push before the wider Bitcoin market simply treats their fork as a side experiment.