Nicehash Friends

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.
User avatar
3Moose
Posts: 102
Joined: Sat Aug 26, 2017 6:14 pm

Re: Nicehash Friends

Post by 3Moose » Thu Oct 26, 2017 8:33 pm

Here what the error means:

Keep in mind: lower difficulties were left in the pools due to historical reasons, but are really inefficient with today's miners. That said - if your orders are disconnected with "Pool difficulty too low." or invalid extranonce sizes we encourage you to contact pool operator to make sure that pool is using minimal/starting pool share difficulty which is compatible with our service (and thus compatible with today's miners).

The required minimal initial and running pool difficulty is displayed on the "Create new order" page. Each algorithm has it's own initial and running difficulty, displayed in the field called "Minimal pool difficulty". Initial pool difficulty is evaluated while order is on stand-by without miners (but still Alive) while running pool difficulty is evaluated when order starts accepting miners - hashing power is assigned to order. If pool operator can't set this for you and setting worker difficulty isn't properly evaluated by the pool, you will unfortunately be forced to use another pool that uses higher difficulty.

Keep in mind: pool share difficulty is not the same as network diff
User avatar
3Moose
Posts: 102
Joined: Sat Aug 26, 2017 6:14 pm

Re: Nicehash Friends

Post by 3Moose » Fri Nov 03, 2017 11:14 am

To read the blogs over these last several months, this place was full of NH miners..... guess they all left.
bsock
Posts: 20
Joined: Mon Oct 16, 2017 9:32 pm

Re: Nicehash Friends

Post by bsock » Fri Nov 03, 2017 11:25 am

This is for Scrypt Mining and not X11
---------------------------------------------------------------
Try and connect without any arguments first - a=scrypt is the default and doesn't need to be added....then add back the difficulty level (d=131072), see if you can connect....then add back n (d=131072 n=nh) and see if you can connect, etc. For some reason, the pool is seeing your difficulty level as 64K and not 128K, which is odd. I don't use any settings except for w=watts and p=power on PH.
bsock
Posts: 20
Joined: Mon Oct 16, 2017 9:32 pm

Re: Nicehash Friends

Post by bsock » Fri Nov 03, 2017 11:28 am

You are correct, pool share difficulty is not the same as network difficulty. I believe you divide the pool share difficulty by 65536 to get the network difficulty. Or vice versa...been a while since I messed with the settings and options.
b0849003
Posts: 6
Joined: Sun Oct 15, 2017 11:00 pm

Re: Nicehash Friends

Post by b0849003 » Sat Nov 04, 2017 1:44 pm

have same problem =(



Pool host: prohashing.com
Pool port: 3333
Pool user: Owner90Ant
Pool pass: g=off h=1000
Algorithm: Scrypt

Resolving pool host prohashing.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 167.88.15.87:3333... Error: Read timed out

Pool host: prohashing.com
Pool port: 3333
Pool user: Owner90Ant
Pool pass: d=131072 n=nh
Algorithm: Scrypt

Resolving pool host prohashing.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 167.88.15.87:3333... Error: Read timed out
b0849003
Posts: 6
Joined: Sun Oct 15, 2017 11:00 pm

Re: Nicehash Friends

Post by b0849003 » Sun Nov 05, 2017 1:08 pm

i make some test - and stop at this working config
c=COINNAME d=655360 g=off

0.5GHS = d=71K so for minimal rent 10ghs use 20x71k
Locked