- situation
- verify your block hashes
- further info about forks
I. situation
About 11h ago, there were first reports of Gridcoin users being on a fork :-(
Looking now at it, the block that "split" the other chain(s) seems: 1046801
output from IRC:
- !verify 1046800 e20a0e5c04c987942f7a557ec2b06a220a6c0dfb504f4db7de2719b8c436cf5e
- fediverse: => CORRECT: the given hash (e20a0e5c04c987942f7a557ec2b06a220a6c0dfb504f4db7de2719b8c436cf5e) belongs to block 1046800
- !verify 1046801 14782e6f8fff6133cec35e6a533d308adcc98f1d8d73be2867be085ddb1250df
- fediverse: => WRONG: block 1046801 has this hash: 2b3ce5374983ba1c47ef6dd078e28e1d29a590e23a3690d19c0a1c4e84d4e8a6
Chain examples at 22:03 UTC+2, 2017 Oct 12:
- another user on forked chain: net weight: 1.07M; difficulty 0.125
- fediverse has: 4.566 mio net weight; diff 1.145
II. Please verify your block hashes below, so we stay together!
(e.g. type in your Gridcoin wallet's debug menu: getblockhash 1047690)
- When your hash doesn't match with below hashes:
- try a restart of the client (see here why).
- If that did not help: come first to IRC and we'll guide you (e.g. let you do a reorganize (see: (A)), this will likely take less time than doing a blockchain rebuild)
- You could also try from the Gridcoin menu: Advanced » Rebuild Block Chain (you can also apply the snapshot/bootstrap and make also a !backup of your important files first)
- ...
- 1047690 - 40a4689d5a63cbc9c61643fba1ab80c3aba4dbdca7f2c795feffa210abbb737d (0.95 difficulty; 9.77 million net weight)
- 1047488 - 7dfad8f9071d5a63d300b2b04946c0e46f8b3cd0851475df7180e22f6f8007a5 (2.46 difficulty; 20.77 million net weight)
- 1047364 - 5c675fceb4d4c93e1d23d756db66713781c3fb419c48e2ffceae4c22e5aa385e (7.7 difficulty; 14.68 million net weight)
- see older hashes at: (B)
III. see also (aka: further info about forks)
See also chapters:
- Prelude +
- So, how do you actually know that something is "wrong" in your Gridcoin client?
here.
Erkan (find me on IRC and twitter)
(A)
Typing "reorganize e20a0e5c04c987942f7a557ec2b06a220a6c0dfb504f4db7de2719b8c436cf5e" (without the "s) in your debug console should bring you to block 1046800, and hopefully you get back to our chain. Compare hashes above, please.
(B)
See newer hashes in section II above.
- 1047348 - 6486f52cb39ef34cca3e2a8dc5f9a883ecc19e59b67ed1269bbdb8ebd9e6d691 (2.4 difficulty; 6.14 million net weight)
- 1047315 - 1b7331cafaf8ba0c375b5f0d898a1cb909b793d9c9c5b2f572f13d0c68adac9e (0.82 difficulty; 5.05 million net weight)
- 1047305 - 36f2ee208e5a718a2f48ed743541a09d5cc52eab3f81a496e31844e91aa58c7c (0.77 difficulty; 4.98 million net weight)
- 1047296 - 6189825f2282ad5cf192f976225522bce6896056657b330935a5f99677ee1954 (0.77 difficulty; 4.935 million net weight)
- 1047290 - 447bcf2cba283852b99a37dfb97486adbbcf69e422953c9b9d717fc3e7dbfdfa (0.849 difficulty; 4.769 million net weight)