The last chapter showed you that all money is ledger entries, kept honest by banks and a central bank. A blockchain asks one radical question: what if everyone holds a copy of the ledger, and math replaces the bank? This chapter builds that machine from zero — keys, blocks, consensus, smart contracts. No hype, no scorn, no prior knowledge.
A bank keeps one notebook and guards it. A blockchain hands out thousands of identical copies of the notebook and lets math, not a manager, decide what gets written next. To pay someone, you sign the entry with a secret key only you hold. Thousands of strangers check the signature, agree, and every copy updates at once.
That buys the one thing money always needed a middleman for: agreement on who owns what, with nobody in charge. It also breaks in new ways. Lose your key and the money is frozen for good — an estimated 3–4 million bitcoin (roughly a fifth of all that will ever exist) are thought lost this way (estimate). First the machine, then exactly where it fails.
Alice sends Bob 5 coins on a public blockchain. No bank, no network operator, no one to call. Watch what replaces them.
Strip the mystique: a block is a page of the ledger, and the "chain" is each page carrying the fingerprint of the page before it.
Eight terms carry the rest of this chapter. Get these and no crypto sentence can lose you.
"A mail slot anyone can drop into. One key opens it."
A blockchain account is a key pair. The address (from your public key) is like a mail slot — anyone can see it and send to it. The private key is the only thing that can spend from it. Signing a transaction with the private key produces a signature anyone can verify but nobody can forge. No username, no password reset, no support line: the key IS the account. Lose it and the money is frozen forever; leak it and the money is gone. Custody — who holds keys — is the industry this fact created.
"Make cheating cost more than honesty pays."
With thousands of ledger copies, who gets to add the next block? Proof-of-Work (Bitcoin): compete by burning electricity on a lottery-like puzzle; rewriting history means redoing all that work — economically absurd. Proof-of-Stake (Ethereum, most modern chains): validators post their own coins as collateral; cheat and the protocol destroys it ("slashing"). Different mechanics, same design: make attacking the ledger more expensive than the ledger is worth. That's what replaces the central bank's rulebook.
"A vending machine living on the ledger."
Some chains let you deploy programs onto the ledger — code with its own balance that moves money by rule, automatically, with no operator. Insert coin, get soda: no cashier. This is the piece that makes everything else possible: a stablecoin is a smart contract (a program that mints and redeems tokens against reserves), a DEX is a smart contract, tokenized deposits are smart contracts. When this site says "token," it means: an entry managed by one of these programs.
"A tab at the bar, settled at closing time."
Every copy of the ledger processes every transaction — secure, but slow and expensive at rush hour (that's the gas fee spiking). A Layer 2 runs a faster side-ledger that batches thousands of transactions and periodically posts a compressed, provable summary to the main chain (L1) — like a bar tab settled once at closing instead of tapping per drink. Security inherited from L1, costs divided across the batch: cents become fractions of cents. When the crypto chapter says "gas ≈ $0.03 on an L2," this is why.
"A town square vs a members-only club."
Public chains (Bitcoin, Ethereum, Solana): anyone can hold a copy, validate, and transact — censorship-resistant, radically transparent (every balance and payment is visible to the world, pseudonymously). Permissioned chains (bank consortium ledgers): a known club of institutions runs the nodes — faster, private, but you're back to trusting the club. Most "enterprise blockchain" is the second kind, and critics reasonably ask what it does that a shared database doesn't. The honest answer: sometimes nothing; sometimes neutral ground no single member controls.
"You don't remove trust. You relocate it."
The last chapter showed banks made trustworthy by capital, collateral and supervision. Blockchains relocate that trust into code, keys and incentives — and inherit new failure modes: bugs in smart contracts, stolen keys, bridge hacks, concentrated validators. Neither system is trustless; they just fail differently. Payments professionals don't need to pick a side — they need to know where each system keeps its trust, and what breaks it.
The ledger itself is hard to break. Almost everything around it is not. Three real failures, then a tree for the question every user eventually asks: why isn't my transaction confirming?
Five questions beginners actually ask, answered without hedging.
Three deeper cuts: what throughput numbers really mean, the privacy paradox, and how chains change their own rules.