Bitcoin

On October 31, 2008, Satoshi described electronic cash with no trusted third party. The January 3, 2009 genesis block fixed the network's starting identity; five days later, Satoshi released the Windows-only v0.1 alpha and its C++ source. A design had become software that other people could run, but its monetary promise still depended on validation code correctly limiting every input, output and block reward.

Block 74,638 exposed that dependency on August 15, 2010. Its anomalous transaction carried two outputs of 92,233,720,368.54275808 BTC each—184,467,440,737.08551616 BTC together. The historical fix introduced MAX_MONEY and checked individual and aggregate amounts. Scarcity survived because repaired software rejected the bad history and enough participants built on the repaired chain—not because an issuer reversed an account.

Bitcoin Core's maintainers decide what enters that repository, and its contribution rules call for broad public review of consensus changes. That merge authority produces one software release; it does not rewrite the rules already running on independent nodes. Shared monetary authority emerges only when nodes, miners, wallets and businesses remain compatible.

SegWit made this boundary visible at scale. Bitcoin Core 0.13.1 shipped witness validation as a soft fork; current parameters record mainnet activation at block 481,824 on August 24, 2017. Participants could continue running older compatible software, but only upgraded validators enforced the new witness rules. It was neither a token vote nor a decision one maintainer could impose.

Current code starts subsidy at 50 BTC and halves it every 210,000 blocks. After 32 halvings the subsidy is one satoshi; the 33rd halving makes it zero, setting the scheduled maximum at 20,999,999.9769 BTC. Nodes enforce that schedule by rejecting a coinbase transaction that pays more than subsidy plus fees; the separate 64-halving guard prevents an undefined software operation rather than extending issuance that long.

The overflow repair and SegWit activation expose the same structure. Consensus code defines the 20,999,999.9769 BTC schedule and maintainers can publish a client, but scarcity persists only while independently run nodes reject invalid creation and economic participants converge on compatible history. No issuer guarantees that outcome, and no repository merge can achieve it alone.

Each halving reduces the subsidy until it reaches zero, shifting miner revenue toward transaction fees. Whether future fees support enough hash power remains an unresolved market outcome. Spot ETP shares widened regulated access in 2024, but their issuers, custodians, fees and product rights sit outside that consensus process; a wrapper neither changes native validation nor solves Bitcoin’s future security budget.