Woofun AI reports that Michael Saylor published a detailed critique on July 18, outlining 100 reasons to reject BIP 110. He argues the proposal imposes governance intervention by restricting valid transactions through consensus rules.

BIP 110, full name "Reduced Data Temporary Softfork," was marked as Complete on Github on June 25, 2026. The proposal introduces seven new consensus restrictions, including an 83-byte limit on OP_RETURN outputs, a 256-byte cap on certain payloads and witness items, as well as restrictions on some Taproot-related structures. Michael Saylor pointed out that BIP 110 adopts a 55% miner signaling threshold, lower than the 95% threshold in the standard BIP 9 process, and removes the regular timeout and FAILED status.

He believes that using a lower threshold for controversial rule changes increases the probability of a chain split and could potentially affect miner fee revenue and long-term network security. He argued that existing Bitcoin relay and mining strategy tools already allow node operators and miners to restrict unwanted transaction types without the need to change the network's consensus rules. Michael Saylor also stated that Bitcoin's base layer should remain conservative and opposed the use of consensus soft forks to regulate controversial use cases.