On April 2, 2025, Google temporarily disabled the Bitcoin Development Mailing List, a crucial forum for Bitcoin developers, and reactivated it a day later after several hours of outage.

Known as bitcoindev, this mailing list is the space where Bitcoin Improvement Proposals (BIPs) are discussed. It coordinates the development of Bitcoin Core and resolves technical issues affecting the network. Its importance is significant: it acts as a communication hub for a community that supports one of the most emblematic projects of decentralization.

Its migration history—from the Linux Foundation to SourceForge.net, and then to Google Groups in February 2024—reflects the search for a stable home for a process that, ironically, underpins a system designed to be independent of any central authority.

Why Did Google Suspend the Bitcoin Development Mailing List?

The reason behind the suspension has no official explanation beyond what has been stated by individuals and forum members on social media.

Ruben Somsen, developer and moderator of the mailing list, shared an initial post detailing that Google had classified the content within the list as “spam, malware or other type of malicious content,” leading to its takedown.

Somsen clarified, “As far as I know, nothing inappropriate has been published,” and stated that he had requested a review.

Later, Somsen made a second post in which he revealed an email (ironically delivered to his own spam folder) explaining that an external report had classified the mailing list’s content as illegal or infringing, prompting Google’s legal team to shut it down.

Google, via a support account on X and in response to Somsen’s posts, said they would conduct “a quick investigation” but did not offer further public commentary.

While the exact cause of the temporary closure remains uncertain, some speculate it may have been the result of a coordinated attack possibly by bots or mass-reporting individuals labeling the list as spam. In the absence of transparency from Google, such theories have gained traction.

Somsen’s frustration was clear:

“The Bitcoin development list is temporarily down. Our transgression? We're 'unwanted content.' Seriously, Google? Open source development is 'unwanted'? I guess we'll migrate again.”
— Ruben Somsen, Bitcoin Development Mailing List moderator

What the incident underscored is the contradiction pointed out by many in the Bitcoin community: a project rooted in decentralization, built specifically to avoid reliance on intermediaries, was silenced if only temporarily by a centralized platform.

Centralization as an Achilles’ Heel

The outage exposed deeper systemic flaws, as software engineer and well-known bitcoiner Jameson Lopp noted:

“This wouldn’t have happened if SMTP hadn’t become ossified, captured, and centralized in the hands of a few gatekeepers over decades.”

SMTP (Simple Mail Transfer Protocol), the standard for sending emails over IP networks and used by bitcoindev, was originally designed as a decentralized system. But over time, it became tied to infrastructure controlled by large corporations like Google, creating centralized points of failure, like a spam filter or a policy decision that can suddenly shut down vital communication channels.

Another user on X summarized the situation more bluntly:

“As a Bitcoiner, I say everything that is centralized depends on someone or something, simple.”

This criticism touches on both technical and philosophical contradictions: while Bitcoin avoids intermediaries at the protocol level, its development infrastructure remains reliant on vulnerable, centralized services.

Looking Ahead

The restoration of the mailing list on April 3 didn’t put an end to the broader discussion. Google may still be the current home of bitcoindev, but the incident has highlighted the fragility of that relationship.

As the community explores alternatives, platforms like GitHub (for collaborative code development) and Nostr (a decentralized communication protocol) have emerged as viable options. However, the email format has a deeply embedded legacy within the Bitcoin development process, and shifting away from it won’t be easy.