Bitcoin supply: the proposal, the first block and the ceiling
The Bitcoin supply limit is usually expressed as 21 million bitcoins. Behind that familiar figure sit several distinct historical documents: Satoshi Nakamoto's proposal for electronic cash, the first block preserved in the software, and the rules that later Bitcoin Core releases used to validate new issuance. The project's FAQ gives the headline ceiling. The program supplies the mechanism, calculating a declining block subsidy and rejecting excessive claims.
Nakamoto's original paper began with a payment problem rather than a numerical supply target. Digital signatures could connect successive owners of an electronic coin, but they could not by themselves establish that an owner had refrained from spending it twice. A conventional electronic mint could settle that difficulty by checking every transaction. Nakamoto instead proposed publicly announced transactions and a shared chronological record. Blocks linked through hashes would make alterations to earlier entries require renewed computational work. The proposal's security argument depended on honest participants collectively controlling more computational power than a cooperating group of attackers.
The paper's incentive section introduced the monetary element. A special first transaction in each block would create new coins for the block's creator, distributing an initial supply without a central issuer. Nakamoto compared the expenditure of computing resources and electricity with the effort of gold mining. Transaction fees provided another possible incentive, and the paper envisaged an eventual transition to fees after a predetermined quantity had entered circulation. It did not print the number 21 million or specify the later halving interval. Those numerical details belong to implementation, beyond the outline of incentives supplied by the original proposal.
The first block gives Bitcoin supply history an unusually specific artifact. Bitcoin Core's version 28.0 chain-parameter file preserves the genesis block and its reference to a newspaper headline dated January 3, 2009, concerning another bank bailout. The same file records a 50-bitcoin output for that block. Its accompanying comment explains that the output cannot be spent because it was not originally present in the transaction database. The opening entry therefore contains both an issuance figure and an explicit technical limitation on that particular output. A recorded output and a spendable balance are not always interchangeable.
The continuing issuance rule appears elsewhere in that release. A function named GetBlockSubsidy begins with 50 bitcoins and determines how many halvings apply from the block's height. It then reduces that starting subsidy by the appropriate number of binary shifts. The main-network parameters set the interval at 210,000 blocks. This is a schedule measured through the chain's accumulated blocks. The comment associates a halving with approximately four years, but the count is the rule. The Bitcoin supply schedule was therefore expressed through an event in the ledger rather than an annual instruction to a monetary authority.
Another part of the validation file enforces the calculated allowance. It combines transaction fees with the permitted subsidy, then compares that total with the value claimed by the block's first transaction. An excessive claim causes rejection under the reason code “bad-cb-amount.” The same file requires the first transaction to be a coinbase transaction and forbids another coinbase later in the block. These restrictions link new issuance to a particular transaction position and a checked maximum. Successful work on a block does not remove the separate requirement that its monetary contents satisfy validation.
The developer documentation clarifies why fees do not enlarge the Bitcoin supply limit. Ordinary transactions consume outputs from previous transactions. If their outputs exceed their inputs, they are rejected; when inputs exceed outputs, the difference can be collected as a transaction fee. That fee consequently comes from previously existing units. The subsidy provides the additional issuance component in the coinbase transaction. The documentation also describes full nodes as independently storing chains containing blocks they have validated. Monetary acceptance is thus tied to repeated checks across participating software, alongside the checks against spending the same output again.
The chain parameters also preserve a separate timing framework: a target spacing of ten minutes and a target timespan of two weeks. The developer guide describes difficulty adjustments every 2,016 blocks using recorded timestamps. That adjustment concerns the work required for later blocks, whereas the 210,000-block interval concerns subsidy reductions. Similar references to block counts can conceal different purposes. One mechanism responds to the pace of block production; the other governs the declining flow of newly created units.
Finally, the project's FAQ distinguishes the Bitcoin supply ceiling from denomination. It identifies 100 million satoshis within one bitcoin and amounts expressed to eight decimal places. Smaller units make it possible to divide a quantity more finely without adding bitcoins to the issuance schedule. The FAQ also distinguishes lost coins from erased ledger entries: coins whose spending keys are unavailable remain recorded but dormant. That distinction limits what an issuance total can say about funds still accessible for transfers.
- Satoshi Nakamoto, Bitcoin: A Peer-to-Peer Electronic Cash System, sections 2–6; original proposal — bitcoin.org
- Bitcoin Core v28.0, src/kernel/chainparams.cpp; genesis block and main-network consensus parameters — raw.githubusercontent.com
- Bitcoin Core v28.0, src/validation.cpp; GetBlockSubsidy, coinbase requirements and ConnectBlock — raw.githubusercontent.com
- Bitcoin developer documentation, Block Chain; independent validation, transaction fees and difficulty — developer.bitcoin.org
- Bitcoin project FAQ; issuance ceiling and satoshi denomination — bitcoin.org