Bitcoin mainnet recalculates its proof-of-work target every 2,016 blocks: Bitcoin Core derives this interval as the target timespan of two weeks (1,209,600 seconds) divided by the target block spacing of 600 seconds.
Sources and checks
T1Bitcoin Core src/consensus/params.h, DifficultyAdjustmentIntervalSource code, says this directly
int64_t DifficultyAdjustmentInterval() const { return nPowTargetTimespan / nPowTargetSpacing; }
Consensus::Params::DifficultyAdjustmentInterval, read 2026-11-20
T1Bitcoin Core src/kernel/chainparams.cpp, mainnet nPowTargetTimespanSource code, says this directly
consensus.nPowTargetTimespan = 14 * 24 * 60 * 60; // two weeks
CMainParams, consensus.nPowTargetTimespan, read 2026-11-20
T2Block arrivals in the Bitcoin blockchain (arXiv:1801.07447)Paper, says this directly
The difficulty of the computational problem is updated every 2,016 blocks in order to control the rate at which blocks are generated.
Abstract, 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.nPowTargetTimespan = 14 * 24 * 60 * 60; // two weeks'bitcoin/bitcoin at f498a5a671 contains this text in src/consensus/params.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/params.h | grep -nF 'int64_t DifficultyAdjustmentInterval() const { return nPowTargetTimespan / nPowTargetSpacing; }'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 3/3, code 2/2
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-proof-of-work