Skip to content
Satoshi Gazette
Data DeskFixed schedule

Supply

The subsidy schedule’s sum through the block last read and at its end, each halving, and the supply events on record, each with its sources.

Bitcoin issued by the subsidy schedule

20,099,390BTC

20,099,390.62500000 BTC through block 971,804, read 17 Oct 2026; the schedule ends at 20,999,999.97690000 BTC

0 BTC20,999,999.97690000 BTC

Each block adds 3.125 BTC until block 1,049,999, then 1.5625 BTC.

The schedule’s sum, not the coins that can move: it counts the genesis block’s 50 BTC and the 100 BTC of the two coinbases later blocks repeated, which cannot be spent, and every subsidy a miner left unclaimed.

Calculation · Subsidy per block in whole satoshis, as Bitcoin Core’s GetBlockSubsidy ·block 971,804, read 17 Oct 2026 ·Difficulty: Full rule →

The halvings so far, and the next

4halvings

at blocks 210,000, 420,000, 630,000 and 840,000; the next is at block 1,050,000, 78,196 blocks after block 971,804

Each halving by its block: the block’s header time and the subsidy on either side
BlockHeader timeSubsidy beforeSubsidy after
210,00050 BTC25 BTC
420,00025 BTC12.5 BTC
630,00012.5 BTC6.25 BTC
840,0006.25 BTC3.125 BTC
1,050,000Not yet mined3.125 BTC1.5625 BTC

Each time is the halving block’s header time, as its miner wrote it. The next halving has a height and no date.

Chain · Header times of blocks 210,000, 420,000, 630,000 and 840,000 ·subsidy as Bitcoin Core’s GetBlockSubsidy ·Difficulty period, halvings and subsidy: Full rule →

The block subsidy, halving by halving

312,500,000sats

per block, 3.125 BTC, to block 1,049,999; 0 sat from block 6,930,000, halving 33

Log scale · each gridline 1,000× the one below · sats per block, by block height · stops at block 6,930,000, where the subsidy reaches 0 sat

The subsidy only: a block’s fees are not in it.

Calculation · 50 BTC halved every 210,000 blocks in whole satoshis, as Bitcoin Core’s GetBlockSubsidy ·Difficulty period, halvings and subsidy: Full rule →

Dates, sources & limits
The subsidy in each era of the schedule
Halvings passedFrom blockSats per block
005,000,000,000
1210,0002,500,000,000
2420,0001,250,000,000
3630,000625,000,000
4840,000312,500,000
51,050,000156,250,000
61,260,00078,125,000
71,470,00039,062,500
81,680,00019,531,250
91,890,0009,765,625
102,100,0004,882,812
112,310,0002,441,406
122,520,0001,220,703
132,730,000610,351
142,940,000305,175
153,150,000152,587
163,360,00076,293
173,570,00038,146
183,780,00019,073
193,990,0009,536
204,200,0004,768
214,410,0002,384
224,620,0001,192
234,830,000596
245,040,000298
255,250,000149
265,460,00074
275,670,00037
285,880,00018
296,090,0009
306,300,0004
316,510,0002
326,720,0001

Summed over these 33 eras: 2,099,999,997,690,000 sat, 20,999,999.97690000 BTC.

Supply events

  1. The genesis block

    Header time , 18:15:05 UTC, as the block states it

    Block 0 has one output, of 50 BTC (5,000,000,000 sat).

    That output cannot be spent.

  2. The value overflow of 2010

    Block time , 17:05:57 UTC; Bitcoin 0.3.10 announced 23:48:22 UTC

    A block at height 74,638 carried a transaction with two outputs of 92,233,720,368.54275808 BTC each, 184,467,440,737.08551616 BTC together, about 184 billion.

    Bitcoin 0.3.10, announced the same day, patched the overflow; the fix is commit d4c6b90.

    That block is not on today’s chain.

  3. BIP 30 and two repeated coinbases

    Repeats at header times of 14 and 15 Nov 2010; BIP 30 assigned 22 Feb 2012, enforced from , 00:00 UTC

    Block 91,842 repeats the coinbase transaction of block 91,812, and block 91,880 repeats that of block 91,722.

    The coinbase outputs of blocks 91,722 and 91,812, 50 BTC each and 100 BTC together, cannot be spent, per the chain and Bitcoin Core’s IsBIP30Unspendable.

    BIP 30 bars a block from containing a transaction whose id matches an earlier, not-fully-spent transaction; blocks 91,842 and 91,880 are its two exceptions.

  4. The chain split of March 2013 (BIP 50)

    ; hashes posted 12 Mar 2013, 01:01:35 UTC

    Block 000000000000015c50b165fcdd33556f8b44800c5298943ac70b112df480c023, at height 225,430, was accepted by Bitcoin 0.8 nodes; some pre-0.8 nodes rejected it, and it was later orphaned.

    Block 225,430 on today’s chain is 00000000000001c108384350f74090433e7fcf79a606b8e797f065b130575932.

    Both hashes were posted to the bitcoin-dev list on 12 Mar 2013.

    BIP 50 states that at least one large double spend took place during the split.

  5. BIP 42

    BIP 42 dated ; pull request #3842 merged 3 Apr 2014

    BIP 42 holds the block subsidy at zero from halving 64, at height 13,440,000, instead of letting it wrap back to 50 BTC.

    Bitcoin Core pull request #3842, which makes that change, was merged on 3 Apr 2014.

    By the schedule’s own arithmetic the subsidy is already 0 sat from halving 33, at height 6,930,000.

  6. CVE-2018-17144

    Fixed 18 Sep 2018; full disclosure

    On Bitcoin Core 0.15.x to 0.16.2, a miner could inflate the supply; on 0.14.x the bug crashed the node.

    Bitcoin Core 0.16.3 and 0.17.0rc4 fixed it on 18 Sep 2018.

    Bitcoin Core’s disclosure of 20 Sep 2018 said it was unaware of any attempts to exploit it.

Reproduce this page1 dataset: 3 node commands

Commands for your own node, each beside what the committed data records, on the chain named by its block 961,632.The chain the figures describe →

  • Difficulty period, halvings and subsidy

    Dataset ID sg-protocol-schedule

    Difficulty period, halvings and subsidy: Full rule →

    Live

    Read when the page loads: on Fees & blocks the newest block height and the retarget projection from mempool.space; on Supply the block the difficulty periods were read through; the rules themselves from Bitcoin Core at one pinned commit. Nothing is saved, so there is no file or download.

    On your node
    1. bitcoin-cli getblockcountPrints the newest block’s height. Divided by 2,016 and rounded down it is the current difficulty period; 2,016 minus the remainder is the blocks left in it.
    2. bitcoin-cli getblockhash 840000Prints the hash of block 840,000, the fourth halving; bitcoin-cli getblockheader with that hash prints the block’s time, 20 Apr 2024, 00:09:27 UTC, the time the halvings table keeps.
    3. bitcoin-cli getblockstats 840000Prints subsidy 312,500,000: the 3.125 BTC each block from 840,000 to 1,049,999 creates.