Bitcoin Core relies on BIP 34 to skip BIP 30 duplicate-transaction lookups only below block 1,983,702, its constant BIP34_IMPLIES_BIP30_LIMIT; from that height on it enforces the BIP 30 check again, because some coinbase transactions from before BIP 34 could otherwise be repeated.
Sources and checks
T1Bitcoin Core src/validation.cpp, ConnectBlockSource code, says this directly
if (fEnforceBIP30 || pindex->nHeight >= BIP34_IMPLIES_BIP30_LIMIT) {
Chainstate::ConnectBlock, BIP30 enforcement condition, read 2026-11-20
T1Bitcoin Core src/validation.cpp, BIP34_IMPLIES_BIP30_LIMIT commentSource code, says this directly
greater than 1,983,702, so we simply remove the optimization to skip
Chainstate::ConnectBlock, comment above BIP34_IMPLIES_BIP30_LIMIT, 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.
Duplicate transaction vector, 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 'static constexpr int BIP34_IMPLIES_BIP30_LIMIT = 1983702;'Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 3/3, code 1/1
History
Nothing is edited silently; every revision keeps what it replaced.
- 20 Nov 2026, 16:42 UTCblock 976,753
Published Revision 1, run 2026-11-20-seed-utxo-model