Ten Bitcoins for Hal

Finney was no random recipient. He had worked on PGP, operated the first cryptographic anonymous remailer and created RPOW, an early attempt at transferable tokens based on proof of work. When the white paper reached the cryptography mailing list, he recognized echoes of questions he had studied for years.

The first version of the software was released on January 9, 2009. Finney later recalled that he was probably the first person after Satoshi to run Bitcoin. He mined on an ordinary processor at difficulty one and corresponded with Satoshi for several days: Finney reported bugs and Satoshi fixed them.

The Genesis Block appeared on January 3, but by itself it did not yet make a social network. Only the software release allowed someone outside Satoshi’s computer to verify the rules and extend the chain. Finney’s participation was therefore more than an enthusiastic comment. He added a second independent installation, a second pair of eyes on the bugs and the first chance to see whether nodes agreed on the same history.

Finney brought an unusual combination of patience and experience to such an experiment. As a developer working with Phil Zimmermann, he had contributed to PGP, the tool that brought strong cryptography from specialist workplaces to ordinary users. He also operated an anonymous remailer and in 2004 introduced RPOW, a system of transferable proofs of completed work. He knew that a clever algorithm was not enough: someone had to write the software, someone had to run it and someone had to find where it broke.

On January 10 he posted a terse sentence on Twitter: “Running bitcoin.” Today it reads like a ceremonial entry in a chronicle, but then it was closer to a status report: the program was running and taxing the computer. Finney later recalled that the fan was noisy and the processor ran hot, so after a few days he turned mining off. A future coin price was not yet an argument loud enough to drown out the real noise of a machine in his study.

On January 12, block 170 included a transaction that spent coins mined in an earlier block and created an output for Finney. The amount was 10 BTC and the fee was zero. The blockchain record contains no names, but Finney later confirmed that Satoshi sent him ten coins as a test.

Technically it was a small transfer. In human terms it was a decisive leap. Satoshi was no longer testing his own design only against himself. At the other end sat an experienced cryptographer with his own computer, his own copy of the program and the willingness to say what did not work. At that moment, peer-to-peer stopped being just a phrase in the white paper.

The blockchain itself preserves inputs, outputs, the amount and inclusion in a block; it does not preserve the sentence “Satoshi sent Hal.” We know the identities of both parties from Finney’s own testimony and contemporary correspondence. The story neatly separates what cryptography can prove from what people and archives add to the historical picture.

The transaction spent the output from block 9 and created two new outputs: ten BTC for the recipient and change back to the sender. A modern wallet hides such details, but in January 2009 they were exactly what the two men were testing. A valid signature had to be produced, nodes had to accept the transaction and a miner had to include it in a block that the other computer recognized as part of their shared history.

Ten coins did not appear on Hal Finney’s screen as files to download. What appeared was the ability to later create a new valid signature over an output that the network recognized as unspent. Satoshi lost exclusive control of that piece of history and Finney gained control of his own. In that narrow technical sense, the transfer completed the phrase peer-to-peer: the recipient did not have to ask the system’s author to continue maintaining his balance.

Bitcoin reduces the need to trust the keeper of a ledger. It does not remove human trust from the story of its birth. Finney had to believe that running a stranger’s experimental code was worthwhile. Satoshi had to accept his reports and change the program quickly. Both devoted time to a project with no guarantee that it would survive the week.

The difference lay in what they could verify. Finney did not receive a promise recorded in a private database. His node could check the history, the signatures and the rules under which the transfer was created. Trust started the collaboration; validating software checked the result.

That is less romantic, and more accurate, than the slogan about a trustless system. Bitcoin relocates trust: away from a custodian who can change the record and toward open rules, cryptography and personal verification. People can still be wrong, software can contain bugs and collaborators can disappoint. The difference is that the transfer’s validity is not a secret inside one company.

In the earliest days, that boundary was especially clear. The network consisted of only a handful of participants, Satoshi apparently mined most of the blocks and the program itself was freshly released. Finney could not rely on thousands of independent nodes or years of operation. He could, however, open the code, watch his client behave and compare the history it received with the rules. Trust in a person remained present, but for the first time it was accompanied by a concrete means of verification.

Their collaboration also had the ordinary shape of software development. Finney reported crashes and other problems, Satoshi sent fixes and both tried again. Neither knew whether the project would gain a third user. Yet they worked as though correctness mattered. Trust between two cypherpunks was not the opposite of verification; it was the reason they spent time building a system in which the people who followed would no longer have to rely on their word alone.

In 2013, Finney described his beginnings with Bitcoin while almost completely paralyzed by ALS. He controlled a computer with his eyes and still programmed safer Bitcoin wallets. What he remembered from the first blocks was mainly a hot processor, a noisy fan and the decision to stop mining.

His account does not turn the ten coins into a relic. It shows the continuity of a craft: download code, run it, find a bug, fix it and consider how the keys will one day pass to the children. The first transaction was therefore more than the beginning of an accounting history. It began a community that outlived both its first sender and its first recipient.

Finney’s earlier RPOW also shows that Bitcoin did not emerge in a vacuum. It inherited proof of work, digital signatures and the cypherpunk obsession with electronic cash, then combined them in a new way. Its first recipient was someone who understood not only the result, but the long line of failed attempts behind it.

Finney was diagnosed with amyotrophic lateral sclerosis in 2009. The disease gradually took away his movement and speech, but not his interest in technical work. When he wrote his recollections in March 2013, he controlled the computer with an eye-tracking system and was working on a tool for safer keys. He put neither self-pity nor a claim to a special place in history into the account. He described the joy of someone who had recognized a promising idea and could be there at its first moment.

He also thought about his wife Fran and the children who would one day inherit whatever remained of the early coins. That closes the first transfer in a different place from where it began. In January 2009, the question was whether ten units could safely pass to a second computer. Four years later, Finney was asking whether control could pass to another generation when the original holder could no longer type a password. In the meantime, Bitcoin had changed from an experiment between two programmers into personal property with real consequences for a family.