The 2009 launch announcement made supply a code rule

Inherited archive entry · retained from the earlier edition. Its factual, legal and policy claims have not all been reverified for 19 September 2026. Research scope.

What the announcement claims and how it phrases it

Satoshi Nakamoto posted 'Bitcoin v0.1 released' to the Cryptography mailing list on 8 January 2009, describing a new electronic cash system that uses a peer-to-peer network to prevent double-spending, and stating the issuance schedule outright: 10,500,000 coins in the first four years, halving every four years after, for a total circulation of 21,000,000 coins. The post reads as a product announcement, a download link, a supported platform, an invitation to try the software, sitting alongside a specific numerical claim about the total money supply that would ever exist.

Distinguishing a stated plan from an enforced rule

A number in a mailing list post is not, by itself, a guarantee; an author can announce any target and later ship something different. What makes the 21 million figure durable is that the schedule described in the post corresponds to a rule enforced by every node's independent validation, not by continued trust in the author. The whitepaper that accompanied the release specifies the mechanism generating new coins, a fixed reward attached to each mined block, and the current Bitcoin developer reference still documents that reward halving every 210,000 blocks, the same roughly four-yearly cadence Nakamoto described in plain language in 2009. A node that received a block paying more than the scheduled reward would reject it regardless of who mined it or what any announcement claimed.

What the announcement does not settle

The 2009 post is a statement of intent and a description of code as it existed that week; it is not proof the schedule could never change. Bitcoin's supply schedule is a consensus rule like any other, alterable in principle by a coordinated change every validating node adopts; the constraint is social and economic, not physical. The announcement also says nothing about later disputes over how the system should scale or govern itself; it predates those debates entirely and should not be read as having settled them in advance.

• Is a supply figure a property of the software everyone runs, or a claim made by whoever is speaking?
• What would have to happen for validating nodes to accept a different schedule than the one announced?
• Does an early technical document bind later versions of the same project to its stated intentions?

The durability of the 21 million figure comes from more than a decade of independent nodes continuing to enforce it, not from the fact that it was written down first.