Gridcoin: fork situation about 3h ago

We have users reporting being on a fork for a few hours :-(

• they had correct hash for 972178: 78f84f0fc91b832f54c5ff5e0c9a144334a469ebe0ce1dd488d02471728870c9
• but not this correct hash for 972179: 9e27450a65b4985a77eeedf78f479c6d3fc8ee531094bd36067de7e520a2e426

What will hopefully help you is to restart the client then.

See in general about forks here:

• Prelude
• 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 #972320) is wrong, please also check 10 blocks past (e.g.  #972310). If 972310 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 972581" (type this in your debug console): 

• 29a47db64069240b6ac1fc49efc9916ddd3695c8688cb02c092d37be00a574b1

and the net weight is at around >80 million at the moment