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.

Sign up for GitHub

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

Jump to bottom

under investigation: fork (August 2) #20

Open

Erkan-Yilmaz opened this issue Aug 2, 2017 · 0 comments

Labels

fork

Owner

Erkan-Yilmaz commented Aug 2, 2017 •

edited

Loading

Please compare hashes (e.g. in debug menu: getblockhash 982964):

983047 - 0e9d2f5df5d1133567c5d6e2fceac94590851d4b88fdd21c873e58dd9ac19627 (57.988 mio net weight)
983017 - 176c538ef42a960a98fe37cfc7952e760f6b02acae953addaba7dcc4a3340104
982989 - c2aca...a442 (net weight 45.7 mio)
982964 - d74afce916d489e114cb37c9e3c2eccc957e307594505d49eb2faf50c3a7ac6a

situation:

again gridcoinstats is on a fork :-( see their displayed red notice!
- edit: 2h later: gridocinstats is still on a fork :-(
there are at least since 40mins ago wrong block hashes also reported by users in irc :-(

most uptodate in IRC!

read in #10 how to check your hash, general info on forks, etc..

for the 2 forks yesterday, see: #19

You like what I do? Take action here.

Erkan-Yilmaz added the fork label

Erkan-Yilmaz mentioned this issue

the idle bot is back! #23

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment