Summary
- Samson Mow argues that Bitcoin Core decisions surrounding OP_RETURN helped fuel community tensions and contributed significantly to the BIP-110 movement’s emergence.
- Mow maintains that changing OP_RETURN offered little practical benefit because the disputed setting involved default node policy rather than consensus rules.
- The BIP-110 dispute produced an alternative Bitcoin fork, but extremely low adoption prevented it from gaining meaningful support across the network.
Bitcoin entrepreneur Samson Mow has blamed decisions within the Bitcoin Core ecosystem for fueling the BIP-110 movement. According to Mow, developers helped create the backlash through their handling of OP_RETURN and wider community disputes.
Mow directly challenged Bitcoin Core developer Antoine Poinsot over the development community’s handling of disagreements surrounding Bitcoin policy. He argued that similar conflicts could emerge unless developers recognize their role in creating the backlash.
Moreover, Mow claimed that hostility from people opposing BIP-110 strengthened anger among supporters of the movement. He criticized associations between some Core developers and individuals whom he accused of using aggressive rhetoric.
Mow also referenced controversies involving Zhao and Newberry while explaining factors that increased divisions across the Bitcoin community. He described several decisions surrounding the dispute as poorly handled and damaging to trust between opposing groups.
Also Read: Here’s When the Greatest XRP Rally Opportunities are Forged – Analyst Explains
OP_RETURN Dispute Takes Center Stage in Mow’s Criticism
OP_RETURN remains central to Mow’s explanation for why the BIP-110 movement attracted support among some Bitcoin users. The feature allows transactions to carry limited arbitrary data without changing Bitcoin’s fundamental consensus rules.
Significantly, Mow argued that developers should have left the OP_RETURN default policy unchanged while community tensions eased. He maintained that users understood the difference between default node policy and Bitcoin’s consensus requirements.
Consequently, Mow believes changing the default setting offered little practical benefit while creating unnecessary conflict across the wider ecosystem. His argument centers on how developers approached the policy change rather than its technical impact alone.
Additionally, Mow rejected claims that his earlier criticism of Bitcoin Core amounted to defamatory attacks against its developers. He maintained that his remarks highlighted structural concerns that Bitcoin developer Jon Atack later discussed publicly.
BIP-110 Fork Struggles to Gain Network Support
The BIP-110 dispute reflects competing views about how participants should use Bitcoin’s limited block space. Supporters of tighter restrictions generally favor monetary transactions over storing arbitrary data across the network.
Meanwhile, those disagreements contributed to an alternative Bitcoin fork seeking stronger restrictions on arbitrary transaction data. However, the fork received extremely low adoption and failed to secure meaningful support among Bitcoin network participants.
Its limited adoption demonstrated the difficulty of converting dissatisfaction with Bitcoin Core policies into support for alternative software. Bitcoin participants ultimately determine whether competing rules gain traction through software choices and network participation.
Mow’s criticism therefore places Bitcoin Core’s decisions at the center of the backlash surrounding BIP-110. He maintains that leaving OP_RETURN unchanged could have reduced tensions while preserving Bitcoin’s existing consensus rules.
Also Read: Bitcoin Long-Term Holder Losses Signal Bottoming Phase Without Full Capitulation
