Pool initial difficulty changed

[Steve Sokolowski]

Today, I changed the initial difficulty of the pool from 1024 to 2048. This difficulty is assigned to miners that do not provide a "d=" argument at startup. After 3 minutes of mining at this difficulty, it is then changed to a more appropriate level (perhaps even back down to 1024.) The reason for the change is to reduce initial load and to deal with services like NiceHash, which seem to have raised their minimum difficulties yet again.

This change will not affect profitability in any way.

[loszhor]

Thank you, I recently rented some hash power and the renter's miner was running some kind of software that wouldn't allow him to mine if the difficulty didn't hit 1024 minimum within a minute. This had to do with the "test phase" initial difficulty. If it is possible to have a password setting that would skip or set the test phase difficulty to about the 16 - 32 that it has now it would be very helpful. If the new update changes that then never mind.

[Chris Sokolowski]

Try using the r= password argument to set a static work restart time and work around this issue.

[Elanaz]

For NiceHash initial difficulty 2048 too small, as the minimum rented power of 0.10 GH/s
Therefore there will be very useful additional password argument for initial difficulty.

[Chris Sokolowski]

d= sets the initial difficulty manually. There are lots of other password arguments available to tune your miner. Please see https://prohashing.com/help.html#tuning-passwordargs

[loszhor]

Try using the r= password argument to set a static work restart time and work around this issue.

I tried many things including that but the problem was with that particular user's software. If the difficulty was not at a certain level almost immediately it refused to run his miner.