Bitcoin's supply policy is encoded as a validation rule rather than set by a committee. A valid block may create only a defined subsidy, and that amount decreases after fixed numbers of blocks. Adding all scheduled subsidies produces a total that approaches 21 million BTC and ultimately stops increasing.
The phrase fixed supply can sound more automatic than it is. Software expresses the rule, but scarcity persists because node operators, businesses, miners, and users coordinate around versions that enforce it. The cap is credible when changing it would be widely detected and rejected, not because code can never be edited.
What you will learn
- Explain the relationship among subsidy eras, halvings, and the long-run supply limit
- Describe how independent validation prevents unauthorized issuance
- Separate a scarce issuance schedule from claims about price or demand
A declining issuance schedule
Bitcoin began with a block subsidy of 50 BTC. After every 210,000 blocks, the permitted subsidy is cut in half using integer-based protocol logic. Because each era creates fewer units than the era before it, the cumulative total converges toward a limit slightly below the commonly stated 21 million BTC.
The schedule follows block height, meaning a block's numbered position in the chain, rather than a calendar chosen by officials. Actual halving dates are estimates because blocks arrive at variable intervals. Nodes calculate the allowed subsidy from height and reject any coinbase transaction that overclaims it.
Nodes, not miners, enforce the ceiling
Miners write the special coinbase transaction that collects a block's subsidy and fees, but they do not define its maximum. Every validating node independently computes how much new bitcoin that block may create. A block with excessive issuance is invalid even if a powerful miner spent substantial energy producing it.
This division matters because proof of work chooses among valid histories; it does not rewrite the validity rules. Miners generally avoid building invalid blocks because honest nodes will not accept, relay, or extend them. The economic value of an invalid reward is therefore effectively zero to participants enforcing the established rules.
Why the rule is durable but not physically immutable
Bitcoin software is open source, so anyone can publish a version with a different supply rule. That edit cannot silently force existing nodes to accept extra issuance. It would create an incompatible system unless enough participants deliberately adopted the new rule and treated its resulting asset as the continuation they value.
The cap's defense is therefore social and technical at once. Technical validation makes violations obvious and locally rejectable; economic coordination makes unilateral change unattractive. Exchanges, custodians, merchants, miners, developers, and individual users may have different influence, but no single actor possesses a built-in supply override.
Maximum supply is not circulating liquidity
Issued supply includes units that may be inaccessible because keys were lost, scripts are unspendable, or owners refuse to sell. Circulating estimates cannot perfectly identify those cases from public data. Consequently, the amount available in markets at a given price may be far smaller and more variable than total issued supply.
Scarcity describes the issuance side, not demand. A capped quantity can still have falling value if fewer people want to hold or use it, if regulation limits access, or if market liquidity deteriorates. The supply rule is measurable; forecasts about purchasing power require separate evidence and assumptions.
Common misconceptions
“The 21 million cap is unchangeable because software can never be modified.”
Software can be modified, but existing nodes do not automatically adopt changes. Raising supply would require visible coordination around incompatible rules and could produce a separate asset and network.
“A fixed maximum supply guarantees that bitcoin's price must rise.”
Price reflects both supply and demand through available liquidity. A known cap does not guarantee adoption, market access, security, or willingness to pay.
Risks and limitations
- Lost keys reduce spendable supply but are difficult to identify reliably, making precise liquid-supply claims uncertain and easy to overstate.
- As subsidy declines, network security relies increasingly on transaction fees; insufficient fee demand could weaken miner revenue and alter security assumptions.
- A severe disagreement over monetary rules could split participants across incompatible networks, leaving markets to decide names, value, and operational support.
- Known scarcity does not prevent volatility, leverage-driven liquidations, exchange failures, custody losses, or long periods of weak demand.
Key takeaways
- Bitcoin's permitted block subsidy declines after fixed block intervals.
- Summed subsidies approach a limit conventionally described as 21 million BTC.
- Full nodes reject blocks that claim more issuance than consensus rules permit.
- The cap endures through transparent validation and participant coordination.
- Maximum supply, accessible supply, market liquidity, and demand are different concepts.
Primary and further reading
Test your understanding
Score at least 2 out of 3 to complete this lesson. Explanations appear after you submit.