Saylor Tells BIP-110 Backers to Stand Down Before the Fork

Why Saylor is pushing BIP-110 backers to pause

Saylor appears to be arguing that blocking BIP-110 now matters more than any single fork battle over Bitcoin's rules. The immediate setup is straightforward: BIP-110 is designed around a one-year deployment, and the proposal is already generating a serious governance fight before it has broad backing. For now, the debate is about whether Bitcoin should use consensus rules to limit data embedding at all.

That is why Saylor telling backers to stand down matters. He is not making a purely technical objection. He has argued that BIP-110 would turn a spam dispute into a broader precedent, and that Bitcoin should be more careful about invalidating currently valid, fee-paying transactions.

What BIP-110 would change in Bitcoin consensus

BIP-110 is a soft fork that would add seven consensus restrictions during a temporary deployment window. Its backers say the change would correct distorted incentives caused by standardizing support for arbitrary data and help refocus Bitcoin on payments rather than data storage.

Critics focus on the risks. The proposal would temporarily restrict several methods used to embed arbitrary data in Bitcoin transactions, and opponents argue that it could reject valid transactions and split the network. That is the core divide: supporters see spam relief and cleaner node economics, while skeptics see a contested rule change that could damage confidence in Bitcoin's consensus process.

Why the activation debate matters before miners signal

The evidence provided does not confirm a 55% miner-signaling threshold, nor does it show current miner support at 1%. What the sources do support is simpler but still important: BIP-110 is controversial, its activation would rely on miner signaling, and the debate has already drawn sharp reactions from miners, developers, companies, and users.