The time it takes to generate the first block after the difficulty level changes isn't used in the computation of how long the next 2016 blocks takes to compute. In some sense this is an artifact of the fact that there isn't the data available to compute how long it took to generate the genesis block. Anyhow, it would be interesting if this small flaw could somehow be exploited.
Time to generate first block after difficulty change isn't counted. #318
issue roconnor opened this issue on June 16, 2011-
roconnor commented at 12:20 AM on June 16, 2011: none
- dexX7 referenced this in commit cf1ffb79b4 on Dec 30, 2015
- MarcoFalke added the label Consensus on Sep 18, 2016
- MarcoFalke removed the label Priority Low on Sep 18, 2016
- deadalnix referenced this in commit 905170c7e8 on Mar 1, 2017
- classesjack referenced this in commit 0151d5c83a on Jan 2, 2018
- MarcoFalke added the label Feature on Feb 8, 2018
- MarcoFalke removed the label Bug on Feb 8, 2018
-
jb55 commented at 5:44 PM on July 16, 2018: member
Came here from a codetriage... is there anything to be done here?
- MarcoFalke removed the label Feature on May 23, 2019
- MarcoFalke added the label Brainstorming on May 23, 2019
- Losangelosgenetics referenced this in commit f5d13bb76e on Mar 12, 2020
-
MarcoFalke commented at 7:55 PM on April 24, 2020: member
Consensus changes or clean-ups should be discussed on the mailing list. When it is time to deploy a consensus change and implement it, a pull request can be opened against Bitcoin Core.
- MarcoFalke closed this on Apr 24, 2020
- hebasto referenced this in commit 2161a05855 on Sep 14, 2021
- DrahtBot locked this on Feb 15, 2022
Contributors
Labels