The double-spend problem
The reason digital cash didn’t exist for the first fifty years of computing comes down to one sentence: a digital file can be copied perfectly, so digital money can be spent twice. Solving that — with no referee — is the problem Bitcoin was invented to crack.
Why copying breaks money
A physical coin can only be in one place. When you hand it over, you no longer have it. But a digital “coin” is just a file — a string of bits — and bits copy for free. If money were a file on your computer, you could email it to Alice, keep the original, and email the very same money to Bob. Both would think they were paid. That’s a double spend, and it’s just counterfeiting by another name.
“For money to work, spending it has to mean losing it. Digital files don’t naturally work that way.”
The old solution: a trusted middleman
Every digital payment system before Bitcoin solved this the same way — with a central referee who keeps the one true ledger. When you pay with a card, your bank checks its records, confirms you have the money, subtracts it from your balance and adds it to the merchant’s. You never actually hold the money; the bank just updates a number. Because there’s a single authoritative ledger, you can’t spend the same dollar twice.
But the referee is also the weakness. A central ledger-keeper can freeze your account, censor payments, reverse transactions, inflate the supply, get hacked, or simply be ordered around by whoever holds power over it. We saw this exact pattern in Monetary History: the moment your money lives in someone else’s ledger, they control it.
The real question
So the challenge sharpens. Could you build digital money that prevents double-spending WITHOUT a trusted third party? Could a crowd of strangers, none of whom trust each other, agree on one shared history of who owns what — and keep it honest?
For decades this was considered impossible, because it’s really an instance of a famous computer-science puzzle about reaching agreement among untrustworthy participants: the Byzantine Generals Problem. That’s next.
Spotted an error or have feedback on this lesson? Suggest a correction ↗
Comments
Powered by Nostr — reply from any Nostr client, and zap the lesson over Lightning.