-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
blocks are staking too slowly #11
Comments
The situation seems to be getting worse:
My client currently tells me the network weight is 4769. That's about 3.5 times less than 17476, which explains why we're getting 3.5 minute blocks, not 1 minute blocks. Making the minimum difficulty lower would allow us to go back to 1 minute blocks:
If there's any interest in fixing these two issues, I'll write code to fix them both. Do we have other hard-fork changes planned that these can get bundled in with? |
#25 fixes this. |
The target time per block is 1 minute, but we're seeing around half that rate. The last two days we've seen around 700 blocks per day.
I looked to see why that is, and found:
changing the 20 to 18 or something would probably fix the problem by increasing the max target / decreasing the min difficulty.
Issue #4 means that it's not unusual for two blocks to have the same timestamp, causing nActualSpacing to be 0, and causing a 2/15 = 13.3% leap in difficulty which then takes a while to recover from.
Changing bnProofOfStakeLimit would cause a hard fork.
The text was updated successfully, but these errors were encountered: