-
Notifications
You must be signed in to change notification settings - Fork 115
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
[request]Mining difficulty adjustment #325
Comments
This bug is crippling the network... This is a list of block times from today, columns:
|
Change as: if(_bi.number < FORKBLOCK)
{
if(_bi.timestamp >= _parent.timestamp + time_config)
{
target = _parent.bits - (_parent.bits/1024);
} else {
target = _parent.bits + (_parent.bits/1024); }
} else {
bigint const interval = (bigint)(_bi.timestamp-_parent.timestamp);
bigint const adjustvalue= max<bigint>(2 - interval /10 ,-99);
target = _parent.bits + _parent.bits/2048*adjustvalue;
} |
Whats the status of this issue? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Once the difficulty goes up, it takes months to go go down.
Report from kali:
screenshot from metaverse.farm
some one put 800GH (yes giga hash) solo for 1 hour
difficulty jumped from 31 to 35T really quickly (as it should)
now look at the difficulty when he is gone, 800GH of extra hashpower gone, and it takes ages to get back to original levels.
8 hours passed since that "1 hour 800GH burst mining" and difficulty is nowhere near the original level.
The text was updated successfully, but these errors were encountered: