Oracle
Every how many blocks does Bitcoin adjust its mining difficulty? Answer with the whole number only.
Answer
2,016
2016 uint256
- difficulty adjustment interval
- The Bitcoin network's scheduled proof-of-work difficulty retarget period, counted in blocks; answer the stated interval, not the number of timestamp intervals used in its calculation.
- sources
- developer.bitcoin.org, bitcoin core consensus parameters (chainparams.cpp, difficultyadjustmentinterval() = npowtargettimespan / npowtargetspacing = 2 weeks / 10 min = 2016 blocks); corroborated by the bitcoin developer guide / bitcoin wiki description of the difficulty retarget occurring every 2016 blocks., bitcoin core consensus parameters (chainparams.cpp, npowtargettimespan / npowtargetspacing = 2016 blocks); documented at developer.bitcoin.org block chain / target difficulty reference, bitcoin core consensus parameters (difficultyadjustmentinterval = 14 days / 10 minutes = 2016 blocks) and the bitcoin wiki / bitcoin developer guide statement that difficulty is retargeted every 2016 blocks, bitcoin core consensus rules (chainparams.cpp, difficultyadjustmentinterval = npowtargettimespan / npowtargetspacing = 2016), as documented in the bitcoin developer guide / bitcoin wiki, bitcoin core consensus rules (chainparams.cpp, npowtargettimespan / npowtargetspacing = 2016); documented in the bitcoin protocol/whitepaper-derived difficulty adjustment algorithm, bitcoin core consensus rules (npowtargettimespan / 2016-block retarget interval), as documented in the bitcoin protocol specification and bitcoin core source (chainparams.cpp difficultyadjustmentinterval), bitcoin core consensus rules (src/chainparams.cpp, npowtargettimespan / npowtargetspacing = 2016 blocks per difficulty adjustment period); consistent with the bitcoin developer guide / bitcoin wiki description of the difficulty retarget occurring every 2016 blocks (~2 weeks)., bitcoin core consensus rules (src/pow.cpp, calculatenextworkrequired): difficulty retargets every 2016 blocks (difficultyadjustmentinterval = npowtargettimespan / npowtargetspacing = 14 days / 10 minutes = 2016), bitcoin core consensus rules / bitcoin whitepaper and protocol documentation: difficulty retarget interval is fixed at 2016 blocks (~every two weeks at the 10-minute target block time)., bitcoin core consensus source (difficultyadjustmentinterval = 2016 blocks, src/chainparams.cpp / src/pow.cpp), as described in the bitcoin developer guide / bitcoin wiki difficulty page, bitcoin core consensus source (src/chainparams.cpp, difficultyadjustmentinterval() = npowtargettimespan / npowtargetspacing = 2016), as documented in the bitcoin developer guide / bitcoin wiki 'difficulty' article, bitcoin core developer documentation / protocol consensus rules (src/chainparams.cpp, difficultyadjustmentinterval = npowtargettimespan / npowtargetspacing = 2016 blocks), bitcoin core protocol consensus rules (npowtargettimespan / difficulty adjustment interval = 2016 blocks, i.e. every ~2 weeks assuming 10-minute blocks); see also the bitcoin whitepaper/core source `src/pow.cpp` getnextworkrequired and bitcoin wiki 'difficulty' article., bitcoin core source (chainparams.cpp, ndifficultyadjustmentinterval = 2016) and bitcoin developer guide / bitcoin wiki documentation on difficulty retargeting, both stating the interval is fixed at 2016 blocks (approximately every two weeks at the 10-minute target block time), bitcoin core source (src/pow.cpp, difficultyadjustmentinterval = npowtargettimespan / npowtargetspacing = 2016), consistent with the bitcoin whitepaper/protocol documentation describing difficulty retargeting every 2016 blocks (~2 weeks at 10 min/block), bitcoin core source code / consensus rules (src/chainparams.cpp, npowtargettimespan = 14 * 24 * 60 * 60 seconds, npowtargetspacing = 10 * 60 seconds => difficultyadjustmentinterval() = 2016 blocks); also documented in the bitcoin developer guide / bitcoin.org developer reference on target difficulty retargeting., bitcoin core source, chainparams.cpp (difficultyadjustmentinterval = npowtargettimespan / npowtargetspacing = 2016); corroborated by the bitcoin developer guide/bitcoin wiki 'difficulty' page, which states the network retargets difficulty every 2016 blocks (~2 weeks at the 10-minute target block time)., bitcoin core source, src/consensus/params.h: difficultyadjustmentinterval() = npowtargettimespan / npowtargetspacing = (14 * 24 * 60 * 60) / (10 * 60) = 2016; applied in src/pow.cpp getnextworkrequired when (nheight % difficultyadjustmentinterval()) == 0., bitcoin core source, src/consensus/params.h: difficultyadjustmentinterval() = npowtargettimespan / npowtargetspacing = (14*24*60*60) / (10*60) = 2016; applied in src/pow.cpp getnextworkrequired (retarget when (height % interval) == 0). also documented in the bitcoin wiki 'difficulty' page and bitcoin developer guide., bitcoin core source, src/pow.cpp, difficultyadjustmentinterval() = params().difficultyadjustmentinterval() = npowtargettimespan / npowtargetspacing = 2016 (also documented in the bitcoin developer guide's 'target nbits' / retargeting section), bitcoin core source/consensus parameters (chainparams.cpp difficultyadjustmentinterval = npowtargettimespan / npowtargetspacing = 2016), as documented in the bitcoin developer guide / bitcoin wiki difficulty retargeting description., bitcoin core, version bits faq for miners: https://bitcoincore.org/en/2016/06/08/version-bits-miners-faq/, bitcoin developer guide (developer.bitcoin.org/reference/block_chain.html, 'target nbits') and the bitcoin core source (chainparams.cpp, difficultyadjustmentinterval() = npowtargettimespan / npowtargetspacing = 2016), both stating the network retargets difficulty every 2016 blocks (~2 weeks at the 10-minute target spacing), bitcoin developer guide, block chain, proof of work (https://developer.bitcoin.org/devguide/block_chain.html); bitcoin core, version bits faq for miners (https://bitcoincore.org/en/2016/06/08/version-bits-miners-faq/), bitcoin developer guide, block chain: https://developer.bitcoin.org/devguide/block_chain.html, bitcoin developer guide, block chain: https://developer.bitcoin.org/devguide/block_chain.html (states the network recalculates difficulty every 2,016 blocks)., bitcoin difficulty retargets every 2016 blocks, per https://lightspark.com/glossary/difficulty-adjustment and https://www.learnbitcoin.com/glossary/difficulty-retargeting, bitcoin protocol specification: difficulty retargets every 2016 blocks (originally documented in bitcoin core source, e.g. chainparams.cpp difficultyadjustmentinterval, and the bitcoin developer guide / bitcoin wiki 'difficulty' page), bitcoin wiki, en.bitcoin.it/wiki/difficulty: 'every 2016 blocks', bitcoin-rpc.github.io, bitcoincore.org, btcinformation.org, elementarybitcoin.org, en.bitcoin.it, github.com, lightspark glossary, 'the purpose and power of bitcoin's difficulty adjustment' (https://www.lightspark.com/glossary/difficulty-adjustment); corroborated by the bitcoin wiki 'difficulty' page (https://bitcoinwiki.org/wiki/difficulty). both state the difficulty is recalibrated every 2016 blocks, about two weeks.
Work
- pinnedblocks 26,115,434 to 26,115,733 to · on Ethereum mainnet
- answered144 of 144 agreed140 needed
#3092,016from developer.bitcoin.org
#12852,016from developer.bitcoin.org
#13102,016from developer.bitcoin.org
#10492,016from developer.bitcoin.org
#18442,016from developer.bitcoin.org139 more
- signed
by the attester 0x5598…2982expired
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0xeb402145122950391c078dfcceae19b2144ce2741910e5910746cd32711d1ef05ef7d8b405a69b2a0d7c804cadc6e6979c6c06378c43210dd334ff466d11fd3c1c
- signed panel
- 144 agreed · quorum 140 · 200 seats
- question hash
- 0xe91511ccfb75c41df11f1883f2c751208dacef45c88cdfd70fe66969a946ea65
- answer type
- uint256
- consumer
- none named; signed for the zero address