Pool host: mine.zergpool.com
Pool port: 4233
Pool user:
Pool pass:
Algorithm: NeoScrypt
Resolving pool host mine.zergpool.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 198.251.81.136:4233... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_difficulty... Pool difficulty too low (provided=512, minimum=2048)
Waiting for pool to send higher difficulty.
Received mining.notify work... OK
Received mining.notify work... OK
Error: Difficulty too low.
Test with custom diff:
Pool host: mine.zergpool.com
Pool port: 4233
Pool user:
Pool pass: c=BTC d=2048
Algorithm: NeoScrypt
Resolving pool host mine.zergpool.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 198.251.81.136:4233... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_difficulty... OK: difficulty=2048
Received mining.notify work... OK
Pool verification process is complete. Tested pool is compatible!
Warning: Selected pool did not request min or higher working diff: 16384 Check FAQ!
Thanks, for giving a test there. Does this warning create troubles in further mining ? I will check config setup
With diff=2048 miners often disconnect from pool due to "low difficulty" error . With diff=16384 (recommended minimum for nicehash) I did not noticed disconnects but it may be too high diff for some coins. I suggest to set up auto adjust. Usually yimp pools set diff equivalent 5-15 shares per minute.
Yes, the issue is that we have some low difficulty coins there. If the difficulty is set higher than one of the a mined coins, it will be forced down to fit the lowest coin's difficulty.