Quote from: romasalah on July 04, 2017, 07:09:02 AM

Quote from: HamiltonWDS on July 04, 2017, 02:58:19 AM

Quote from: mitache365 on July 02, 2017, 05:03:59 PM

suprnova sh*t as usual

I have noticed that the amount of disconnects is usually in direct relation to the amount of hashing power or worker connections to the pool server. There was one particular account that I believe was about 10 million KH/s and a few others at the 5 million mark in the past few days. As of now, those accounts are not there and the pool seems stable for the most part.
Which if based on the past postings, this coin causes high CPU performance, and thus may not be suited for large data centers (unless they get their own pool).

I did give a try with solo mining with a high powered CPU server at home, but does seem that the wallet is too slow to keep up with the blocks. In 48 hours, only two blocks mined, one accepted, one orphaned (with 100 MH/s). Giving a short experiment with AWS for solo mining to see if network connectivity plays a significant factor.

I've tried solomining yesterday. 1st block is after 4 hours, the second after additional 6 hours but was orphaned. then no more for 7 hours. so I was a bit disappointed and went back to suprnova (46 Mh/s). At least now I know that I have a backup plan if suprnova goes down again

As you have managed to connect to the supernova, I have not been able to, the connection is lost every 30 seconds