TechFlow reports that on July 19, Michael Saylor published an article titled "110 Reasons BIP 110 Is a Bad Idea," opposing the Bitcoin proposal BIP 110. He stated that BIP 110 will add 7 new consensus constraints via a soft fork within approximately 1 year, including restrictions on scriptPubKey, OP_RETURN, witness data, Taproot annex, control blocks, and certain Tapscript usage, and will adopt a modified BIP 9 deployment mechanism.
Saylor believes that the proposal does not fix clear consensus failures such as inflation, double-spending, or signature verification, but instead attempts to handle disputes over the usage of valid paying transactions at the consensus layer, which may compress future upgrade space, increase activation coordination risks, and set a precedent for excluding specific uses via consensus rules.
