A coin too big to use
Divide 21 million coins across the roughly 8 billion people alive today and the arithmetic is unforgiving:
That's if every coin were spread out evenly, which they never will be — the point isn't the distribution, it's the scale. There is not enough "bitcoin" for one in four hundred people to own a whole one, let alone everyone. A unit that most of the species can't hold even one of is a poor everyday unit, whatever else it's good for. So the protocol was built with a second, much smaller unit from day one: the satoshi.
The division that was there from the start
One bitcoin divides into exactly 100,000,000 satoshis (sats). This isn't a later add-on or a community convention — it's built into the transaction format itself. Bitcoin's ledger doesn't actually store "0.00050000 BTC"; internally, amounts are integers counted in satoshis, and "BTC" is just a display convention, a way of writing a very large integer with a decimal point inserted eight digits from the right.
That last row is the floor. One satoshi is the smallest amount the protocol can represent — there's no such thing as half a satoshi in a transaction. In that sense, satoshis are to bitcoin what cents are to a dollar, except the ratio is ten-thousand times finer: 100 cents make a dollar, but 100,000,000 sats make a bitcoin.
A sliver too thin to see at the whole-coin scale is still a million satoshis wide.
21 million is the number worth quoting. 2.1 quadrillion is the number worth using.
Redoing the population arithmetic in sats
The same division that looked scarce in whole bitcoins looks completely different once it's expressed in the unit the protocol actually tracks:
262,500 sats per person, evenly split, is a far more usable-sounding number than 0.0026 BTC — even though it's the exact same amount of value. Nothing about the underlying scarcity changed; only the unit did. This is purely a labeling effect, and it's worth naming as one: "not enough bitcoin to go around" and "hundreds of thousands of sats per person" describe an identical division of an identical supply. Neither framing is more true than the other — but one is much easier to reason about in everyday amounts.
Why the name, and why it stuck
The unit is named after Satoshi Nakamoto, the pseudonym used by Bitcoin's creator (or creators — the identity has never been confirmed, and this book has no theory about it). The name wasn't official in the original software, which referred to the small unit simply as "cents" or displayed raw integer values; "satoshi" emerged from the community as shorthand sometime after the 2009 launch and was later adopted informally by wallet software and, eventually, by the reference client's own documentation. It's a rare case of a technical unit named by consensus rather than by decree — fitting, for a system that runs on the same principle.
Wallets and exchanges are not fully consistent about which unit they show by default. Some display BTC with eight decimal places (0.00050000), some display sats as a plain integer (50,000), and a few use intermediate units like "bits" (one-millionth of a BTC, 100 sats) that never achieved wide adoption. When reading any bitcoin amount, the first thing worth checking is which unit is actually being displayed — the same underlying value can look tiny or large purely based on that choice, as the arithmetic above demonstrates.
This isn't just a hypothetical fix — it's already happened in practice. Lightning-focused wallets and apps including Strike, Cash App, BlueWallet, Muun, Phoenix, and Breez default new users to a sats-denominated balance rather than decimal BTC, for exactly the reason this chapter argues: a coffee priced at 7,350 sats reads as an ordinary whole number, while the identical amount priced at 0.00007350 BTC reads as an intimidating string of leading zeros. Same value, same protocol, different number of digits before the decimal point — the industry converged on sats-first display for everyday spending because the labeling effect described above is real, not just a book's argument about it.
Precision has a cost, too
It's worth being honest about the other direction: a smallest unit that fine also means transaction fees, wallet displays, and mental arithmetic all have to handle very large integers or very small decimals, depending on which unit is in view. This is a usability tradeoff, not a free lunch — it's just a better tradeoff than the alternative of a currency with no small unit at all, where the population arithmetic above would leave most people holding an awkward fraction of an indivisible thing.
There's a floor to how small a real-world payment can practically go, too, even with a unit this fine — not because of the satoshi itself, but because of what it costs to move one on-chain. That's the subject of a later chapter on the Lightning Network, which exists specifically to let sat-sized and even sub-sat-equivalent payments move without touching the base ledger at all.
What actually changed by switching units
Nothing about scarcity, nothing about the schedule from Chapter 1, and nothing about the 21 million cap. What changed is only the number you'd say out loud when describing an everyday amount. That's not a trivial point — units shape intuition, and a supply that sounds impossibly scarce in one unit can sound perfectly workable in another, without a single fact on the ground being different. The honest summary: 21,000,000 is the number that makes headlines; 100,000,000 is the number that makes the currency usable; and 2,100,000,000,000,000 — the product of the two — is the number that was true the entire time.