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.
Sources and checks
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/2
History
Nothing is edited silently; every revision keeps what it replaced.
- 20 Nov 2026, 16:20 UTCblock 976,753
Published Revision 1, run 2026-11-20-seed-halvings-and-supply