Step 6 / The Idea of Bitcoin
A paper, then a running network.
Follow the steps from a published idea to software another person could use.
On October 31, 2008, someone using the name Satoshi Nakamoto sent a message to a cryptography mailing list. Cryptography is the study of tools for protecting and checking information. The message linked to a paper describing a proposed electronic-cash system.
People could read the idea and question it. That was different from having public software they could run. The proposal and the running network arrived at different points in the story.
An idea published during a crisis
The announcement came during the global financial crisis. Financial institutions were under serious pressure. Governments and central banks were taking action in financial markets and institutions.
That setting helps explain why people might be interested in another way to make payments. It does not tell us every private reason Satoshi had for building Bitcoin.
The paper addressed a specific problem: making online payments without depending on one financial institution to stop the same money being spent twice. That is the claim we can read and examine.
A plan is different from proof that it works
The paper is called *Bitcoin: A Peer-to-Peer Electronic Cash System*. It describes signatures, linked records, proof of work, incentives, and possible attacks. The important idea is how those pieces work together.
A document explaining a technical design is often called a white paper. It can tell you what a project proposes and what assumptions its design needs. It cannot, by itself, show that someone has built the system or that it works in use.
Ask three separate questions. What does the paper claim? What has actually been built? What happened when people tried it? A polished paper is not an audit, and it does not prove that buying the asset will turn out well.
Peer-to-peer means participants can connect and exchange information with one another. It does not mean the system has no dependencies. It still needs software, network connections, and people operating computers.
A proposal, a working implementation, and observed use establish different things.
The first block, then software and a test payment
Bitcoin’s first block is dated January 3, 2009. It is called the genesis block. It contains a headline from The Times about another possible bank bailout. We can check that the message is there; it does not tell us why Satoshi made every design choice.
The software-release announcement came a few days later. Its archived timestamp says January 8 in UTC, the time standard used to compare times around the world. Some histories use January 9. The software release and the January 3 first block are separate events.
Hal Finney later wrote about running the software. He described receiving ten bitcoin from Satoshi as a test and sending bug reports back and forth. Here was someone besides the creator using the system and helping check how it worked.
Other people could keep the network running
Satoshi later stepped back from public development. Other people continued maintaining software and running the network. The creator did not need to approve every later payment.
People still had influence. Developers wrote software, miners proposed blocks, and node operators chose which rules to check. Users and businesses made choices too. A later lesson will separate those roles.
The public record has not established the creator’s real-world identity. Even if someone signs a message with an early key, that proves control of the key. It does not by itself prove that person wrote Bitcoin. The identity mystery should not replace evidence about the system.
The idea to keep
A proposal explains an idea. Released software lets people try it. Reports of use provide evidence about what happened. Those are different steps, and none alone proves an asset is a good investment.
Before following Maya’s payment through the network, pause and explain how the problem led to the design.