-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The problem of connecting nicehash pool #11
Comments
If only one nicehash proxy possible in chain, nicehash.com itself or Stratum-Proxy-XMR? |
Look at this topic, I there answered the same question #2 |
You need to put in proxy settings [Emu nicehash = false, Max workers = 1]. |
Thank you. I solve it with your guid. |
Hello, I want to compile your source code, can you provide a guide how to compile? Thank you very much for your help.On 1/16/2018 10:46,JerryWm<notifications@github.com> wrote:
Look at this topic, I there answered the same question #2
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hello! |
try turn off [KPALV 60] |
There are 2 miner workers login in the proxy, and then the prxoy connecting the nicehash pool "stratum+tcp://cryptonight.eu.nicehash.com:3355", the following problems arise:
1, if enable "Emu nicehash", then the proxy will be rejected by the nicehash pool.
2, if disable "Emu nicehash", can normally connect nicehash pool, but 2 miners will receive a lot of rejection, as follows:
![image](https://user-images.githubusercontent.com/32667839/34967995-70d11d52-faa1-11e7-8a75-f8d455f04981.png)
3、On the nicehash dashboard, there is only 1 worker's hashrate. It seems nicehash pool reject half of the 2 workers's hash.
4、2 miner workers use xmr-stak with "use_nicehash: true".
The text was updated successfully, but these errors were encountered: