We have users reporting being on a fork. It seems it happened about 2 hours ago :-(
- they had correct hash for 976381: 430643ecd7bb4022fcbdbcb6c9b5ccf829ebf5c8f7eb068edce9b31d9744ee67
- but not this correct hash for 976382: 8bd922c14ba1a52314aed7e7eae4ff414b8ad2c7af56b93f7137d5d414194a6c
What will hopefully help you is to restart the client then.
See in general about forks here:
- Prelude (e.g. "Forks happen all the time, you could say with every new block. With every cryptocoin that is out there, and the clients notice this soon and bring you back on track.")
- So, how do you actually know that something is "wrong" in your Gridcoin client?
So, what to do when you notice you are on a fork?
- check your block hash with fediverse on IRC (use the !blocks and !verify commands): if your current block's hash (e.g. for #976511) is wrong, please also check 10 blocks past (e.g. #976501). If 976501 and upper blocks are fine, likely your client will "self-heal" and you can enjoy your cup of coffee
- If you notice though, that the hashes are wrong for a longer series: please restart your client (your client will try to fix your situation at start)
- If this still does NOT help: ask first in IRC what to do (the most likely answer will be to use the !snapshot or !bootstrap).
current hash for "getblockhash 976506'" (type this in your debug console):
- e8a47c60af21b758696b4d124c8ce2725332f39ba2c25059d8ac8bda4f4e3313
see also here for some comments
and overview here
Comments
Post a Comment