Hi. Thank you for the response.
When you said IPool, did you mean lpool.name?
I've been using lpool.name, and when I set my difficulty to 1 or 2, after about 10 minutes
it's like the pool disconnects me. My D3 shows that the pool is dead, and I failover to my backup pool.
After about 20 or 30 seconds, then lpool.name's CNO pool shows alive. It's like they're changing the status of
their pool to dead to cause me to failover and stop mining at their site.
I raised my difficulty setting to d=3, and it lasted a little longer than 10 minutes, but not much. Same thing: kicked and had to
manually failover my D3 to go back there.
I tried changing my password setting from d=3 to just an x, where I don't set any difficulty.
lpool.name started me off at a 0.01 difficulty, and I had over 1000 shares submitted in about 5 seconds.
Then, a few seconds later, the pool status was dead, and I got kicked again, as described above.
I set my difficulty to d=8, and the pool set my difficulty at 3, and same kick systems happened again.
I couldn't find any other pool that has CNO listed, so stuck with lpool.name.
I'd like to find a place that's reliable and won't kick me every 8 to 10 minutes.
Thanks for any other pool suggestions besides lpool.name.
I do not own miners. I do hiring mining rigs to run through Ipool.name to help stabilize the network. Because there is no other dedicated public mining pool, I just set several different "workers" in the same pool to "failover" but do not know if this has happened frequently or not-it did happen not infrequently when there was other mining pool to failover which was not desirable for my purpose of supporting Coino network; most of them being switching-mining when available in the past.
I think as Coino is more active again, and more profitable, more mining pools will come back again.