Documented history · July 2010

How Bitcoin 0.3 Reached Slashdot’s Front Page

A small community decided to present Bitcoin 0.3 to a large technical audience. Before publication, participants edited the text together and debated whether the project was ready for the attention.

Version 0.3

In the summer of 2010, Bitcoin was discussed mainly within a small community. Developers released updates while forum participants tested the software, found defects, and debated how to explain the project to newcomers.

On July 6, Satoshi announced Bitcoin 0.3. The release added command-line and JSON-RPC control, a separate daemon without a graphical interface, transaction filters, a mining performance display, and roughly twenty percent faster hashing.

It also brought a Mac OS X version and German, Dutch, and Italian translations. Bitcoin was becoming useful to people with different computers and purposes, but its version number still began with zero: the project did not claim to be mature.

The Slashdot text was written together

One day before the release, a forum participant named teppy offered to submit the news to Slashdot, then one of the largest sites for programmers and technology enthusiasts. He drafted a headline and short description and asked the community to review the wording.

Participants debated whether to mention the issuance limit, how to explain BTC divisibility, whether BitTorrent was a useful comparison, and which words would make sense to someone encountering Bitcoin for the first time.

Satoshi joined the discussion. Overstated or inaccurate descriptions were removed. Instead of explaining everything, the submission needed to convey the distributed network, the absence of a central server, the limited issuance of BTC, and the new tools for controlling payments.

Bitcoin’s public introduction was shaped much like its software: through proposals, objections, and edits from several participants.

Not everyone thought the timing was right

Some forum members worried that reaching Slashdot’s front page was premature. Xunie pointed out that this was only version 0.3: interfaces were incomplete, defects might remain, and the server infrastructure might not withstand a sudden influx of visitors.

Others saw the risk differently. If a larger audience uncovered problems, it was better to see them while the project was young. The publication might also attract programmers willing to inspect the code and contribute.

The disagreement was not about whether Bitcoin should grow. It was about choosing between caution and an early test under pressure.

The story went live

On July 11, 2010, Slashdot published Bitcoin Releases Version 0.3. Readers who had never followed Bitcoin’s forum or the cryptography mailing list were invited to examine a digital system without a central controlling server.

The comments raised basic questions:

• why spend computing resources to create digital units;
• whether limited issuance could work in a growing economy;
• why the result of mining should possess value;
• how decentralized the network really was;
• whether Bitcoin could move beyond a technical experiment.

This was not promotional coverage with approval built in. Bitcoin had reached an audience under no obligation to accept the project’s original assumptions.

Attention brought new questions

New users and technical questions appeared on the forum after the publication. July discussions covered installation on different operating systems, processor load, address creation, database behavior, and other properties of the early client.

At the same time, Wikipedia considered deleting its Bitcoin article. One problem was the lack of enough independent sources: the project’s own website, forum, and developer descriptions were not sufficient to establish the subject’s significance.

Satoshi recommended making the encyclopedia entry less promotional and limiting it to a calm account of what Bitcoin was and where it belonged among electronic money systems.

Not advertising, but an outside test

One publication did not turn Bitcoin into a mass system. It did take the project beyond its usual circle of readers.

Newcomers did not come only to agree. They asked uncomfortable questions, ran the software on other computers, noticed limitations, and demanded more precise language. For an open project, that was another form of development.

The Slashdot episode can be presented as successful promotion, but the surviving discussion records something more complex: attention arrived together with criticism, load, technical questions, and the need for independent evidence of the project’s significance.

The outside audience did not arrive to confirm Bitcoin’s promises. It asked questions, looked for limitations, and tested the software.

Historical and educational material. Events and participants’ positions are reconstructed from the surviving forum discussions and the Slashdot publication.

Unless stated otherwise, the text, conclusions, structure and editorial arrangement were created by the project editors. Facts, quotations and source materials remain attributable to their authors and rights holders.