Module 4 · The Bitcoin Machine / 4.8
A supply schedule you can check.
What the limit tells you—and what it cannot tell you about price.
Imagine a release schedule printed before the first unit exists. It says how many new units may arrive at each stage.
If demand suddenly doubles, the schedule does not hear the news. That is the unusual idea behind Bitcoin’s issuance rules.
Small units. A bounded schedule.
One bitcoin contains 100 million satoshis. You do not need to own a whole bitcoin to use the network. Dividing a bitcoin into smaller existing units does not create additional bitcoin, just as changing a dollar into cents does not create extra dollars.
The original subsidy was 50 BTC per block. It halves every 210,000 blocks: 25, 12.5, 6.25, 3.125, and onward. These are amounts a valid block may newly issue, not interest paid to every holder.
The halves form a converging series. Under the current rules, total issuance is bounded by approximately 21 million BTC. Satoshi-level rounding and subsidies that were not fully claimed mean the actual issued total is slightly lower than the simple idealized sum.
maximum new subsidy per block
Era 1 of this illustration: existing coins do not halve. Transaction fees are separate from the subsidy.
The flow shrinks while the stock grows.
Before issuance ends, accepted subsidies add new bitcoin to the amount already issued. That is growth in the issued supply, even though the eventual limit was announced in advance.
Price inflation means a broad rise in prices. People also sometimes use “monetary inflation” to mean growth in a money supply. Neither definition should be quietly replaced with “any change to the maximum.” Be clear about which quantity you mean.
The halving cuts the subsidy, not the transaction fees and not everyone’s holdings. It happens at a block height, so its calendar date is an estimate. The final satoshi-sized subsidies are expected to end around 2140 under the current schedule.
The stock-to-flow ratio compares an existing stock with the annual amount newly produced. A shrinking issuance flow can increase that ratio. It does not turn the ratio into a reliable price forecast.
Scarcity does not create a buyer.
Imagine there are only ten tickets for an event nobody wants to attend. The count is fixed. That fact alone does not make the tickets valuable.
Bitcoin’s supply schedule answers a question about issuance. Price still depends on what buyers and sellers are willing and able to exchange, including their expectations, liquidity and alternatives.
A known halving can already be part of those expectations. Reducing new issuance does not mechanically guarantee a price rise, a particular cycle, or a useful return from any purchase date.
Lost keys can remove coins from practical circulation. But an old unmoved output may be saved, lost or waiting for a different reason. We cannot reliably label every quiet balance. Lost coins do not reappear as a reward for everyone else, and their existence does not guarantee anyone a gain.
The limit is enforced by people running rules.
A full node checks the permitted subsidy at each height and rejects a block that claims too much. A miner cannot raise the limit simply by buying more machines.
Anyone can write different software. The difficult question is whether others will adopt and value the changed network. The current rule has strong support, but no software lesson can prove that every future human decision is impossible.
That is why it helps to distinguish a verifiable rule from a prediction. You can inspect the subsidy schedule and observe whether blocks comply. You cannot inspect a line of code that guarantees future demand or unanimous social agreement.
As subsidies shrink, fees play a larger role in miner revenue. That connects supply policy to the security-budget question from the previous lessons. A fixed schedule removes one kind of discretion; it does not settle every economic tradeoff.
The idea to keep
Bitcoin’s current rules make new issuance predictable and bounded. They do not freeze the price, halve your holdings, eliminate lost-key risks, or guarantee that future users will want the asset.