Thank you for your suggestion, I've began working on it. I'm contemplating a solution that won't just make the chain becoming stuck "less" likely, but certainly not likely. Open to suggestions, but as I said will try some various approaches.
So did someone actually put 500Gh on this coin or was it just the difficulty adjustment algo that made it go screwy like that? I'm thinking the latter is most likely. Can you just implement digi-shield or kgw?
Nobody ever put 500GHs on this coin and difficulty is not real. I have find many
blocks with 1.7 GHs when difficulty was 8000+. If it really was 8000+, it would
take me many hours to find a block, but I've find blocks every minute. But for some
reason pools can't find any block with more hashes.
It was more than 500 GHs; I think 1300ish GH/s at one point, or even higher.
I manged to screen capture while in the 715 GH/s range,
it was on
http://hashgoal.com/pool/MDOG/
Show Posts
