- Steve Sokolowski
- Archived posts: 4559
- Joined: Aug 27, 2014
Nicehash-specific ports now available
We're proud to announce the final release of Nicehash-specific ports, which are now available for immediate use.
By default, the stratum protocol declares that an initial difficulty needs to be sent to miners right after connect, and then the miner is to send a username and password back. To comply with this specification, Prohashing assigns a difficulty suitable for most miners and then, if the miner requests a static difficulty with the "d=" password argument, reassigns that difficulty when the password is received. However, Nicehash requires a minimum difficulty, and uses this initial difficulty to determine whether a pool is compatible with its service. Since Nicehash miners don't wait to see what difficulty is assigned after the "d=" password argument is received, Nicehash returns errors even if the "d=" argument is above their minimum difficulty.
Like algorithm-specific ports that prevent some mining rigs from declaring incompatibility, Nicehash-specific ports send a very high initial difficulty to trick Nicehash's "pool checker" algorithm into thinking the pool is compatible. That allows enough time for Nicehash to authorize and actually send the "d=" password argument the customer wants to use.
The port numbers for Nicehash-specific ports are available in the documentation at https://prohashing.com/help.html#tuning-ports. Feel free to post your comments and suggestions for improvement!
By default, the stratum protocol declares that an initial difficulty needs to be sent to miners right after connect, and then the miner is to send a username and password back. To comply with this specification, Prohashing assigns a difficulty suitable for most miners and then, if the miner requests a static difficulty with the "d=" password argument, reassigns that difficulty when the password is received. However, Nicehash requires a minimum difficulty, and uses this initial difficulty to determine whether a pool is compatible with its service. Since Nicehash miners don't wait to see what difficulty is assigned after the "d=" password argument is received, Nicehash returns errors even if the "d=" argument is above their minimum difficulty.
Like algorithm-specific ports that prevent some mining rigs from declaring incompatibility, Nicehash-specific ports send a very high initial difficulty to trick Nicehash's "pool checker" algorithm into thinking the pool is compatible. That allows enough time for Nicehash to authorize and actually send the "d=" password argument the customer wants to use.
The port numbers for Nicehash-specific ports are available in the documentation at https://prohashing.com/help.html#tuning-ports. Feel free to post your comments and suggestions for improvement!
