Hi JCE,
When using your GPU miner, can you advise as to whether or not you are currently verifying the GPU result by cross checking with CPU that is is valid before submitting to the pool? Some other miners perform this check and will avoid submitting if there is a discrepancy, merely noting it as a 'Compute Error'. If you aren't, would you consider adding the functionality, even if only via a config or switch? If it slows down performance, it can still be beneficial when testing more aggressive clocks and multi_hash/intensity settings to have this check before submitting when trying to find the performance vs stability sweet spot and not wanting to get banned by the pool for invalid shares.
I received this error in JCE while testing the reasonable limit of each GPU so it got me wondering about this. My static difficulty is definitely appropriate as it's not even 25x my hashrate. I am sure that lowering my clocks will reduce or eliminate this issue, but I thought I'd include this result for informational purposes.
21:40:57 | Rejected by the pool.
21:40:57 | Message from the pool: Low difficulty share
21:41:45 | GPU 7 Thread 14 Lane 1526 finds a Share, value 400015
21:41:45 | Rejected by the pool.
21:41:45 | Connection failed: The pool kicked you out as Unauthenticated, its Difficulty 400015 is probably too high for your computing power. If the pool allows fixed Difficulty, fix it to a lower value.
21:41:45 | Connection interrupted, waiting 5s then retry, attempt #1
21:41:45 | Connection failed: Socket receive error: A blocking operation was interrupted by a call to WSACancelBlockingCall.
21:41:45 | Connection interrupted, waiting 5s then retry, attempt #2
Thank you for considering this. As things stand now only having the ability to specify one pool, it can result in complete downtime if invalid shares are submitted that are outside the proper difficulty level and the pool issues a ban.