Halvings and the supply schedule
Reading as Holder. What matters when you hold your own coins.14 of 23 claims
What it isCurious
Bitcoin halvings are counted in blocks, not dates: the subsidy halves every 210,000 blocks, which Bitcoin Core's source code describes as occurring approximately every four years.1: open 1 source
FactCuriousEstablishedHigh confidence
T1Bitcoin Core src/validation.cpp, GetBlockSubsidySource code, says this directly
Subsidy is cut in half every 210,000 blocks which will occur approximately every 4 years.
GetBlockSubsidy, comment, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'Subsidy is cut in half every 210,000 blocks which will occur approximately every 4 years.'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 1/1, code 1/1History, hash and citation
Bitcoin's block subsidy started at 50 BTC per block: the genesis block was created with a 50 BTC coinbase, and the rules allowed a 50 BTC subsidy for every block up to block 209,999.2: open 3 sources
FactCuriousEstablishedHigh confidence
T1Bitcoin Core src/validation.cpp, GetBlockSubsidySource code, says this directly
CAmount nSubsidy = 50 * COIN;
GetBlockSubsidy, read 2026-11-20
T1Bitcoin Core src/kernel/chainparams.cpp, mainnet genesis blockSource code, says this directly
genesis = CreateGenesisBlock(1231006505, 2083236893, 0x1d00ffff, 1, 50 * COIN);
CMainParams, genesis block, read 2026-11-20
T1Coinbase subsidy of blocks 1 and 209,999The chain, says this directly
Blocks 1 and 209,999 coinbase outputs minus fees, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'CAmount nSubsidy = 50 * COIN;'Block 1 created 5,000,000,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 1 '["subsidy"]'Block 209,999 created 5,000,000,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 209999 '["subsidy"]'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 3/3, code 1/1, chain 2/2 (esplora pair agreed)History, hash and citation
The halvings so farUser
Bitcoin's first halving took effect at block 210,000, timestamped 28 November 2012, cutting the block subsidy from 50 BTC to 25 BTC per block.3: open 2 sources
EventUserEstablishedHigh confidence
T1Block 210,000The chain, says this directly
Block 210,000 header time and coinbase subsidy, blocks 209,999 and 210,000, read 2026-11-20
T1Bitcoin Core src/validation.cpp, GetBlockSubsidySource code, supports part of it
int halvings = nHeight / consensusParams.nSubsidyHalvingInterval;
GetBlockSubsidy, read 2026-11-20
Block 209,999 created 5,000,000,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 209999 '["subsidy"]'Block 210,000 created 2,500,000,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 210000 '["subsidy"]'Block 210,000 has hash 000000000000048b...
Run it yourself
bitcoin-cli getblockhash 210000Block 210,000's header has time = 1354116278.
Run it yourself
bitcoin-cli getblockheader $(bitcoin-cli getblockhash 210000) | grep '"time"'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, chain 4/4 (esplora pair agreed)History, hash and citation
Bitcoin's second halving took effect at block 420,000, timestamped 9 July 2016, cutting the block subsidy from 25 BTC to 12.5 BTC per block.4: open 2 sources
EventUserEstablishedHigh confidence
T1Block 420,000The chain, says this directly
Block 420,000 header time and coinbase subsidy, blocks 419,999 and 420,000, read 2026-11-20
T1Bitcoin Core src/validation.cpp, GetBlockSubsidySource code, supports part of it
int halvings = nHeight / consensusParams.nSubsidyHalvingInterval;
GetBlockSubsidy, read 2026-11-20
Block 419,999 created 2,500,000,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 419999 '["subsidy"]'Block 420,000 created 1,250,000,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 420000 '["subsidy"]'Block 420,000 has hash 0000000000000000...
Run it yourself
bitcoin-cli getblockhash 420000Block 420,000's header has time = 1468082773.
Run it yourself
bitcoin-cli getblockheader $(bitcoin-cli getblockhash 420000) | grep '"time"'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, chain 4/4 (esplora pair agreed)History, hash and citation
Bitcoin's third halving took effect at block 630,000, timestamped 11 May 2020, cutting the block subsidy from 12.5 BTC to 6.25 BTC per block.5: open 2 sources
EventUserEstablishedHigh confidence
T1Block 630,000The chain, says this directly
Block 630,000 header time and coinbase subsidy, blocks 629,999 and 630,000, read 2026-11-20
T1Bitcoin Core src/validation.cpp, GetBlockSubsidySource code, supports part of it
int halvings = nHeight / consensusParams.nSubsidyHalvingInterval;
GetBlockSubsidy, read 2026-11-20
Block 629,999 created 1,250,000,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 629999 '["subsidy"]'Block 630,000 created 625,000,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 630000 '["subsidy"]'Block 630,000 has hash 0000000000000000...
Run it yourself
bitcoin-cli getblockhash 630000Block 630,000's header has time = 1589225023.
Run it yourself
bitcoin-cli getblockheader $(bitcoin-cli getblockhash 630000) | grep '"time"'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, chain 4/4 (esplora pair agreed)History, hash and citation
Bitcoin's fourth halving took effect at block 840,000, timestamped 20 April 2024, cutting the block subsidy from 6.25 BTC to 3.125 BTC per block.6: open 2 sources
EventUserEstablishedHigh confidence
T1Block 840,000The chain, says this directly
Block 840,000 header time and coinbase subsidy, blocks 839,999 and 840,000, read 2026-11-20
T1Bitcoin Core src/validation.cpp, GetBlockSubsidySource code, supports part of it
int halvings = nHeight / consensusParams.nSubsidyHalvingInterval;
GetBlockSubsidy, read 2026-11-20
Block 839,999 created 625,000,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 839999 '["subsidy"]'Block 840,000 created 312,500,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 840000 '["subsidy"]'Block 840,000 has hash 0000000000000000...
Run it yourself
bitcoin-cli getblockhash 840000Block 840,000's header has time = 1713571767.
Run it yourself
bitcoin-cli getblockheader $(bitcoin-cli getblockhash 840000) | grep '"time"'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, chain 4/4 (esplora pair agreed)History, hash and citation
As of block 976,751 (20 November 2026), Bitcoin's block subsidy is 3.125 BTC (312,500,000 sats) per block, the amount set by the fourth halving at block 840,000.7: open 2 sources
FactUserEstablishedHigh confidence
T1Coinbase subsidy of block 976,751The chain, says this directly
Blocks 840,000 and 976,751 coinbase outputs minus fees, read 2026-11-20
T1Bitcoin Core src/validation.cpp, GetBlockSubsidySource code, supports part of it
int halvings = nHeight / consensusParams.nSubsidyHalvingInterval;
GetBlockSubsidy, read 2026-11-20
Block 976,751 created 312,500,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 976751 '["subsidy"]'Block 840,000 created 312,500,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 840000 '["subsidy"]'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, chain 2/2 (esplora pair agreed)History, hash and citation
Bitcoin's fifth halving is set by the 210,000-block interval to take effect at block 1,050,000, cutting the block subsidy from 3.125 BTC to 1.5625 BTC. As of block 976,751, that height is 73,249 blocks away.8: open 2 sources
FactUserEstablishedHigh confidence
T1Bitcoin Core src/kernel/chainparams.cpp, mainnet halving intervalSource code, says this directly
consensus.nSubsidyHalvingInterval = 210000;
CMainParams, nSubsidyHalvingInterval, read 2026-11-20
T1Bitcoin Core src/validation.cpp, GetBlockSubsidySource code, says this directly
int halvings = nHeight / consensusParams.nSubsidyHalvingInterval;
GetBlockSubsidy, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/kernel/chainparams.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/chainparams.cpp | grep -nF 'consensus.nSubsidyHalvingInterval = 210000;'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, code 1/1History, hash and citation
A Bitcoin miner pays itself through the block's coinbase transaction, which may claim at most the block subsidy plus the fees of the block's transactions. Nodes reject a block whose coinbase claims more than that total.9: open 2 sources
How it worksUserEstablishedHigh confidence
T1Bitcoin Core src/validation.cpp, ConnectBlock coinbase limitSource code, says this directly
CAmount blockReward = nFees + GetBlockSubsidy(pindex->nHeight, params.GetConsensus());
ConnectBlock, blockReward and bad-cb-amount, read 2026-11-20
T1Bitcoin Core src/validation.cpp, ConnectBlock coinbase limitSource code, says this directly
if (block.vtx[0]->GetValueOut() > blockReward && state.IsValid()) {
ConnectBlock, the check that rejects an overpaying coinbase, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'CAmount blockReward = nFees + GetBlockSubsidy(pindex->nHeight, params.GetConsensus());'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, code 1/1History, hash and citation
The supply limitHolder
Bitcoin Core's MAX_MONEY constant of 21,000,000 BTC is a sanity check on amounts, not the total money supply: its source comment says the supply in Bitcoin currently happens to be less than 21,000,000 BTC for various reasons.10: open 2 sources
FactHolderEstablishedHigh confidence
T1Bitcoin Core src/consensus/amount.h, MAX_MONEYSource code, says this directly
Note that this constant is *not* the total money supply, which in Bitcoin
MAX_MONEY comment, read 2026-11-20
T1Bitcoin Core src/consensus/amount.h, MAX_MONEYSource code, says this directly
inline constexpr CAmount MAX_MONEY{21'000'000 * COIN};
MAX_MONEY definition, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/consensus/amount.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/consensus/amount.h | grep -nF 'inline constexpr CAmount MAX_MONEY{21'"'"'000'"'"'000 * COIN};'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, code 1/1History, hash and citation
If every block claimed its full subsidy, Bitcoin's schedule would issue 2,099,999,997,690,000 sats (20,999,999.9769 BTC) in total, 0.0231 BTC under 21 million, because each halving shifts the subsidy in whole satoshis and drops any half satoshi.11: open 2 sources
How it worksHolderEstablishedLow confidence
T1Bitcoin Core src/validation.cpp, GetBlockSubsidySource code, supports part of it
nSubsidy >>= halvings;
GetBlockSubsidy, right shift of the satoshi amount, read 2026-11-20
T3Strike, How many bitcoin are there?Media, says this directly
According to the supply schedule, the actual predetermined limit is 20,999,999.9769 bitcoin
Section on the supply limit, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'nSubsidy >>= halvings;'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, code 1/1History, hash and citation
Because Bitcoin's 50 BTC starting subsidy is 5,000,000,000 sats, shifting it right 32 times leaves 1 sat and 33 times leaves 0. The subsidy is therefore 1 sat for blocks 6,720,000 to 6,929,999 and zero from block 6,930,000 on.12: open 2 sources
How it worksHolderEstablishedMedium confidence
T1Bitcoin Core src/validation.cpp, GetBlockSubsidySource code, says this directly
nSubsidy >>= halvings;
GetBlockSubsidy, right shift of the satoshi amount, read 2026-11-20
T1Bitcoin Core src/consensus/amount.h, COINSource code, says this directly
inline constexpr CAmount COIN{100'000'000};
COIN, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'CAmount nSubsidy = 50 * COIN;'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, code 1/1History, hash and citation
The amount of bitcoin in existence is not a function of block height alone, because some allowed rewards were never claimed and some issued coins are provably unspendable. A Bitcoin Core node reports the total from its own UTXO set: the gettxoutsetinfo RPC returns total_amount, the total of all unspent outputs.13: open 2 sources
How it worksHolderEstablishedHigh confidence
T1Bitcoin Core src/rpc/blockchain.cpp, gettxoutsetinfoSource code, says this directly
The total amount of coins in the UTXO set
gettxoutsetinfo, RPCResult total_amount, read 2026-11-20
T1Bitcoin Core src/rpc/blockchain.cpp, gettxoutsetinfoSource code, supports part of it
The total amount of coins permanently excluded from the UTXO set (only available if coinstatsindex is used)
gettxoutsetinfo, RPCResult total_unspendable_amount, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/rpc/blockchain.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/rpc/blockchain.cpp | grep -nF 'The total amount of coins in the UTXO set'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, code 1/1History, hash and citation
In the codeBuilder
Bitcoin Core computes the block subsidy in GetBlockSubsidy (src/validation.cpp): it divides the height by nSubsidyHalvingInterval, which mainnet sets to 210,000, and shifts 50 BTC, expressed in satoshis, right by that many halvings.14: open 2 sources
TraceBuilderEstablishedHigh confidence
T1Bitcoin Core src/validation.cpp, GetBlockSubsidySource code, says this directly
int halvings = nHeight / consensusParams.nSubsidyHalvingInterval;
GetBlockSubsidy, read 2026-11-20
T1Bitcoin Core src/kernel/chainparams.cpp, mainnet halving intervalSource code, says this directly
consensus.nSubsidyHalvingInterval = 210000;
CMainParams, nSubsidyHalvingInterval, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/kernel/chainparams.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/chainparams.cpp | grep -nF 'consensus.nSubsidyHalvingInterval = 210000;'bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'int halvings = nHeight / consensusParams.nSubsidyHalvingInterval;'Block 840,000 created 312,500,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 840000 '["subsidy"]'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, code 2/2, chain 1/1 (esplora pair agreed)History, hash and citation
Bitcoin's consensus rules cap a coinbase's claim at subsidy plus fees but set no minimum, so a miner can claim less. An amount left unclaimed is never paid to anyone, and Bitcoin Core's gettxoutsetinfo reports such amounts under unclaimed_rewards.15: open 2 sources
How it worksBuilderEstablishedHigh confidence
T1Bitcoin Core src/validation.cpp, ConnectBlock coinbase limitSource code, says this directly
if (block.vtx[0]->GetValueOut() > blockReward && state.IsValid()) {
ConnectBlock, the only check on the coinbase value is an upper bound, read 2026-11-20
T1Bitcoin Core src/rpc/blockchain.cpp, gettxoutsetinfoSource code, says this directly
Fee rewards that miners did not claim in their coinbase transaction
gettxoutsetinfo, RPCResult unspendables.unclaimed_rewards, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/rpc/blockchain.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/rpc/blockchain.cpp | grep -nF 'Fee rewards that miners did not claim in their coinbase transaction'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, code 1/1History, hash and citation
The 50 BTC coinbase of Bitcoin's genesis block cannot be spent: Bitcoin Core skips connecting the genesis block's transactions, so that output never enters the UTXO set, and gettxoutsetinfo lists it as unspendable.16: open 3 sources
FactBuilderEstablishedHigh confidence
T1Bitcoin Core src/validation.cpp, ConnectBlock genesis special caseSource code, says this directly
(its coinbase is unspendable)
ConnectBlock, special case for the genesis block, read 2026-11-20
T1Bitcoin Core src/rpc/blockchain.cpp, gettxoutsetinfoSource code, says this directly
The unspendable amount of the Genesis block subsidy
gettxoutsetinfo, RPCResult unspendables.genesis_block, read 2026-11-20
T1Bitcoin Core src/kernel/chainparams.cpp, mainnet genesis blockSource code, supports part of it
genesis = CreateGenesisBlock(1231006505, 2083236893, 0x1d00ffff, 1, 50 * COIN);
CMainParams, genesis block, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'Special case for the genesis block, skipping connection of its transactions'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 3/3, code 1/1History, hash and citation
Blocks 91,842 and 91,880 contain coinbase transactions identical to earlier ones, which was possible before BIP 30 because early coinbases were easy to duplicate. BIP 30 forbids such duplicates in all blocks except these two, and Bitcoin Core exempts them in IsBIP30Repeat.17: open 3 sources
TraceBuilderEstablishedHigh confidence
T1BIP 30, Duplicate transactionsBIP, says this directly
to apply to all blocks except the two historic blocks at heights 91842 and 91880 on the main chain
Specification, read 2026-11-20
T1BIP 30, Duplicate transactionsBIP, says this directly
in particular coinbases are easy to duplicate
Motivation, read 2026-11-20
T1Bitcoin Core src/validation.cpp, IsBIP30RepeatSource code, says this directly
return (block_index.nHeight==91842 && block_index.GetBlockHash() == uint256{
IsBIP30Repeat, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'bool fEnforceBIP30 = !IsBIP30Repeat(*pindex);'Block 91,842 has hash 00000000000a4d0a...
Run it yourself
bitcoin-cli getblockhash 91842Block 91,880 has hash 00000000000743f1...
Run it yourself
bitcoin-cli getblockhash 91880BIP 30's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0030.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 3/3, code 2/2, chain 2/2 (esplora pair agreed)History, hash and citation
The 50 BTC coinbase outputs of blocks 91,722 and 91,812 can never be spent, because identical coinbases mined later, in blocks 91,842 and 91,880, overwrote them. Bitcoin Core marks them in IsBIP30Unspendable, and gettxoutsetinfo with coinstatsindex reports them in its bip30 total.18: open 3 sources
FactBuilderEstablishedHigh confidence
T1Bitcoin Core src/validation.cpp, IsBIP30UnspendableSource code, says this directly
return (block_height==91722 && block_hash == uint256{
IsBIP30Unspendable, read 2026-11-20
T1Bitcoin Core src/rpc/blockchain.cpp, gettxoutsetinfoSource code, says this directly
Transactions overridden by duplicates (no longer possible with BIP30)
gettxoutsetinfo, RPCResult unspendables.bip30, read 2026-11-20
T1Coinbase subsidy of blocks 91,722 and 91,812The chain, says this directly
Blocks 91,722 and 91,812 block hashes and coinbase outputs, read 2026-11-20
Block 91,722 has hash 00000000000271a2...
Run it yourself
bitcoin-cli getblockhash 91722Block 91,812 has hash 00000000000af0ae...
Run it yourself
bitcoin-cli getblockhash 91812Block 91,722 created 5,000,000,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 91722 '["subsidy"]'Block 91,812 created 5,000,000,000 sats of new coins.
Run it yourself
bitcoin-cli getblockstats 91812 '["subsidy"]'bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'return (block_height==91722 && block_hash == uint256{'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 3/3, code 1/1, chain 4/4 (esplora pair agreed)History, hash and citation
Specifications and historyResearcher
BIP 42 noted that Bitcoin's subsidy code shifted by the halving count, a shift undefined in C++ from 64 on, so the subsidy could repeat its cycle every 64 halvings. Bitcoin Core's GetBlockSubsidy now returns zero from 64 halvings on, keeping the supply finite.19: open 2 sources
TraceResearcherEstablishedHigh confidence
T1BIP 42, A finite monetary supply for BitcoinBIP, says this directly
the cycle repeats itself every 64 halvings on all currently supported platforms.
Details, read 2026-11-20
T1Bitcoin Core src/validation.cpp, GetBlockSubsidySource code, says this directly
Force block reward to zero when right shift is undefined.
GetBlockSubsidy, guard on the shift, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'Force block reward to zero when right shift is undefined.'BIP 42's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0042.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, code 2/2History, hash and citation
BIP 34 requires each block's height as the first item of its coinbase scriptSig, a rule its stated motivation ties to enforcing block and transaction uniqueness. Bitcoin Core's mainnet parameters set BIP34Height to block 227,931.20: open 3 sources
TraceResearcherEstablishedHigh confidence
T1BIP 34, Block v2, Height in CoinbaseBIP, says this directly
Add height as the first item in the coinbase transaction's scriptSig, and increase block version to 2.
Specification, read 2026-11-20
T1BIP 34, Block v2, Height in CoinbaseBIP, says this directly
Enforce block and transaction uniqueness, and assist unconnected block validation.
Motivation, read 2026-11-20
T1Bitcoin Core src/kernel/chainparams.cpp, BIP34HeightSource code, says this directly
consensus.BIP34Height = 227931;
CMainParams, BIP34Height, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/kernel/chainparams.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/chainparams.cpp | grep -nF 'consensus.BIP34Height = 227931;'Block 227,931 has hash 000000000000024b...
Run it yourself
bitcoin-cli getblockhash 227931BIP 34's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0034.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 3/3, code 2/2, chain 1/1 (esplora pair agreed)History, hash and citation
BIP 34 does not rule out every duplicate coinbase: some early coinbases could be replayed in future blocks, so Bitcoin Core enforces BIP 30 checks again from block 1,983,702 on. BIP 54 (consensus cleanup), a proposed soft fork whose BIP status is Complete as of 20 November 2026, specifies that each coinbase's nLockTime equal the block height minus 1.21: open 3 sources
TraceResearcherEstablishedHigh confidence
T1Bitcoin Core src/validation.cpp, ConnectBlock BIP30 enforcementSource code, says this directly
TODO: Remove BIP30 checking from block height 1,983,702 on, once we have a
ConnectBlock, comment on BIP34_IMPLIES_BIP30_LIMIT, read 2026-11-20
T1BIP 54, Consensus CleanupBIP, says this directly
The coinbase transaction's `nLockTime` field must be set to the height of the block minus 1
Specification, coinbase transactions, read 2026-11-20
T2Bitcoin Optech topic, Consensus cleanup soft forkBitcoin Optech, says this directly
Some early coinbase transactions exhibit patterns that would allow them to be replayed in future blocks.
Topic summary, duplicate transactions, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'if (fEnforceBIP30 || pindex->nHeight >= BIP34_IMPLIES_BIP30_LIMIT) {'BIP 54's Status is "Complete" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0054.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 3/3, code 2/2History, hash and citation