Strategy founder Michael Saylor published a long post on July 18 listing 100 reasons to oppose BIP 110. According to Odaily, he said the proposal would use Bitcoin consensus rules to restrict a category of controversial but currently valid transactions and would amount to governance intervention over use cases.
BIP 110, formally called "Reduced Data Temporary Softfork," was listed as complete on GitHub on June 25, 2026. It is designed to run for about one year and adds seven consensus restrictions, including an 83-byte limit on OP_RETURN outputs, 256-byte caps on some payload and witness items, and limits on certain Taproot-related structures.
Saylor said BIP 110 uses a 55% miner signaling threshold, below the 95% threshold in the standard BIP 9 process, and removes the usual timeout and FAILED status. He argued that using a lower threshold for controversial rule changes would raise the chance of a chain split and could affect miner fee revenue and long-term network security.
He also said Bitcoin’s existing relay and mining strategy tools already allow node operators and miners to limit unwanted transaction types without changing network-wide consensus rules. Saylor added that the Bitcoin base layer should remain conservative and opposed using consensus soft forks to regulate controversial use cases.