Mow accused devs of mocking node operators an even DDoSing them, calling the culture "toxic" and urging humility and professionalism.Mow accused devs of mocking node operators an even DDoSing them, calling the culture "toxic" and urging humility and professionalism.

Samson Mow Slams Bitcoin Core Devs: Contempt for Users Threatens Network Future

2025/09/10 03:55

A dispute has emerged within the Bitcoin community, with Jan3 CEO Samson Mow accusing Bitcoin Core developers of treating users with disdain, and warning that such attitudes could jeopardize the network’s long-term success.

Mow stressed that no project can succeed if its builders look down on the people they are meant to serve.

Mow’s Indictment of Developer Conduct

In a lengthy post published on X, the BTC advocate argued that Bitcoin’s core issue is not merely technical but deeply cultural. He asserted that a toxic attitude among some developers is poisoning the ecosystem.

He pointed to specific behaviors to illustrate his claim, alleging that developers have been branding user nodes as “fake,” telling them “they don’t matter,” and even engaging in “DDoSing their nodes and laughing about it.”

The Jan3 executive described this behavior as “appalling” and suggested it stems from a problematic mindset:

According to him, the only solution to the issue is a return to professionalism and humility. He stated that anyone looking to work on Bitcoin should not make it all about themselves or take out their frustrations on other users.

“If you are really such a talented developer, then how come you are completely incapable of convincing people that your changes are good?” Mow asked, alluding to the ongoing debate surrounding the decision to remove the longstanding 80-byte limit on OP_RETURN outputs, which has seemingly divided the community.

His sentiment found support from others, with developer ‘Uncle Rockstar’ pointing out that it was “easy for developers to fall into the trap of thinking that technical proficiency equals intellectual superiority.”

However, not everyone agrees with this characterization. Earlier, BTCAzores co-founder Antoine Poinsot stated that Bitcoin is money and that protocol developers cannot force anyone to use it one way or the other.  Meanwhile, security expert Jameson Lopp offered a more pragmatic view, suggesting programmers may simply be “building for a different set of users” and that the “free market tends to sort these things out.”

The Technical Catalyst

Initially, the 80-byte OP_RETURN cap was implemented as a “gentle signal” to discourage excessive non-financial data from being embedded on the blockchain. However, some developers now say the limit is obsolete because miners have found ways to bypass it, even though they are complex and inefficient.

According to them, removing it will promote cleaner data storage and uphold network neutrality. Some, like Gregory Sanders, have asserted that “this is not endorsing non-financial data usage, but accepting that as a censorship-resistant system, Bitcoin can and will be used for use cases not everyone agrees on.”

Still, their justification has failed to placate critics. One of them, Bitcoin Knots maintainer Luke Dashjr, called the removal “utter insanity,” a sentiment also echoed by Mow and others who fear it will lead to network spam and a departure from the blockchain’s main function as peer-to-peer electronic cash. This change has become the battleground for a much larger war over the soul and future direction of the Bitcoin network.

The post Samson Mow Slams Bitcoin Core Devs: Contempt for Users Threatens Network Future appeared first on CryptoPotato.

Market Opportunity
NODE Logo
NODE Price(NODE)
$0.04
$0.04$0.04
+0.05%
USD
NODE (NODE) Live Price Chart
Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact service@support.mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.