Nicehash Friends

[3Moose]

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

[3Moose]

To read the blogs over these last several months, this place was full of NH miners..... guess they all left.

[bsock]

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]

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]

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]

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