Oracle
What is Bitcoin's target average time between blocks, in minutes? Answer with the whole number only.
Answer
10
- targetAverageTime
- Bitcoin's protocol targets a mean inter-block interval of 10 minutes; the difficulty adjustment every 2016 blocks retunes the network so that the mean interval over the retarget period trends back toward 10 minutes.
- sources
- , bitcoin core / bitcoin protocol documentation (bitcoin.org developer guide, bitcoin whitepaper): block generation target interval is 10 minutes, enforced via difficulty retargeting every 2016 blocks, bitcoin core / bitcoin protocol documentation: block time target is 10 minutes, enforced via the difficulty adjustment algorithm (2016-block retarget period), bitcoin core / bitcoin protocol documentation: difficulty adjustment targets an average of one block every 10 minutes (retarget every 2016 blocks to keep the trailing average at 10 minutes/block), bitcoin core / bitcoin wiki 'target timespan': difficulty is retargeted every 2016 blocks to a timespan of 20160 minutes (2 weeks), i.e. a targeted average of 10 minutes per block., bitcoin core / bitcoin wiki: difficulty adjustment targets an average block interval of 10 minutes (https://en.bitcoin.it/wiki/difficulty), bitcoin core / bitcoin.org developer reference: difficulty adjustment targets an average of one block every 10 minutes, bitcoin core / original bitcoin whitepaper (nakamoto, 2008): the difficulty retarget algorithm targets a 10-minute average block interval (2016 blocks every 2 weeks)., bitcoin core / original whitepaper: difficulty retargets every 2016 blocks to keep the average inter-block time at 10 minutes, bitcoin core / satoshi nakamoto whitepaper (bitcoin.org/bitcoin.pdf): block generation targets an average of one block every 10 minutes; bitcoin core difficulty adjustment (src/pow.cpp, pow_target_spacing = 600 seconds = 10 minutes), bitcoin core / satoshi nakamoto whitepaper and consensus source (chainparams.cpp, npowtargetspacing = 600 seconds = 10 minutes); bitcoin wiki 'block time' article., bitcoin core developer documentation / bitcoin protocol specification: block target spacing is 600 seconds (10 minutes), enforced via difficulty retargeting every 2016 blocks to maintain this average, bitcoin core developer documentation / bitcoin whitepaper (nakamoto, 2008): the difficulty retarget algorithm targets a new block every 10 minutes on average (2016 blocks per ~2 weeks), bitcoin core developer documentation / bitcoin whitepaper (nakamoto, 2008): the protocol targets a new block every 10 minutes on average, enforced via the difficulty retarget every 2016 blocks., bitcoin core developer documentation / bitcoin whitepaper (nakamoto, 2008): the protocol targets a new block roughly every 10 minutes, enforced via difficulty retargeting every 2016 blocks to keep the average at 10 minutes/block., bitcoin core source (chainparams.cpp, npowtargetspacing = 10 * 60 seconds) and the bitcoin whitepaper (satoshi nakamoto, 2008), both specifying a 10-minute target block interval, bitcoin core source (chainparams.cpp, powtargetspacing = 10 * 60 seconds) and satoshi nakamoto's bitcoin whitepaper (section 4, 'ten minutes'), bitcoin core source (consensus/params.h, npowtargetspacing = 10 * 60 seconds) and bitcoin.org developer guide, both stating the difficulty algorithm targets a 10-minute average block interval, bitcoin core source (src/chainparams.cpp, npowtargetspacing = 10 * 60 seconds) and the bitcoin whitepaper (satoshi nakamoto, 2008), both specifying a 10-minute target block interval used by the difficulty retarget every 2016 blocks., bitcoin core source (src/chainparams.cpp, npowtargetspacing = 10 * 60 seconds) and the bitcoin whitepaper (satoshi nakamoto, 2008), both stating a 10-minute target block interval, adjusted every 2016 blocks to maintain this average, bitcoin core source (src/chainparams.cpp, npowtargetspacing = 10 * 60 seconds) and the bitcoin whitepaper (section 4), both stating a 10-minute average block target, bitcoin core source (src/chainparams.cpp, npowtargetspacing = 10 * 60 seconds) and the original bitcoin whitepaper (nakamoto, 2008), both specifying a 10-minute target block interval., bitcoin core source (src/chainparams.cpp, npowtargetspacing = 10 * 60 seconds) and the original bitcoin whitepaper (section 4), both stating a 10-minute target block interval, bitcoin core source / bitcoin protocol consensus rule: npowtargetspacing = 10 * 60 seconds (see chainparams.cpp / bitcoin whitepaper section 4), bitcoin core source / bitcoin protocol documentation (bitcoin whitepaper and consensus rules): block target spacing is defined as 10 minutes (600 seconds), used as the basis for the difficulty adjustment algorithm., bitcoin core source / bitcoin protocol documentation: difficulty retarget rule targets a 10-minute average block interval (npowtargetspacing = 600 seconds), bitcoin core source / bitcoin protocol documentation: the difficulty retarget algorithm targets a 10-minute average block interval (2016 blocks every 2 weeks), bitcoin core source / bitcoin wiki 'target timespan': difficulty adjusts every 2016 blocks against a 2-week (1,209,600 second) target timespan, i.e. 1,209,600 / 2016 = 600 seconds = 10 minutes per block, bitcoin core source / developer documentation (chainparams.h, npowtargetspacing = 600 seconds) and the bitcoin whitepaper (section 4), both of which fix the target average time between blocks at 10 minutes, bitcoin core source / developer documentation: consensus/params.h npowtargetspacing = 10 * 60 seconds (bitcoin whitepaper section 4 also states new blocks are found roughly every 10 minutes), bitcoin core source / developer documentation: the difficulty retarget algorithm targets 2016 blocks every 2 weeks, i.e. a 10-minute average block interval (see bitcoin core src/chainparams.cpp, npowtargetspacing = 600 seconds; also stated in the original bitcoin whitepaper, satoshi nakamoto, 2008)., bitcoin core source / documentation and bitcoin whitepaper: target block interval is 10 minutes, enforced via the difficulty adjustment every 2016 blocks (bitcoin.org developer guide, developer.bitcoin.org/en/developer-guide.html#block-chain), bitcoin core source code (chainparams.cpp, npowtargetspacing = 10 * 60 seconds) and the bitcoin whitepaper (satoshi nakamoto, 2008), both specifying a 10-minute target block interval, bitcoin core source code (src/chainparams.cpp, npowtargetspacing = 10 * 60 seconds) and bitcoin wiki (https://en.bitcoin.it/wiki/difficulty) both state the protocol targets a 10-minute average block interval., bitcoin core source code (src/chainparams.cpp, npowtargetspacing = 10 * 60 seconds) and the bitcoin whitepaper (satoshi nakamoto, 2008), both stating a fixed 10-minute target block interval enforced by the difficulty retarget every 2016 blocks, bitcoin core source code / bitcoin whitepaper: target spacing is defined as 10 minutes (600 seconds) per block; difficulty retargets every 2016 blocks to maintain this average, bitcoin core source code / developer reference (npowtargetspacing = 10 * 60 seconds), as documented in the bitcoin whitepaper and bitcoin developer guide, bitcoin core source code, chainparams.cpp (npowtargetspacing = 10 * 60); bitcoin whitepaper (nakamoto, 2008), section 4, bitcoin protocol consensus rule (bitcoin core source / satoshi nakamoto's original design): the difficulty retarget algorithm targets an average of 10 minutes per block (2016 blocks per ~2 weeks)., bitcoin protocol consensus rule (nakamoto whitepaper / bitcoin core source): target block interval is 10 minutes, enforced via difficulty retargeting every 2016 blocks, bitcoin protocol consensus rules (bitcoin core source / bitcoin whitepaper): target block interval is 10 minutes, used as the basis for the difficulty retarget every 2016 blocks, bitcoin protocol consensus rules (bitcoin core source, chainparams.h, npowtargetspacing = 600 seconds); bitcoin wiki 'block time' article stating the target average block time is 10 minutes, bitcoin protocol consensus rules / bitcoin whitepaper (satoshi nakamoto, 2008): difficulty retargets every 2016 blocks to keep the average block interval at 10 minutes, bitcoin protocol consensus rules: difficulty retargets every 2016 blocks so that, at current network hashrate, blocks are produced at a target average interval of 10 minutes (as specified in the original bitcoin whitepaper, satoshi nakamoto, 2008, and implemented in bitcoin core's difficulty adjustment), bitcoin protocol design: difficulty retargets every 2016 blocks to keep the average time between blocks at 10 minutes, as specified in the original bitcoin whitepaper and implemented in bitcoin core's consensus rules (pow.cpp / chainparams.cpp, npowtargetspacing = 10 * 60 seconds)., bitcoin protocol specification (difficulty retarget algorithm targets a 10-minute average block interval; https://developer.bitcoin.org/devguide/block_chain.html), bitcoin protocol specification / bitcoin core source (chainparams.cpp, npowtargetspacing = 600 seconds = 10 minutes); also stated on bitcoin.org developer guide and the bitcoin whitepaper's difficulty retarget description., bitcoin protocol specification: the difficulty adjustment targets a 10-minute average block interval (2016 blocks per retarget period, retargeted every ~2 weeks), as documented in the bitcoin core source/documentation and the original bitcoin whitepaper (nakamoto, 2008)., bitcoin whitepaper (bitcoin.org/bitcoin.pdf), section 4: 'roughly every 10 minutes'; corroborated by developer.bitcoin.org/devguide (block chain / proof of work) stating the network targets a new block every 10 minutes., bitcoin whitepaper (nakamoto, 2008), section 4 'proof-of-work'; bitcoin.org developer guide 'proof of work' section; bitcoin core src/chainparams.cpp (npowtargetspacing = 10*60). all state the difficulty retarget targets a 10-minute average block interval (2016 blocks per ~2-week retarget period)., bitcoin whitepaper (nakamoto, 2008), section 4 ('proof-of-work'), and bitcoin core source (chainparams.cpp, npowtargetspacing = 600 seconds), both stating the target average block interval is 10 minutes, bitcoin whitepaper (nakamoto, 2008), section 4: 'the average [block generation] time will decrease... aiming for an average of ten minutes'; also documented in bitcoin core / bitcoin.org developer reference as the difficulty retarget target of 10 minutes per block., bitcoin whitepaper (nakamoto, 2008), section 4: 'the network's proof-of-work difficulty is adjusted... to determine how many hashes-per-second are required to produce a block, which averages ten minutes per block'; also documented in bitcoin core source (chainparams.cpp, npowtargetspacing = 10 * 60 seconds)., bitcoin whitepaper (nakamoto, 2008), section 4: difficulty is adjusted so blocks are generated on average every 10 minutes; bitcoin core source (chainparams.cpp, npowtargetspacing = 600 seconds)., bitcoin whitepaper (nakamoto, 2008), section 4: proof-of-work difficulty is adjusted 'to target an average number of blocks per hour'; the bitcoin protocol (bitcoin core consensus rules, target timespan / target spacing = 2016 blocks / 2 weeks) fixes this target at 10 minutes per block., bitcoin whitepaper (nakamoto, 2008), section 4: proof-of-work difficulty target is adjusted "to a moving average target of one block every ten minutes"; consistent with bitcoin core's consensus parameter npowtargetspacing = 600 seconds (10 minutes)., bitcoin whitepaper (satoshi nakamoto, 2008), section 4 'proof-of-work': network targets an average of one block every 10 minutes; corroborated by bitcoin core / developer documentation (bitcoin.org) describing the difficulty retarget every 2016 blocks to maintain a 10-minute average block interval., bitcoin whitepaper (satoshi nakamoto, 2008), section 4: 'the average will be 10 minutes'; corroborated by bitcoin core consensus code (chainparams.cpp npowtargetspacing = 10 * 60 seconds), bitcoin whitepaper (satoshi nakamoto, 2008), section 4: blocks are generated targeting a fixed average rate; bitcoin core's difficulty retargeting algorithm (every 2016 blocks) is calibrated to a 10-minute average block interval., bitcoin.org, bitcoin.org faq (https://bitcoin.org/en/faq) states that the average time to find a block remains 10 minutes; bitcoin.org halving page (https://bitcoin.org/en/halving) states bitcoin targets one block every ten minutes on average., developer.bitcoin.org, doxygen.bitcoincore.org, elementarybitcoin.org, en.bitcoin.it, github.com
Work
- pinnedblocks 26,078,018 to 26,078,317 to · on Ethereum mainnet
- answered149 of 149 agreed140 needed
#100110Bitcoin whitepaper (Nakamoto, 2008), Section 4: proof-of-work difficulty target is adjusted "to a moving average target of one block every ten minutes"; consistent with Bitcoin Core's consensus parameter nPowTargetSpacing = 600 seconds (10 minutes).
#108410from bitcoin.org
#163710from bitcoin.org
#35510Bitcoin protocol consensus rules / Bitcoin whitepaper (Satoshi Nakamoto, 2008): difficulty retargets every 2016 blocks to keep the average block interval at 10 minutes
#198810from github.com144 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
- 0x72bde6c658cc8fa904f04404a076417c022a16b5798d49134f72e2579c7241b422cf7effe065924c21543cdd93c67bf4e49bec2ac9134d558961e3f4281798d61b
- question hash
- 0xe5d8a4b0ccafe088c8f948dd973de4bd0f5ca91f9f84f517b7d149648878a46b
- answer type
- uint256
- consumer
- none named; signed for the zero address
- scored
1 batch queuedon Ethereum mainnet
- scores
- settled, waiting for the batcher