LOL, smarterhash didn't drive the diff up that high as it was hashing with well under 200 mh/s, I was there mining and know this... (the blockchain explorer will bear this out, if you care to take the time to look instead of just throwing blame in the wrong place)
Once the other pools went live, big hash jumped in, and around 2.3 gh/s is what drove the diff up so high.
Here is the proof, check the block explorer for times..
Then the big hash decided to leave because there were no exchanges to dump, so at the current hashrate it's still around 1.5 days to the diff readjustment. (after being here for 4 days already..)
If the dev cares to save his coin, he should do 2 things:#1 rent some hash to get over this hurdle
#2 release a new wallet with either a 1 hour diff change, or implementing KGW immediately
Failure to do so, is likely to kill this coin before the next diff change, as blocks are already taking about 10x as long as they should be, and this will get worse as hash drops.
How can I make this assessment? Having the tools to do it right. Smarterhash is the best tools in the business, even if the coins we end up mining flop because of bad developers.
