Bitcoin Developer Mailing List

Bitcoin Developer Mailing List is the long-standing public forum where technical proposals, protocol changes, and Bitcoin Improvement Proposals are first aired and debated. It is a plain-text email list — deliberately low-tech — which keeps discussion searchable, archivable, quotable, and independent of the moderation quirks and algorithmic feeds of social platforms. Convention expects authors to introduce a protocol idea on the list before submitting a formal BIP, so the list functions as the ecosystem's first filter: a place where weak proposals meet hard questions early, in public, on the record.

History and hosting

The list has migrated with the infrastructure of open-source itself: originally hosted on SourceForge in Bitcoin's earliest era, later on Linux Foundation infrastructure, and — after that host wound down its mailing lists — reconstituted in early 2024 as the "bitcoindev" group on Google Groups. Each move preserved continuity of purpose rather than platform. The historical archives, reaching back to threads where Satoshi-era design decisions were argued, have been mirrored and preserved externally, so the record does not depend on any single provider's continued goodwill — an arrangement very much in keeping with the subject matter.

How ideas move through it

A typical lifecycle: an author posts a problem statement or draft design; implementers, researchers, and adversarially minded reviewers respond with attacks, prior art, and edge cases; the idea is revised, sometimes over months or years, or quietly abandoned. Ideas that survive graduate into the formal BIP process, reference implementations, and ultimately review under the project's code review culture. Landmark upgrades — SegWit's design debates, Taproot's multi-year refinement, and the activation-mechanism arguments covered under soft fork activation — all left long, public trails on the list first. Reading those archives remains one of the best educations in protocol design available anywhere, free.

A venue, not a government

The list's authority is reputational, not institutional. Posting an idea confers no power; a maintainer's email carries no more formal weight than a newcomer's, and nothing "passes" by being discussed. Decisions in Bitcoin emerge downstream — through rough consensus among reviewers, the willingness of maintainers to merge, and ultimately the software choices of node operators who can decline any change. The list is where arguments are made legible so that those distributed decisions can be informed ones. That is also why its plain-text, mirrored, censorship-resistant form matters: a monetary protocol's design debate should be as auditable as its code.

Reading and participating

The list sits within a small constellation of venues, each with a role. Implementation detail and line-by-line review happen on the Bitcoin Core repository; real-time coordination lives in developer IRC channels; and longer-form research increasingly appears on dedicated web forums built for threaded technical discussion. The mailing list remains the layer where protocol-level proposals seek ecosystem-wide visibility — the one address that reaches implementers of every wallet and node, not just one codebase's contributors. Knowing which venue a claim came from is itself useful context: a merged pull request, a mailing-list sketch, and a forum musing carry very different weights. When in doubt about provenance, the archives settle it: the list's history is public, mirrored, and searchable back to the beginning, which is more than can be said for most institutions that manage money.

The list is public to read and open to post, with light moderation for spam and civility. Etiquette is old-school: plain text, inline replies, technical substance over rhetoric, and search the archives before raising what was settled in 2015. For most practitioners the right relationship is asymmetric — read broadly, post rarely, and treat the archive as the primary source it is. When a claim circulates about "what developers intend," the list is where you check it against what was actually said.