clarifying Gridcoin's situation/hashes/forks after stakeV8 block 1010000

more uptodate now here (block hashes, ...)

So, Gridcoin's new PoS "stake v8 kernel" blocks came (see timeline)

but:

many nodes got stuck at block 1010000
- e.g. my linux node with 3.6.0.2 got stuck

What seems to work is:

to download the snapshot file (md5 hash: 1b0f6288038bf6afff89de8eef3fa67b, sha256: 544f8dd4184f69ab3c0afbe92d8981e068e1980f6e3293ead694d1e039e347b9)
- see here for how to apply it: !snapshot howto
- this snapshot brings you to around block 968k only (July 2017)
- I'd recommend to you to take ONLY this file (see below: "Worrying for me is this")
- e.g. my snapshot file from February 2017 did not help unfortunately :-( my node did not seem to go past the v8-blocks...

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

When your hash doesn't match, try a restart of the client (see here why). If that did not help: you might try from menu: Advanced » Rebuild Block Chain (you can also apply the snapshot/bootstrap and make also a !backup of your important files); OR: come to IRC and we'll help you
...
1010485 (7.37 mio net weight, 0.673 difficulty)
1010482 - dcb4a0f296cbcfaba171b6f65bd7778ffc04d14fb54d675f6e8a5fffc1e1bd9d (7.22 million net weight)
1010447 - 48aeeac1fb580c6e2c9c6be3490f3814d41471018df7ac544cab3c251cf01146

most uptodate in IRC!

forks:

besides the pre-v8 blockchain we have now (from clients still using version below 3.6.0.1)
there happened also a fork at block 1010358
- to get yourself then on the "main chain" do this in your debug console: reorganize c9901362a87567d4ab09d04108957f3ae8382c4b1ef313ca62eb47c9105327be

Worrying for me is this:

the low network weight, difficulty, ...
- we had recently like >100 million net weight (e.g. >315 million net weight in August 2017)
- Gridcoin is/was now ideal laying there for being attacked (especially when someone prepared this beforehand) :-(

Erkan-Yilmaz / Gridcoin-tasks