Is your feature request related to a problem? Please describe.
Currently, the difficulty retargeting configuration can be confusing. At first glance, chainparams.cpp contains:
The difficulty retargeting nPowTargetTimespan is set at 3.5 days, although according to the website, Vertcoin is using the Kimoto Gravity Well to retarget at every block. After some digging, we find in https://github.com/vertcoin-project/vertcoin-core/blob/master/src/pow.cpp#L22 that indeed the retargeting is set to 2.5 min (i.e. every block):
static const int64_t BlocksTargetSpacing = 2.5 * 60; // 2.5 minutes
Describe the solution you'd like
It would be less confusing to move the Kimoto BlocksTargetSpacing setting into the chainparams.cpp with the rest of the configurations. If there are other configurable settings, for example the block height when to start the Kimoto Well, move them as well. This would make things easier for testings and forking.
Is your feature request related to a problem? Please describe. Currently, the difficulty retargeting configuration can be confusing. At first glance,
chainparams.cppcontains:The difficulty retargeting nPowTargetTimespan is set at 3.5 days, although according to the website, Vertcoin is using the Kimoto Gravity Well to retarget at every block. After some digging, we find in https://github.com/vertcoin-project/vertcoin-core/blob/master/src/pow.cpp#L22 that indeed the retargeting is set to 2.5 min (i.e. every block):
static const int64_t BlocksTargetSpacing = 2.5 * 60; // 2.5 minutesDescribe the solution you'd like It would be less confusing to move the Kimoto
BlocksTargetSpacingsetting into thechainparams.cppwith the rest of the configurations. If there are other configurable settings, for example the block height when to start the Kimoto Well, move them as well. This would make things easier for testings and forking.