One of the most heated debates in Bitcoin's history has erupted around BIP-110. The proposal to temporarily restrict the recording of non-financial data—images, text, and other junk—into the blockchain seems, at first glance, like a noble fight against spam. However, heavyweights such as Michael Saylor and Adam Back, who cannot be suspected of sympathizing with network cloggers, have opposed it. Let's figure out what is actually wrong with this initiative.
Seven restrictions for one year
BIP-110, developed under the pseudonym Dathon Ohm, introduces seven restrictions lasting approximately one year. Among them are a limit on the size of new addresses, a ban on using the Taproot auxiliary field, and the refusal to process certain opcodes. It is important to note that these rules do not affect coins at already existing addresses, which removes the main fear of possible confiscation of funds. However, there is a nuance: transactions prepared in advance under the old rules may become invalid during the soft fork's activation period.
The key element of the dispute is not the restrictions themselves, but the mechanism for their activation. BIP-110 uses a modified version of BIP 9, where the miner support threshold is reduced from 95% to 55%, and a "FAILED" state for the proposal is not provided. This means that even with minimal support from miners, the soft fork can be forcibly activated by node operators. This approach, borrowed from the 2017 UASF, sparks fierce controversy.
Votes diverge: miners against, nodes in favor
Support for BIP-110 from miners has been negligible. Over eight months, the support signal has not exceeded one and a half percent of new blocks. The largest mining pools, such as Foundry, AntPool, and F2Pool, are either silent or openly opposed. The situation with nodes is the opposite: the share of Bitcoin Knots, ready to apply the new rules, has grown noticeably, reaching 8-20% of all publicly accessible nodes. However, as developer Jameson Lopp rightly notes, these numbers can easily be inflated via Tor.
This divergence is the key point. Miners, who have invested billions in equipment, vote against it with their hashrate. Node operators, which can be run almost for free, vote in favor. So who ultimately determines the rules of the game?
Opponents: not for spam, but for neutrality
Critics of BIP-110 are not defending spam. Their objections are to the method. Adam Back called the initiative a "lynch mob" that damages Bitcoin's reputation as a store of value. Michael Saylor, in his 110-point essay, put forward the most compelling argument: "The rules will run for a year and be lifted, but the precedent for their adoption will remain forever." He warns that BIP-110 is "iatrogenesis"—harm caused by the treatment itself.
Analyst Axel Adler Jr. put it this way: changing the consensus is only worth it when there is an objective technical necessity. BIP-110 in its current form "undermines the network's neutrality more than the problem itself requires." And this, in my opinion, is the main takeaway: Bitcoin is valuable precisely for its immutability and neutrality, and any attempts to "improve" it, even with good intentions, create a dangerous precedent.
In early August, nodes with the new rules will begin rejecting blocks without bit 4. The network will likely not split, but we will see a parallel chain with lower hashrate. This moment will show how many participants are willing to apply the new rules. But, as Saylor rightly noted, Bitcoin does not need guardians of purity. It needs guardians of neutrality.
Expert opinion: BIP-110 is an attempt to solve a problem that is not critical to network security, using a tool that could undermine its fundamental principles. The debate around it is not just a technical discussion, but a battle for the soul of Bitcoin. Whether pragmatism or the principle of immutability will prevail remains to be seen. But I lean toward the view that the market and community will ultimately choose neutrality, rejecting such a controversial activation mechanism.