-
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
Dynamic difficulty start check #18
Comments
hihiben
added a commit
to hihiben/gcoin-community
that referenced
this issue
Apr 18, 2016
Difficulty check is not necessary to guarantee the correctness of block. Remove t=it to avoid the restart failure that may caused by the dynamic difficulty check.
hihiben
added a commit
to hihiben/gcoin-community
that referenced
this issue
Apr 18, 2016
Difficulty check is not necessary to guarantee the correctness of block. Remove it to avoid the restart failure that may caused by the dynamic difficulty check.
willliw
added a commit
that referenced
this issue
Apr 25, 2016
Remove difficulty check when verifyDB #18
hihiben
added a commit
to hihiben/gcoin-community
that referenced
this issue
May 10, 2016
lbyyy
pushed a commit
to lbyyy/gcoin-community
that referenced
this issue
Jul 1, 2016
Difficulty check is not necessary to guarantee the correctness of block. Remove it to avoid the restart failure that may caused by the dynamic difficulty check.
solved |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Node在重啟時由於讀入cache的狀態和checkblock時的時間點會不一樣,加上由於無法紀錄在各個block height時當下的alliance狀態,可能造成重啟時dynamic difficulty check failure
The text was updated successfully, but these errors were encountered: