Need help with Nicehash

Encounter a problem related to the pool or have a request for a feature? Post your issue here and we will help you out.
Forum rules
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.

Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.

We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.

For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Locked
Maznoz
Posts: 27
Joined: Thu Sep 03, 2015 6:02 am

Re: Need help with Nicehash

Post by Maznoz » Thu Oct 29, 2015 12:03 pm

They say the following about minimum difficult when creating a new order:

Code: Select all

Minimal pool difficulty: 1024 => 8192
No idea what it means, since 1024 seems to be too low. When using 8192 as a fixed difficulty there are no issue.

However, this is what their pool verificator says (seems to indicate that 1024 should work):

Code: Select all

Resolving pool host prohashing.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 98.115.147.74:3333... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received mining.set_difficulty... Pool difficulty too low (provided=16, minimum=1024)
Waiting for pool to send higher difficulty.
Received mining.notify work... OK
Received authorization result... OK
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Need help with Nicehash

Post by Steve Sokolowski » Thu Oct 29, 2015 2:33 pm

That's due to the work restart testing, which Nicehash doesn't support. You can use r=0.5 to get rid of that error. Or, you can wait 60s, after which the pool will detect there is an issue and skip the testing.
Locked