Why Blockchain?

Before any block, any chain, or any cryptographic hash function shows up, blockchain starts as the answer to one specific, genuinely old problem: how do two people who don't trust each other exchange digital money without a trusted third party in the middle? This chapter is entirely about that problem — what it actually is, why it resisted a clean solution for decades, and the real 2008–2009 moment where Bitcoin first solved it.

The Double-Spending Problem

Physical cash solves its own trust problem by being, well, physical. If you hand someone a £10 note, you no longer have it. There is exactly one copy, and possession of that one copy is the proof of ownership.

Digital information doesn't work that way. A digital file — a photo, a document, a string of bytes representing "£10" — can be copied perfectly and instantly, as many times as you like, with no way to tell the copy from the original. If digital money were just a file, nothing would stop you from emailing that same "£10" file to two different people, or spending it in two different shops at once. This is the double-spending problem: the risk that the same unit of digital currency gets spent more than once, since nothing about the digital token itself prevents duplication.

The Traditional Fix: A Trusted Third Party

Every digital payment system that predates blockchain solves double-spending the same way: by appointing a trusted central authority — a bank, a card network, a payment processor — to keep the one authoritative ledger. When you pay by card, your bank checks its own private records, confirms you actually have the money, deducts it, and credits the recipient's bank. The ledger only has one owner, so there's only ever one "true" balance to check against, and double-spending simply can't happen — not because of anything clever about the money itself, but because a single trusted party is watching every transaction and refusing to allow it twice.

This works, and it's how essentially all electronic payments still function today. But it comes with a real, structural cost: every transaction depends on that one trusted party actually being trustworthy, actually staying available, and actually being willing to process your transaction at all. Two people who don't know or trust each other, and don't want to depend on a bank, a government, or a company sitting between them, have no way to transact digitally without simply trusting someone.

Earlier Attempts, and Why They Fell Short

Bitcoin wasn't the first attempt at digital cash, and it's worth being honest about that rather than treating it as having appeared from nowhere. Several real, earlier cryptographic proposals tackled pieces of the same problem:

• David Chaum's digital cash (1980s, commercialized as DigiCash in the 1990s) — pioneered genuinely anonymous, untraceable electronic payments using real cryptographic techniques. It still relied on a central issuer to prevent double-spending, though, so it hadn't removed the trusted-third-party problem — only made that party's job cryptographically more private.
• Adam Back's Hashcash (1997) — a real proof-of-work scheme, originally built to fight email spam by making a sender do a small, verifiable amount of computational work per message. It wasn't a currency at all, but its core mechanism — "prove you did real, costly work" — is directly what Bitcoin's own mining later reused.
• Wei Dai's b-money (1998) — a real proposal for a currency created through solved computational puzzles, without a central issuer, that Satoshi Nakamoto's own Bitcoin whitepaper directly cites.
• Hal Finney's RPOW, "Reusable Proof of Work" (2004) — took Hashcash's own proof-of-work idea and made the resulting tokens actually transferable between people.
• Nick Szabo's bit gold (2005) — another real proof-of-work-based proposal, explicitly aimed at creating scarce digital value without a central authority, but it never fully solved double-spending on its own and was never actually built as a working system.

Every one of these proposals contributed a real, genuine piece — anonymity, proof-of-work, scarcity, transferability — but none of them combined all the pieces into one working system that solved double-spending without a trusted central party. That synthesis is exactly what Bitcoin did.

Bitcoin: The First Working Solution

What a Blockchain Actually Is, at a High Level

Stripped of the mechanics this course builds up over the coming chapters, a blockchain is:

• a distributed ledger — a record of transactions copied across many independent computers ("nodes") rather than stored in one central place;
• that is append-only — new transactions can be added, but existing ones can't be secretly rewritten, because doing so would break a cryptographic chain of links back through every earlier block (Chapter 3);
• where the participants agree on what's true not because they trust each other, but because of a costly, verifiable process (Chapter 4) that makes cheating more expensive than it's worth.

None of this requires anyone to trust a bank, a government, or a company. It requires trusting that a majority of the network is following the rules honestly — and, crucially, that the system's own incentives make honest behavior the profitable choice. That's a genuinely different kind of trust than "trust this one company," and it's the whole reason blockchain gets described as trustless or, more precisely, trust-minimized.

Hands-On Exercises

Three exercises reinforcing this chapter's own core distinction — trusted-third-party systems vs. trust-minimized ones — before any blockchain mechanics are introduced.