Chapter 7

Scarcity You Can Audit

Chapters 1 and 5 established what the schedule says: 21 million coins, issued on a fixed, public timetable. This chapter is about something different — not what the schedule says, but how anyone, including you, can check that reality matches the schedule, without asking a single institution to vouch for it.

Chapter 7 of 24

Two ways to check a number

Every monetary system publishes a supply figure of some kind. The difference that matters isn't whether the number exists — it's whether you can independently reproduce it, or whether you're stuck trusting whoever published it. Central banks report the money supply (M0, M1, M2 — progressively broader measures of currency and bank deposits) on a periodic schedule, compiled from data that ordinary people cannot access or recompute themselves. When the Federal Reserve reports M2, you're trusting their data collection, their methodology, and their honesty — not because they're likely lying, but because the underlying ledger genuinely isn't open for you to check.

Bitcoin's supply figure works the other way around. The entire issuance history — every coin, from the first block in 2009 to the block mined an hour ago — is recorded on a ledger anyone can download and independently recompute from scratch. Nobody has to take Bitcoin's word for how many coins exist. They can count.

The rule every node enforces, not just observes

"Counting" undersells what actually happens. A Bitcoin full node doesn't just read a total off the chain and trust it — it independently re-derives every block's legitimacy from the protocol's rules, including one rule in particular: a block's coinbase transaction (the one that pays the miner) may pay out at most the block-height subsidy plus the transaction fees in that block. Fees transfer existing coins; only the subsidy permits new issuance. The subsidy is the exact figure tracked era by era in Chapter 5's table. A miner is free to claim less than the allowed subsidy — plenty of early blocks did, by accident or design — but a block that claims more is invalid, full stop, rejected by every honest node on the network regardless of how much hashing power produced it.

This is the detail that turns "21 million" from a design intention into an enforced fact. It isn't that miners have agreed, as a courtesy, to follow the schedule. It's that a block violating the schedule doesn't propagate as a valid block at all — the software refuses it, the same way it would refuse a block that tried to spend coins twice. Chapter 5 was one column short of a claim this chapter can now make in full: the reward schedule isn't just what's supposed to happen, it's what full nodes make happen, by rejecting anything else.

Miner assembles a block Coinbase tx claims X BTC Every node independently checks: X ≤ subsidy + block fees? yes no Amount check passes other validity checks still required Rejected refused by every honest node — any hash power
Era 5's subsidy is 3.125 BTC. With 0.001 BTC in block fees, coinbase outputs may total up to 3.126 BTC; 3.12600001 BTC fails this amount check. Passing it alone does not make a block valid or select it for the active chain: the other consensus checks and valid-chain selection still apply.

This isn't a purely hypothetical mechanism — it was tested once, for real, early on. On August 15, 2010, a bug later cataloged as CVE-2010-5139 let a single transaction in block 74,638 create 184,467,440,737.09551616 BTC out of thin air for two addresses. It was a different flaw than the coinbase check diagrammed above — an integer overflow in how transaction output amounts were summed, not a subsidy violation — but the same category of threat: more coins than the rules permit. What happened next is the part that matters for this chapter's claim. A patched client shipped within about five hours, honest nodes adopted it, and the corrected chain overtook the tainted one by block 74,691 — orphaning the invalid transaction for good. No coins were permanently created and no user lost funds. The 21-million schedule held not because anyone asked nicely, but because enough independently operated nodes simply refused to build on a chain that broke it.

Counting the supply by hand

The fixed block ranges and subsidies let us calculate a scheduled subsidy ceiling including the genesis schedule. This is not actual issued, circulating or spendable supply. The first four eras cover heights 0–839999 inclusive:

Era 1: 210,000 blocks × 50 BTC = 10,500,000 BTC Era 2: 210,000 blocks × 25 BTC = 5,250,000 BTC Era 3: 210,000 blocks × 12.5 BTC = 2,625,000 BTC Era 4: 210,000 blocks × 6.25 BTC = 1,312,500 BTC ----------- Scheduled ceiling, heights 0–839999 inclusive: 19,687,500 BTC

Height 840000 is the first block of era 5, so its 3.125 BTC scheduled subsidy must already be included when counting through that height. For integer heights 840000–1049999 inclusive, the ceiling is:

Scheduled subsidy ceiling through height H: 19,687,500 + (H − 840000 + 1) × 3.125 BTC At height 840000: 19,687,503.125 BTC

The +1 counts the block at H itself. This formula applies only to the stated era; later heights require the next era's subsidy. Unclaimed subsidies and the unspendable genesis output prevent interpreting this schedule as measured spendable supply. Transaction fees transfer existing coins rather than add subsidy. An explorer's supply total may use a different definition and cannot be assumed to equal this ceiling.

Reproduce the integer-satoshi arithmetic with the code and era table in our subsidy-schedule resource. The pinned Bitcoin Core v29.0 sources show GetBlockSubsidy and block validation and the mainnet halving interval and genesis parameters. Reproducing the schedule is not a measurement of chain issuance or spendability.

Nobody has to believe Bitcoin's supply is honest. They can check it — and so can the next person, and the next, forever, using nothing but public data and arithmetic anyone can run themselves.

What auditability doesn't prove

This chapter's claim is narrower than it might sound, and worth stating precisely rather than oversold. Auditability proves that the issuance rule is enforced — that no more than the scheduled number of coins can ever be created. It does not prove anything about price, about how many coins are actually in active circulation versus lost forever (a later chapter covers exactly that gap), and it does not, by itself, prove decentralization — a network where one party controlled every node could still "enforce" any rule it liked, honestly or otherwise. What makes the enforcement meaningful is that thousands of independently operated nodes run this same check with no coordination required, and a would-be cheater has to convince all of them at once, not just one.

It's also not a claim that the schedule is somehow immune to change. Bitcoin's rules are software, and software can theoretically be changed by consensus among the people running nodes — Chapter 1 already covers why that's a coordination problem approaching impossible in practice, not a mathematical impossibility. What this chapter adds is the mechanism for the half of that claim Chapter 1 took as given: the reason changing the schedule is hard isn't that anyone declared it off-limits, it's that every node is actively, continuously checking for exactly that kind of change and rejecting it on sight.

This chapter describes a verification mechanism, not investment guidance. Running a full node or reproducing this arithmetic yourself requires no permission from anyone, but it also doesn't tell you anything about future value — only about how much has been, and can be, issued.