Closed idenchik1 closed 3 years ago
Hello, I investigated this shortly after you mentioned it. As of 2/11/2021, this is reproducible on computers that are capable of achieving at least 2.5 MH/s on a single process, and it is due to a hash-rate limit on the main server. Anything that was mined too fast appears to be rejected.
Anyway, it's out of my control. It will still work though if you run the program on a slower computer or use the recommended number of threads, I guess. I originally recommended 8 or 16 to keep the CPU fed, but now splitting CPU power between more processes than cores helps keep the hashrate per process low. Other than that, I'll keep an ear to the ground for anything I can do.
Closing this issue.
After 2.0 update mostly reject shares, but result seem right, comparing bad requests with good gived nothing