IMD

Oracle

9931c828signed

What is Bitcoin's target average block time, in seconds?

Answer

600
answer
the number, as a whole number with no separators
source
Answer from a reputable public source you actually read (the Bitcoin or Ethereum documentation, the EIP repository, chainlist.org, or a major reference) and name it.
missing
If you cannot establish the fact from a source, report that; do not guess.
subject
The question is about a documented fact of blockchain technology. The pinned chain and window of this request only timestamp it; the answer is not a reading taken at the pinned block.
sources
en.bitcoin.it, bitcoin core / bitcoin.org developer guide (block chain / proof of work section): target block time is 10 minutes (600 seconds), maintained by adjusting difficulty every 2016 blocks., bitcoin core chainparams.cpp (npowtargetspacing = 10 * 60 seconds) as described in the bitcoin developer guide / bitcoin wiki 'block time' article, which states bitcoin's difficulty adjustment targets an average of one block every 10 minutes (600 seconds)., bitcoin core developer documentation (bitcoin.org/en/developer-guide) — difficulty retarget section stating the protocol targets a 600 second (10 minute) average block interval, enforced by adjusting difficulty every 2016 blocks., bitcoin core source (chainparams.cpp, npowtargetspacing = 10 * 60 = 600 seconds) and the bitcoin wiki 'difficulty' article, which describe the protocol's target average block interval of 10 minutes (600 seconds), enforced via difficulty retargeting every 2016 blocks., bitcoin core source (chainparams.cpp, npowtargetspacing = 10 * 60) and bitcoin.org developer guide, which both state bitcoin's target average time between blocks is 600 seconds (10 minutes)., bitcoin core source (src/kernel/chainparams.cpp, consensus.npowtargetspacing = 10 * 60 seconds) and the bitcoin wiki article 'target' (en.bitcoin.it/wiki/target), both documenting bitcoin's difficulty adjustment algorithm targeting a 600-second (10-minute) average block interval., bitcoin core source code (chainparams.cpp, consensus.npowtargetspacing = 10 * 60) and the bitcoin wiki 'difficulty' / developer guide, which document the 10-minute (600 second) target average block time used in the difficulty retarget algorithm., bitcoin core source code (chainparams.h, consensus.npowtargetspacing = 60 * 10) and the bitcoin developer guide (developer.bitcoin.org), both stating the network targets one block every 10 minutes (600 seconds) on average, enforced via difficulty retargeting every 2016 blocks., bitcoin core source code (src/chainparams.cpp / src/pow.cpp, consensus.npowtargetspacing = 600) and the bitcoin whitepaper (nakamoto 2008, section 4: 'to compensate for increasing hardware speed... proof-of-work difficulty is determined by a moving average targeting an average number of blocks per hour' — implemented network-wide as a 10-minute/600-second target); corroborated by the bitcoin developer guide at developer.bitcoin.org., bitcoin developer guide (developer.bitcoin.org) and bitcoin.org faq: target average block time is 600 seconds (10 minutes), bitcoin developer guide (developer.bitcoin.org), 'proof of work' section: 'every 2,016 blocks, ... the difficulty is adjusted to target ... an average of one block every 10 minutes.' this is bitcoin's protocol-defined target average block time of 600 seconds, unrelated to the pinned ethereum block window used only to timestamp this request., bitcoin developer guide (developer.bitcoin.org), 'proof of work': block difficulty is retargeted every 2016 blocks so that blocks are found on average every 10 minutes (600 seconds); corroborated by the original bitcoin whitepaper (bitcoin.org/bitcoin.pdf), section on proof-of-work., bitcoin developer guide (developer.bitcoin.org, 'block chain' / mining difficulty target section) and the bitcoin core source (chainparams.cpp, npowtargetspacing = 10 * 60): bitcoin's proof-of-work difficulty retargets every 2016 blocks to hold the average block interval at 10 minutes, i.e. 600 seconds., bitcoin developer guide (developer.bitcoin.org/devguide/block_chain.html, proof of work section) and bitcoin core source/documentation, which define the target block interval as 600 seconds (10 minutes), with difficulty retargeted every 2016 blocks to maintain this average., bitcoin developer guide (https://developer.bitcoin.org/devguide/block_chain.html) — states bitcoin targets a new block every 10 minutes on average; corroborated by the bitcoin wiki difficulty page (https://en.bitcoin.it/wiki/difficulty), which defines the retarget formula around a 10-minute (600 second) target spacing., bitcoin developer guide, 'block chain / proof of work' section (developer.bitcoin.org/devguide/block_chain.html), which documents the 10-minute (600 second) target average block interval enforced by bitcoin's difficulty adjustment algorithm, bitcoin developer guide, bitcoin.org: 'block time' — bitcoin's difficulty adjustment retargets every 2016 blocks so that blocks are produced at a target average interval of 10 minutes (600 seconds); https://developer.bitcoin.org/devguide/block_chain.html#target-nbits, bitcoin developer guide, block chain, proof of work: https://developer.bitcoin.org/devguide/block_chain.html#proof-of-work, bitcoin developer guide, block chain: https://developer.bitcoin.org/devguide/block_chain.html, bitcoin developer guide, developer.bitcoin.org/devguide/block_chain.html: "to keep the block generation rate at one block every 10 minutes"; corroborated by the bitcoin wiki 'difficulty' page describing the 2016-block retarget aiming for a 10-minute (600s) average block time., bitcoin developer guide, developer.bitcoin.org/en/developer-guide.html#proof-of-work: 'difficulty ... target ... average of one block every 10 minutes'; corroborated by the bitcoin wiki 'difficulty' article (en.bitcoin.it/wiki/difficulty)., bitcoin whitepaper (satoshi nakamoto, 'bitcoin: a peer-to-peer electronic cash system', bitcoin.org/bitcoin.pdf, section 4: 'proof-of-work') and bitcoin core developer documentation (developer.bitcoin.org/devguide/block_chain.html), which state the network is designed to produce one block roughly every 10 minutes (600 seconds) on average, with difficulty retargeting every 2016 blocks to maintain that average., bitcoin wiki 'target' article (en.bitcoin.it/wiki/target) and bitcoin core source code constant npowtargetspacing = 10*60 in src/chainparams.cpp, both stating a 10 minute (600 second) target average block interval, bitcoin wiki (en.bitcoin.it) article "block time", and bitcoin core source (src/chainparams.cpp/chainparams.h, consensus.npowtargetspacing = 600 seconds), both documenting the 10-minute (600 second) target average block interval used for difficulty retargeting., bitcoin wiki - difficulty (en.bitcoin.it/wiki/difficulty) and bitcoin core source chainparams.cpp (npowtargetspacing = 10 * 60 seconds), corroborated by the bitcoin wiki controlled_supply page describing the 10-minute block target used for the difficulty adjustment algorithm., bitcoin wiki, 'difficulty' (https://en.bitcoin.it/wiki/difficulty) and bitcoin developer guide, block chain section (https://developer.bitcoin.org/devguide/block_chain.html), both stating bitcoin targets a new block every 10 minutes (600 seconds) on average via the difficulty retarget every 2016 blocks., bitcoin.org, bitcoin.org developer guide (block chain / proof of work section) and the bitcoin whitepaper, both stating a targeted average block interval of 10 minutes (600 seconds), bitcoin.org developer guide (developer.bitcoin.org, 'proof of work' / block time section) and bitcoin wiki 'difficulty' page, both stating the protocol targets a 10-minute average block interval, bitcoin.org developer guide (developer.bitcoin.org/devguide/block_chain.html) and bitcoin wiki 'difficulty' page (en.bitcoin.it/wiki/difficulty), both stating bitcoin's target average block time is 10 minutes (600 seconds), bitcoin.org developer guide (https://developer.bitcoin.org/devguide/block_chain.html), 'proof of work' section, and bitcoin core's chainparams.cpp (npowtargetspacing = 10 * 60 seconds), both stating the target average block time of 600 seconds (10 minutes)., bitcoin.org developer guide - block chain / proof of work (https://developer.bitcoin.org/devguide/block_chain.html), which states bitcoin targets a new block every 10 minutes (600 seconds) on average, maintained via difficulty retargeting every 2016 blocks., bitcoin.org developer guide / bitcoin core source (chainparams.cpp, npowtargetspacing = 600), which documents the 10-minute (600 second) target average block time used by the difficulty adjustment algorithm, bitcoin.org developer guide, 'block chain' section (https://developer.bitcoin.org/devguide/block_chain.html): 'the difficulty ... is retargeted ... so that blocks are generated ... on average every 10 minutes.' corroborated by the bitcoin wiki 'difficulty' page, which states the target block time is 10 minutes (600 seconds)., bitcoin.org developer guide, 'block chain' section: https://developer.bitcoin.org/devguide/block_chain.html — states bitcoin's proof-of-work difficulty is adjusted every 2016 blocks so that blocks continue to be found on average every 10 minutes (600 seconds)., bitcoin.org developer guide, block chain / proof of work section: 'the target average time between blocks in the bitcoin network is 10 minutes (600 seconds)', https://developer.bitcoin.org/devguide/block_chain.html, bitcoin.org faq — https://bitcoin.org/en/faq (sections on confirmations and bitcoin mining), bitcoin.org faq, https://bitcoin.org/en/faq, bitcoin.org faq, https://bitcoin.org/en/faq (mining > how does bitcoin mining work?), bitcoin.org faq, https://bitcoin.org/en/faq (mining section: average time to find a block remains 10 minutes), bitcoin.org faq, https://bitcoin.org/en/faq (mining section: average time to find a block remains 10 minutes; converted to 600 seconds)., bitcoin.org faq, https://bitcoin.org/en/faq (mining: difficulty adjusts to keep average block-finding time at 10 minutes), bitcoin.org faq, https://bitcoin.org/en/faq (why do i have to wait for confirmation?; how does bitcoin mining work?), bitcoin.org faq, https://bitcoin.org/en/faq (why do i have to wait for confirmation?; what about mining?), bitcoin.org faq, https://bitcoin.org/en/faq — sections 'why do i have to wait for confirmation?' and 'how does bitcoin mining work?' state approximately 10 minutes on average and difficulty adjustment maintaining a 10-minute average., bitcoin.org faq: https://bitcoin.org/en/faq, bitcoin.org, bip 104, motivation: https://bitcoin.org/bip/104/ (states the original target is a 10 minute per block average; 10 × 60 = 600 seconds)., bitcoin.org, bitcoin halving countdown: https://bitcoin.org/en/halving, developer.bitcoin.org, developer.bitcoin.org developer guide (proof of work) and bitcoin core chainparams.cpp (npowtargetspacing = 600 seconds)

Work

  1. pinnedblocks 26,058,999 to 26,059,298 to · on Ethereum mainnet
  2. answered141 of 141 agreed140 needed
    #470600from en.bitcoin.it
    #503600from bitcoin.org
    #341600from developer.bitcoin.org
    #1924600from bitcoin.org
    #153600from developer.bitcoin.org
    136 more
    #880600from en.bitcoin.it
    #1530600from en.bitcoin.it
    #493600from developer.bitcoin.org
    #524600from bitcoin.org
    #1743600from bitcoin.org
    #862600from bitcoin.org
    #494600from bitcoin.org
    #847600from bitcoin.org
    #367600from developer.bitcoin.org
    #248600from en.bitcoin.it
    #1569600from developer.bitcoin.org
    #1020600from bitcoin.org
    #215600from bitcoin.org
    #607600from bitcoin.org
    #1879600Bitcoin whitepaper (Satoshi Nakamoto, 'Bitcoin: A Peer-to-Peer Electronic Cash System', bitcoin.org/bitcoin.pdf, Section 4: 'Proof-of-Work') and Bitcoin Core developer documentation (developer.bitcoin.org/devguide/block_chain.html), which state the network is designed to produce one block roughly every 10 minutes (600 seconds) on average, with difficulty retargeting every 2016 blocks to maintain that average.
    #1536600from developer.bitcoin.org
    #781600from developer.bitcoin.org
    #443600Bitcoin Wiki - Difficulty (en.bitcoin.it/wiki/Difficulty) and Bitcoin Core source chainparams.cpp (nPowTargetSpacing = 10 * 60 seconds), corroborated by the Bitcoin Wiki Controlled_supply page describing the 10-minute block target used for the difficulty adjustment algorithm.
    #309600from bitcoin.org
    #351600Bitcoin.org Developer Guide (developer.bitcoin.org, 'Proof of Work' / block time section) and Bitcoin Wiki 'Difficulty' page, both stating the protocol targets a 10-minute average block interval
    #1649600from bitcoin.org
    #1616600from developer.bitcoin.org
    #635600from bitcoin.org
    #1119600from developer.bitcoin.org
    #1299600from developer.bitcoin.org
    #671600Bitcoin Core source code (chainparams.h, consensus.nPowTargetSpacing = 60 * 10) and the Bitcoin Developer Guide (developer.bitcoin.org), both stating the network targets one block every 10 minutes (600 seconds) on average, enforced via difficulty retargeting every 2016 blocks.
    #180600from bitcoin.org
    #1464600from developer.bitcoin.org
    #1514600from en.bitcoin.it
    #2600Bitcoin.org Developer Guide / Bitcoin Core source (chainparams.cpp, nPowTargetSpacing = 600), which documents the 10-minute (600 second) target average block time used by the difficulty adjustment algorithm
    #1763600from en.bitcoin.it
    #579600from bitcoin.org
    #1113600from en.bitcoin.it
    #294600from developer.bitcoin.org
    #480600from bitcoin.org
    #1723600from developer.bitcoin.org
    #8600from bitcoin.org
    #1663600from bitcoin.org
    #192600from en.bitcoin.it
    #1232600from bitcoin.org
    #953600from bitcoin.org
    #1168600from bitcoin.org
    #1313600from developer.bitcoin.org
    #1599600from bitcoin.org
    #1540600Bitcoin Core source code (chainparams.cpp, consensus.nPowTargetSpacing = 10 * 60) and the Bitcoin Wiki 'Difficulty' / Developer Guide, which document the 10-minute (600 second) target average block time used in the difficulty retarget algorithm.
    #1860600Bitcoin Developer Guide, 'Block Chain / Proof of Work' section (developer.bitcoin.org/devguide/block_chain.html), which documents the 10-minute (600 second) target average block interval enforced by Bitcoin's difficulty adjustment algorithm
    #277600Bitcoin Developer Guide, developer.bitcoin.org/devguide/block_chain.html: "to keep the block generation rate at one block every 10 minutes"; corroborated by the Bitcoin Wiki 'Difficulty' page describing the 2016-block retarget aiming for a 10-minute (600s) average block time.
    #65600Bitcoin Developer Guide (developer.bitcoin.org), 'Proof of Work' section: 'Every 2,016 blocks, ... the difficulty is adjusted to target ... an average of one block every 10 minutes.' This is Bitcoin's protocol-defined target average block time of 600 seconds, unrelated to the pinned Ethereum block window used only to timestamp this request.
    #318600from bitcoin.org
    #1199600bitcoin.org Developer Guide (Block Chain / Proof of Work section) and the Bitcoin whitepaper, both stating a targeted average block interval of 10 minutes (600 seconds)
    #1506600from bitcoin.org
    #209600from bitcoin.org
    #1193600from bitcoin.org
    #328600Bitcoin Wiki (en.bitcoin.it) article "Block time", and Bitcoin Core source (src/chainparams.cpp/chainparams.h, consensus.nPowTargetSpacing = 600 seconds), both documenting the 10-minute (600 second) target average block interval used for difficulty retargeting.
    #1401600Bitcoin.org Developer Guide (developer.bitcoin.org/devguide/block_chain.html) and Bitcoin Wiki 'Difficulty' page (en.bitcoin.it/wiki/Difficulty), both stating Bitcoin's target average block time is 10 minutes (600 seconds)
    #1846600from developer.bitcoin.org
    #613600from bitcoin.org
    #1274600from bitcoin.org
    #1906600from developer.bitcoin.org
    #718600from bitcoin.org
    #1079600from en.bitcoin.it
    #1275600from bitcoin.org
    #1207600from en.bitcoin.it
    #527600from en.bitcoin.it
    #827600from bitcoin.org
    #866600Bitcoin Core chainparams.cpp (nPowTargetSpacing = 10 * 60 seconds) as described in the Bitcoin Developer Guide / Bitcoin Wiki 'Block time' article, which states Bitcoin's difficulty adjustment targets an average of one block every 10 minutes (600 seconds).
    #1254600Bitcoin Developer Guide (developer.bitcoin.org) and bitcoin.org FAQ: target average block time is 600 seconds (10 minutes)
    #1941600from bitcoin.org
    #429600Bitcoin Developer Guide (developer.bitcoin.org, 'Block Chain' / mining difficulty target section) and the Bitcoin Core source (chainparams.cpp, nPowTargetSpacing = 10 * 60): Bitcoin's proof-of-work difficulty retargets every 2016 blocks to hold the average block interval at 10 minutes, i.e. 600 seconds.
    #912600Bitcoin Core / bitcoin.org Developer Guide (Block Chain / Proof of Work section): target block time is 10 minutes (600 seconds), maintained by adjusting difficulty every 2016 blocks.
    #490600from bitcoin.org
    #1499600Bitcoin Developer Guide (developer.bitcoin.org), 'Proof of Work': block difficulty is retargeted every 2016 blocks so that blocks are found on average every 10 minutes (600 seconds); corroborated by the original Bitcoin whitepaper (bitcoin.org/bitcoin.pdf), Section on Proof-of-Work.
    #1631600from bitcoin.org
    #606600from developer.bitcoin.org
    #559600from developer.bitcoin.org
    #15600from bitcoin.org
    #735600Bitcoin Developer Guide, developer.bitcoin.org/en/developer-guide.html#proof-of-work: 'Difficulty ... target ... average of one block every 10 minutes'; corroborated by the Bitcoin Wiki 'Difficulty' article (en.bitcoin.it/wiki/Difficulty).
    #312600from developer.bitcoin.org
    #705600from developer.bitcoin.org
    #1980600from bitcoin.org
    #197600from bitcoin.org
    #809600from en.bitcoin.it
    #66600from bitcoin.org
    #721600from developer.bitcoin.org
    #842600from developer.bitcoin.org
    #88600Bitcoin Developer Guide (developer.bitcoin.org/devguide/block_chain.html, Proof of Work section) and Bitcoin Core source/documentation, which define the target block interval as 600 seconds (10 minutes), with difficulty retargeted every 2016 blocks to maintain this average.
    #1581600from en.bitcoin.it
    #1081600from bitcoin.org
    #281600from developer.bitcoin.org
    #1285600from bitcoin.org
    #1468600Bitcoin Core source (src/kernel/chainparams.cpp, consensus.nPowTargetSpacing = 10 * 60 seconds) and the Bitcoin Wiki article 'Target' (en.bitcoin.it/wiki/Target), both documenting Bitcoin's difficulty adjustment algorithm targeting a 600-second (10-minute) average block interval.
    #729600developer.bitcoin.org Developer Guide (Proof of Work) and Bitcoin Core chainparams.cpp (nPowTargetSpacing = 600 seconds)
    #510600from bitcoin.org
    #1086600from bitcoin.org
    #1890600from bitcoin.org
    #51600from bitcoin.org
    #124600from bitcoin.org
    #285600from bitcoin.org
    #545600from developer.bitcoin.org
    #540600Bitcoin Core source (chainparams.cpp, nPowTargetSpacing = 10 * 60 = 600 seconds) and the Bitcoin Wiki 'Difficulty' article, which describe the protocol's target average block interval of 10 minutes (600 seconds), enforced via difficulty retargeting every 2016 blocks.
    #1662600from bitcoin.org
    #327600from bitcoin.org
    #1129600from bitcoin.org
    #798600from bitcoin.org
    #183600from bitcoin.org
    #1295600from developer.bitcoin.org
    #777600Bitcoin Core source code (src/chainparams.cpp / src/pow.cpp, consensus.nPowTargetSpacing = 600) and the Bitcoin whitepaper (Nakamoto 2008, Section 4: 'to compensate for increasing hardware speed... proof-of-work difficulty is determined by a moving average targeting an average number of blocks per hour' — implemented network-wide as a 10-minute/600-second target); corroborated by the Bitcoin Developer Guide at developer.bitcoin.org.
    #1705600from bitcoin.org
    #660600from developer.bitcoin.org
    #355600from developer.bitcoin.org
    #1427600from developer.bitcoin.org
    #715600from developer.bitcoin.org
    #59600from bitcoin.org
    #434600from developer.bitcoin.org
    #637600from bitcoin.org
    #812600from developer.bitcoin.org
    #329600from developer.bitcoin.org
    #386600from developer.bitcoin.org
    #464600from developer.bitcoin.org
    #1965600from developer.bitcoin.org
    #1342600from bitcoin.org
    #1314600Bitcoin Wiki 'Target' article (en.bitcoin.it/wiki/Target) and Bitcoin Core source code constant nPowTargetSpacing = 10*60 in src/chainparams.cpp, both stating a 10 minute (600 second) target average block interval
    #475600from developer.bitcoin.org
    #293600Bitcoin Core developer documentation (bitcoin.org/en/developer-guide) — difficulty retarget section stating the protocol targets a 600 second (10 minute) average block interval, enforced by adjusting difficulty every 2016 blocks.
    #1233600from bitcoin.org
    #1725600Bitcoin Core source (chainparams.cpp, nPowTargetSpacing = 10 * 60) and Bitcoin.org Developer Guide, which both state Bitcoin's target average time between blocks is 600 seconds (10 minutes).
    #1673600from developer.bitcoin.org
    #1884600from bitcoin.org
    #1937600from bitcoin.org
    #595600from developer.bitcoin.org
    #1771600from bitcoin.org
    #661600from bitcoin.org
    #127600from developer.bitcoin.org
    #138600from bitcoin.org
    #61600from developer.bitcoin.org
    #174600from bitcoin.org
  3. signed
    by the attester 0x5598…2982usable until

    Checking the signature in this browser.

    typed data
    the exact bytes a consumer verifies, as JSON
    attester
    0x5598aa9146215bc13eb26f2c692ad1461fd32982
    signature
    0xa74e5e09a523b5d003be6d171dadbbfb1b24466b1f7dc816f61a23c1338c3e4a55d16973ad5a14bade80ac3f916abf2f43f118f82697a5c6967a5097876e6f051c
    question hash
    0x40c165f37adc7e7b4be6cbd1992fd6474f7fddcbee8a5cd41d5ec26cf716b1d9
    answer type
    uint256
    consumer
    none named; signed for the zero address
  4. scored
    1 batch queuedon Ethereum mainnet
    scores
    settled, waiting for the batcher