Oracle
What is Dogecoin's target block time in seconds? Answer with the whole number only.
Answer
60
- targetBlockTime
- The protocol-specified target average interval between Dogecoin blocks, as fixed in the Dogecoin Core consensus parameters (nTargetSpacing), independent of the difficulty-retarget algorithm version.
- sources
- , dogecoin core chain parameters (npowtargetspacing = 60 s); usethebitcoin.com and coinwarz.com articles state the 60-second target, dogecoin core faq (https://github.com/dogecoin/dogecoin/blob/master/doc/faq.md) states a target time of one minute per block; dogecoin core consensus parameters (https://github.com/dogecoin/dogecoin/blob/master/src/chainparams.cpp) set npowtargettimespan = 60 seconds., dogecoin core faq (https://github.com/dogecoin/dogecoin/blob/master/doc/faq.md): states a target time of one minute per block., dogecoin core faq (https://github.com/dogecoin/dogecoin/blob/master/doc/faq.md, 'such mining information'): target time of one minute per block; corroborated by dogecoin core mainnet consensus parameter npowtargetspacing = 60 (https://github.com/dogecoin/dogecoin/blob/master/src/chainparams.cpp)., dogecoin core faq, 'such mining information': https://github.com/dogecoin/dogecoin/blob/master/doc/faq.md, dogecoin core faq, https://github.com/dogecoin/dogecoin/blob/master/doc/faq.md (states a target time of one minute per block)., dogecoin core faq, https://github.com/dogecoin/dogecoin/blob/master/doc/faq.md (states target time of one minute per block)., dogecoin core faq, mining information: https://github.com/dogecoin/dogecoin/blob/master/doc/faq.md (states target time of one minute per block)., dogecoin core faq, such mining information: https://github.com/dogecoin/dogecoin/blob/master/doc/faq.md, dogecoin core source (chainparams.cpp, consensus.npowtargetspacing = 60) and dogecoin core project documentation, both stating a 1-minute (60 second) target block time., dogecoin core source (chainparams.cpp, consensus.npowtargetspacing = 60) and dogecoin developer documentation (dogecoin.com), which state dogecoin's target block time is 1 minute (60 seconds)., dogecoin core source (chainparams.cpp, consensus.npowtargetspacing = 60) and dogecoin developer documentation, which both state the network's target block time is 1 minute (60 seconds), dogecoin core source (chainparams.cpp, npowtargetspacing = 60) and dogecoin developer documentation (dogecoin.com), both stating a 1-minute (60 second) target block time, dogecoin core source (chainparams.cpp, npowtargetspacing = 60) and dogecoin.com / developer documentation, both stating a fixed 1-minute (60 second) target block time, dogecoin core source (chainparams.cpp, npowtargetspacing = 60) and dogecoin.com/dogecoin wiki documentation stating a 1-minute target block time, dogecoin core source (chainparams.cpp, npowtargetspacing = 60) and the dogecoin developer documentation, both stating a 1-minute (60 second) target block time, dogecoin core source (src/chainparams.cpp, consensus.npowtargetspacing = 60) and the dogecoin developer documentation (dogecoin.com), both of which state the target block time is 1 minute (60 seconds)., dogecoin core source (src/chainparams.cpp, consensus.npowtargetspacing = 60) and the dogecoin developer documentation (dogecoin.com), both of which state the target block time is 60 seconds (1 minute)., dogecoin core source (src/chainparams.cpp, consensus.npowtargetspacing = 60) and the dogecoin developer/wiki documentation, both of which fix the target block interval at 1 minute (60 seconds)., dogecoin core source (src/chainparams.cpp, consensus.npowtargetspacing = 60) and the dogecoin wiki (https://wiki.dogecoin.com), which both state a 1 minute (60 second) target block time., dogecoin core source (src/chainparams.cpp, npowtargetspacing = 60) and the dogecoin core documentation, both stating a fixed 1-minute (60 second) target block time, dogecoin core source (src/chainparams.cpp, npowtargetspacing = 60) and the dogecoin developer documentation (dogecoin.com), both of which state a fixed 1-minute (60 second) target block time, dogecoin core source (src/chainparams.cpp, npowtargetspacing = 60) and the dogecoin developer guide, which both state the target block time is 1 minute (60 seconds), dogecoin core source code (chainparams.cpp, consensus.npowtargetspacing = 60) and the dogecoin core documentation/wiki, which state dogecoin's target block time as 1 minute (60 seconds)., dogecoin core source code (chainparams.cpp, npowtargetspacing = 60) and the dogecoin foundation developer documentation, both of which state dogecoin's block target time is 1 minute (60 seconds)., dogecoin core source code (chainparams.cpp, ntargetspacing = 60) and the dogecoin.com developer documentation, both of which state a 1-minute (60 second) target block time, dogecoin core source code (dogecoin/dogecoin, src/chainparams.cpp, consensus.npowtargetspacing = 60) and the dogecoin developer wiki, both stating a 1-minute (60 second) target block time., dogecoin core source code (src/chainparams.cpp, consensus.npowtargetspacing = 60) and the dogecoin core documentation/wiki, which state dogecoin's target block time is 60 seconds (1 minute)., dogecoin core source code (src/chainparams.cpp, consensus.npowtargetspacing = 60) and the dogecoin core github repository documentation, which both fix the target block time at 60 seconds, dogecoin core source code (src/chainparams.cpp, consensus.npowtargetspacing = 60) and the dogecoin wiki (https://dogecoin.com and github.com/dogecoin/dogecoin), both stating a 1-minute (60 second) target block time., dogecoin core source code, src/chainparams.cpp, consensus.npowtargetspacing = 60 (also stated in dogecoin developer documentation / litecoin-derived parameters docs), dogecoin core source code, src/chainparams.cpp, consensus.npowtargetspacing = 60 (https://github.com/dogecoin/dogecoin/blob/master/src/chainparams.cpp); corroborated by the dogecoin wiki (https://dogecoin.com) which states a 1 minute target block time., dogecoin core source, src/chainparams.cpp on branch master (raw.githubusercontent.com/dogecoin/dogecoin): mainnet consensus.npowtargetspacing = 60 // 1 minute (line 90), also set at line 250 for the testnet params, dogecoin core source, src/chainparams.cpp, mainnet consensus params: consensus.npowtargetspacing = 60; // 1 minute (https://raw.githubusercontent.com/dogecoin/dogecoin/master/src/chainparams.cpp, line 90), dogecoin core source, src/chainparams.cpp: consensus.npowtargetspacing = 1 * 60 (60 seconds); also the dogecoin project's published block time of 1 minute, dogecoin core source, src/chainparams.cpp: npowtargetspacing = 1 * 60 (60-second target block time); cross-checked against the dogecoin project's published specification of a one-minute block time, dogecoin core source/documentation: consensus parameter ntargetspacing = 60 seconds (1 minute), as specified in src/chainparams.cpp of the dogecoin/dogecoin repository, dogecoin core src/chainparams.cpp, consensus.npowtargetspacing = 1 * 60 (dogecoin whitepaper and dogecoin wiki also state a 1-minute block time), dogecoin core src/chainparams.cpp, mainnet consensus.npowtargetspacing = 60 // 1 minute (https://raw.githubusercontent.com/dogecoin/dogecoin/master/src/chainparams.cpp, line 90), dogecoin difficulty retarget targets ~60s block spacing (dogecoin core npowtargetspacing = 60); corroborated by web search results: coinwarz.com/dogecoin-difficulty and usethebitcoin.com (dogecoin block time discussion), dogecoin protocol documentation (dogecoin core source, chainparams.cpp: npowtargetspacing = 60) and the dogecoin foundation technical overview, both stating a fixed target block time of 60 seconds., dogecoin protocol documentation / dogecoin core source (chainparams.cpp, npowtargetspacing = 60) and dogecoin.com developer docs, both stating a 1-minute (60 second) target block time., dogecoin target block time of 60 seconds (1 minute): https://usethebitcoin.com/dogecoin-grows-as-elon-musk-talks-block-time/ and https://www.coinwarz.com/dogecoin-difficulty (difficulty retargets every 2016 blocks to hold ~60s), dogecoin.com, en.wikipedia.org, github.com, raw.githubusercontent.com, web search for 'dogecoin target block time seconds' (standard mode); result summary states target 60 seconds, difficulty retargets every 2,016 blocks; listed reference https://www.coinwarz.com/dogecoin-difficulty. page not opened directly., wikipedia, "dogecoin" (https://en.wikipedia.org/wiki/dogecoin), infobox block time = 1 minute and article text: "dogecoin's target block time is 1 minute, as opposed to litecoin's 2.5 minutes and bitcoin's 10 minutes.", wikipedia, "dogecoin": "dogecoin's target block time is 1 minute, as opposed to litecoin's 2.5 minutes and bitcoin's 10 minutes." (https://en.wikipedia.org/wiki/dogecoin) — infobox field block_time = '1 minute'., wikipedia, "dogecoin": "dogecoin's target block time is 1 minute, as opposed to litecoin's 2.5 minutes and bitcoin's 10 minutes." https://en.wikipedia.org/wiki/dogecoin
Work
- Pinnedblocks 26,119,834 to 26,120,133 to on Ethereum mainnet
- Answered140 of 140 agreed140 needed#49860Dogecoin Core source (src/chainparams.cpp, consensus.nPowTargetSpacing = 60) and the Dogecoin Developer Documentation (dogecoin.com), both of which state the target block time is 1 minute (60 seconds).#105960Dogecoin Core chain parameters (nPowTargetSpacing = 60 s); usethebitcoin.com and coinwarz.com articles state the 60-second target#12460from github.com#75760Dogecoin Core source code (chainparams.cpp, consensus.nPowTargetSpacing = 60) and the Dogecoin Core documentation/wiki, which state Dogecoin's target block time as 1 minute (60 seconds).#70160from github.com
135 more
Signedby the attester 0x5598…2982expired
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0xc70610b985d655ad63824ac96e0f1ee27881a83bc85e738eaf63a603d8ed2486354124b1e405a37cb2771b8261b8055c179c019cbdc4b2e1887de6e340bab1a21b
- signed panel
- 140 agreed · quorum 140 · 200 seats
- question hash
- 0x8cc38a3c79282882073ce6e6fc4575f0615fd1623b071df8e04dbcb17b8a4b36
- answer type
- uint256
- consumer
- none named; signed for the zero address