Dead Pool - Nicehash -> PH

[Bitatlas]

Guys, it is someone there with this Nicehash problem, I am the only one or nobody is redirecting hashing power from Nicehash to Prohashing (at least X11)??!

[anssikela]

I have had the same problems with Nicehash -> Prohashing several days now, both algorithms x11 and scrypt.

Other pools work, for example miningpoolhub and coinotron, and Prohashing used to work well too, but if you check it now with Nicehash pool verificator there comes a message from Nicehash:

"Pool host: prohashing.com
Algorithm: Scrypt

Resolving pool host prohashing.com... Error: prohashing.com
Your pool is shown as incompatible therefore we encourage you to contact pool operator to make sure that the pool is using minimal/starting pool share difficulty which is compatible with our service (and thus compatible with today's miners), please send them link to our FAQ on this topic: https://www.nicehash.com/index.jsp?p=faq#faqb3. Thank you!"

Also there is a message in Nicehash front page:

"Pool operators & buyers of hashing power,

We're rising minimum pool difficulties for algorithms id 0 up to including algorithm id 19 due to rising network difficulties of popular crypto coins. Here is a list of all algorithms where first algorithm is id 0, second is id 1, etc. Please make sure that your favorite pools will be compatible with this change. The new difficulties will be doubled current difficulties and will be listed at this page.

The new difficulty will be activated on October 11th 2017 at 09:00 UTC.

Thank you for your using our service and keep on hashing!

Best regards,
NiceHash team"

Links:
https://www.nicehash.com/algorithm
https://www.nicehash.com/pool-operators

[Bitatlas]

I always get this from Nicehash pool verificator. Tried different settings for D:

Pool host: prohashing.com
Pool port: 3333
Pool user: Bitatlas
Pool pass: a=x11 g=off h=1000 d=131074
Algorithm: Scrypt

Resolving pool host prohashing.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 167.88.15.87:3333... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received mining.set_difficulty... Pool difficulty too low (provided=1, minimum=131072)
Waiting for pool to send higher difficulty.
Received mining.notify work... OK
Received authorization result... OK
Received mining.notify work... OK
Error: Difficulty too low.

[AppleMiner]

I always get this from Nicehash pool verificator. Tried different settings for D:

Pool host: prohashing.com
Pool port: 3333
Pool user: Bitatlas
Pool pass: a=x11 g=off h=1000 d=131074
Algorithm: Scrypt

^^^^^^^^^^^^^^^^^^^^
Why does it say Algorithm: scrypt?
if you have a=x11 shouldnt it say x-11 algorithm?
Is there some setting you have to set to tell it x11 vs scrypt on the nicehash side also?

[GregoryGHarding]

user error, either they selected a scrypt miner and trying to mine x11, or vicaversa

[Bitatlas]

Guys,

Now I could connect to the pool but Nicehash is showing a negative Delta of 67% which means that the speed accepted by the pool is 67% bellow.

If someone could help me understand this I would be extremely thankful.

[GregoryGHarding]

i have no knowledge of nice-hash, nor is it exclusively supported here. any issues or learning curves should be taken up with nice-hash.

[AppleMiner]

Are you in the pool mining or solo mining?
If solo and using nicehash are you using g= setting?

[Bitatlas]

Hi Apple,

Solo mining only... and I have g=off

[Bitatlas]

Guys,

I made a ticket to Nicehash explaining the situation and they answered:

"Hello!

Please note that some pools have option to set custom workers difficulty. Usual that is workers password. In that case you need to enter in the password window d=16383 if pool verificator shows you that the minimum pool difficulty is 16383.

Example:
»Received mining.set_difficulty... Pool difficulty too low (provided=2048, minimum=16383)«
worker = nicehashminer
workers password: d=16383

Kind regards,
NiceHash Team"

I already tried before to set d= the minimum that NH pool verificator show.
Now I tried the d=16383 and the order continues to go dead.

Is there any chance that the "d=" it's not working from PH side?

Chris and Steve, can you do something about this?