Strategy founder Michael Saylor said on July 18 that he opposes BIP 110, publishing a long post that laid out 100 reasons against the proposal. He argued that the measure would use Bitcoin consensus rules to restrict a category of transactions that are currently valid, though controversial, and described that approach as governance intervention over use cases.
BIP 110, formally titled “Reduced Data Temporary Softfork,” was marked Complete on GitHub on June 25, 2026. The proposal is designed to run for about one year and would add seven consensus restrictions, including an 83-byte limit for OP_RETURN outputs, a 256-byte cap for certain payloads and witness items, and restrictions on some Taproot-related structures.
Saylor also criticized the activation design. He said BIP 110 uses a 55% miner signaling threshold, below the 95% threshold in the standard BIP 9 process, while removing the usual timeout and FAILED state. In his view, applying a lower threshold to a disputed rule change could raise the risk of a chain split and affect miner fee revenue as well as long-term network security.
Strategy founder Michael Saylor said on July 18 that he opposes BIP 110, publishing a long post with 100 reasons against the proposed Bitcoin soft fork.
Saylor said the proposal would use Bitcoin consensus rules to restrict a class of transactions that remains valid today, even if those transactions are disputed. He described that as governance intervention over use cases.
BIP 110 marked Complete on GitHub
BIP 110, formally titled “Reduced Data Temporary Softfork,” was listed as Complete on GitHub on June 25, 2026. The proposal is intended to run for about one year and would introduce seven new consensus restrictions.
Those restrictions include an 83-byte limit on OP_RETURN outputs, a 256-byte cap on certain payloads and witness items, and limits on some Taproot-related structures.
Saylor objects to the activation threshold
Saylor said BIP 110 uses a 55% miner signaling threshold, below the 95% threshold in the standard BIP 9 process. He also said the proposal removes the usual timeout and FAILED state.
According to Saylor, using a lower threshold for a disputed rule change could increase the probability of a chain split. He added that it could also affect miner fee revenue and Bitcoin’s long-term network security.
Calls for a conservative base layer
Saylor said Bitcoin’s existing relay and mining policy tools already allow node operators and miners to restrict transaction types they do not want, without changing consensus rules across the network.
He also said the Bitcoin base layer should remain conservative and opposed using a consensus soft fork to regulate disputed use cases.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
