Blockchain/Level II · Mechanics/2.3 Blocks and the chain/Lesson 7
The 21 million supply schedule
The arithmetic of scarcity and the bugs that tried to break it
MaterialsA block explorer with real-time supply dataThe Bitcoin Core source code for GetBlockSubsidyA calculator capable of geometric series
Wonder
- How does a finite number emerge from an infinite sequence of halvings?
- What happens when a software bug creates more money than the protocol allows?
- Why is the actual circulating supply lower than the theoretical maximum?
Explore
- The 21 million limit is not a promise but a mathematical consequence of the issuance schedule. New bitcoins enter circulation exclusively through the block subsidy, which started at 50 BTC per block in January 2009. This reward halves every 210,000 blocks, roughly four years. The formula sums a geometric series: 210,000 blocks multiplied by 50 BTC, times the sum of powers of one-half (1 + ½ + ¼ + …). This infinite series converges to exactly 21,000,000 BTC.
- Because Bitcoin measures value in integer satoshis (hundred-millionths of a bitcoin), each halving rounds down. The subsidy reaches the minimum unit of one satoshi at block 6,720,000, around the year 2136 or 2137. By block 6,930,000, approximately in 2140, nearly all 21 million BTC will have been issued. The true maximum is slightly less than 21 million due to these rounding truncations, settling at about 20,999,999.9769 BTC.
- Effective supply is lower than the theoretical cap for several reasons. The genesis block reward of 50 BTC is unspendable by design. Some miners claimed less than the full subsidy, and the unclaimed amount was never created. Coins have been sent to provably unspendable outputs, and many private keys are lost forever due to hardware failures or forgotten passwords. These factors reduce the circulating supply below the protocol’s hard ceiling.
- The cap is enforced by consensus rules in the Bitcoin Core software, not by external authority. Every node validates that no block exceeds the allowed subsidy. In August 2010, a value-overflow bug (CVE-2010-5139) allowed a transaction to create over 184 billion BTC in block 74,638. A patched client was released within about five hours, and miners running it built a chain, without the bad transaction, that overtook the original 53 blocks later, erasing the coins. The episode showed that the cap is only as sound as the node software that enforces it, and that the network can coordinate quickly to defend it.
- In 2018 another inflation bug (CVE-2018-17144) was found in Bitcoin Core versions 0.15 to 0.16.2: a miner could have created coins with a transaction that listed the same input twice. It was patched with no known exploitation. Both episodes show that the schedule depends on correct software and on people watching it.
- Open a block explorer and check the current circulating supply against 21,000,000 BTC. Note the difference between the theoretical maximum and the actual coins in circulation. Observe the next halving date and calculate how many blocks remain until the subsidy drops from 3.125 to 1.5625 BTC. This check confirms that the issuance schedule is proceeding exactly as coded.
Key facts
- The issuance schedule sums to 21,000,000 BTC in theory.
- The block subsidy halves every 210,000 blocks, starting at 50 BTC and reaching zero around 2140.
- The true maximum supply is slightly less than 21 million due to integer rounding of satoshis.
- The genesis block reward of 50 BTC is unspendable, reducing effective supply.
- In August 2010, a bug (CVE-2010-5139) created over 184 billion BTC before the chain was reorganized.
- Miners can claim less than the full subsidy; the unclaimed amount is never created.
Exercise nine, six, three, one
9CollectList 9 different assets or currencies with a fixed or capped supply. Note their maximum quantities and who enforces the cap.
6ClusterGroup the 9 into 6 by enforcement mechanism: code-enforced, contract-enforced, physical scarcity, legal decree, market convention, or other.
3DistillReduce the 6 to 3 reasons why a supply cap might fail or be altered.
1CrystallizeWrite 1 sentence on what distinguishes a hard-coded cap from a political promise.
Fact check
Dates, figures and claims checked against the published sources listed below.