Quote from: valiant1 on April 20, 2018, 01:43:51 AM

The daemon exploded when it hit block 167k. The official pool was rolled back 400 blocks and is mining again. I'll try to update our Discord announcement post as other pool owners get their pools updated to fix the broken daemons, but in the meantime, the only pool that you can mine is http://intensecoin.com/pool . For more information, see https://github.com/valiant1x/intensecoin/issues/67#issuecomment-382936780

Quote from: MagicSmoker on April 19, 2018, 10:06:13 PM

It looks like the network is totally fubar - no block found on the official pool in over an hour and the hashvault pool also reporting effort on the current block exceeding 1300%. Well, we were warned to mine at our own risk... Tongue

Also, the instructions I was given earlier to use the --add-priority-node switches to sync the daemon didn't work; I had to use --add-exclusive-node instead, as reported by @YaStaer. Once synced, the balance from my 1.4.2 wallet showed up, but not the most recent mining payments from today. So, my recommendation - worth price paid - is to stop mining until things get well and truly sorted out.

Apologies for the headaches, Magic. Thanks for your patience.

No problem since you did warn us that mining would be extra risky at the time.

I just restarted the daemon with the 3 exclusive nodes and it synced up fine; the 2.0.0 wallet client also found my most recent mining payments, so looks like I've successfully made it over the hard fork hurdle. I also resumed mining on pool.intensecoin.com about 30 minutes earlier, but that may have been a bit premature because as of now no block has been found in about an hour, once again. I suppose I'll let it run for another 30 minutes or so to see what happens.

UPDATE - still no blocks found in the entire network so I've stopped mining once again.