One of the most heated debates in Bitcoin's history is raging around BIP-110. The proposal, formally aimed at combating spam in the blockchain, has in practice faced harsh criticism from key industry figures — Michael Saylor, Adam Back, and Samson Mow. Let's figure out what's wrong with this initiative and why its opponents cannot be suspected of sympathizing with spammers.
BIP-110, also known as the Reduced Data Temporary Softfork, proposes introducing seven temporary restrictions on writing arbitrary data to the Bitcoin blockchain. This refers to images, texts, and other content unrelated to payments. Supporters position it as protection against spam and legal cover for node operators. However, despite the noble goal, the activation mechanism and potential consequences raise serious concerns.
The Core of the Conflict: Not the Content, but the Method
The key problem with BIP-110 is not the restrictions themselves, but the way they are introduced. Unlike standard procedures, this softfork uses a modified BIP 9 with a lowered activation threshold (55% instead of 95%) and no FAILED state. This means that even without support from miners, the initiative can be forcibly activated by node operators.
In his essay, Michael Saylor lists 110 objections, the key one being the creation of a dangerous precedent. The rules of BIP-110 are designed for one year, but the very fact of their adoption could be used to push through other, far more controversial changes. Adam Back called the initiative a "lynch mob" undermining Bitcoin's reputation as a neutral store of value.
Technical Risks and Workarounds
Researcher under the pseudonym Dathon Pwn discovered a consensus vulnerability in the BIP-110 activation client that could lead to chain splits. The problem is that nodes updating retroactively might recognize blocks that, upon re-checking under the new rules, should be rejected. This creates a risk of network fragmentation.
Furthermore, Slovak developer Martin Habovštiak demonstrated in practice that BIP-110's restrictions can be bypassed. He recorded a 66-kilobyte image in the blockchain without using OP_RETURN, Taproot, or other prohibited opcodes. His experiment showed that the "legal protection" for node operators, which the authors declare, is nothing more than an illusion.
Reality: Miners Against, Nodes — For
Currently, support for BIP-110 among miners is negligible — less than 1.5% of new blocks. The largest pools, including Foundry, AntPool, and F2Pool, have not signaled. Foundry even organized a vote among its clients, but with the standard low turnout, it is virtually impossible to get the necessary 51% "yes" votes.
Paradoxically, support among node operators is higher — up to 20% of public nodes have switched to the Bitcoin Knots client, ready to apply the new rules. However, as developer Jameson Lopp notes, these figures can easily be inflated via Tor and do not reflect real economic weight.
Expert comment from Cryptalist: BIP-110 is a classic example of how good intentions can lead to unpredictable consequences. Fighting spam is an important task, but attempting to solve it through forced consensus changes, ignoring the opinion of miners and creating risks for the integrity of the network, is a dangerous precedent. Bitcoin survives precisely because of its neutrality, and any changes must go through broad consensus, not through a "tyranny of the minority." The August fork will show how ready the community is to defend this principle.