- General
-
Bugs
0
Under review
Issues with pool difficulty - sending NiceHash power to coinfoundry?
Only tried Scrypt (non starter since it's seemingly unable to modify the difficulty on the fly), and Dagger. Dagger will will actually validate in NH's system (valid reachable pool w good starting diff), BUT when the order gets processed it always seems to fail due to difficulty.
Has anyone else had a similar issue? Bug on the pool side stratum? Inability to send a "d=2.5" etc to the pool?
Only "helpful" info I could get was this:
https://www.nicehash.com/help/why-is-your-order-inactive-red-with-pool-difficulty-too-low-or-incorrect-extranonce-size-error
Customer support service by UserEcho
Adding on - this is the error in the "Established Bridges" in the order screen.
When it first connects it responds with 1.5, and then subsequently it offers up a variable difficulty below the minimum (for Dagger on NH the min is 0.9 I think). Thoughts?
I've never been able to get Nicehash to successfully process an order on our Ethereum based pools. I've contacted their support numerous times only to receive canned replies that indicated that they simply didn't care before I gave up.
Bummer. Thanks for the heads up though.
It's frustrating that it passes pool verification fine but won't actually mine. Having a validator that *operates differently* than their real "stratum bridge" (or whatever it's called), just seems dumb... (Seperate unit tests? lol)
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Pool host: eth.coinfoundry.org
Pool port: 3073
Pool user:*{redacted}*74dd.nicehash1
Pool pass: xx
Algorithm: DaggerHashimoto
Resolving pool host eth.coinfoundry.org... OK
Establishing connection with proxy... OK
Establishing connection with pool 88.99.5.24:3073... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received authorization result... OK
Received mining.set_difficulty... OK: difficulty=1.5
Received mining.notify work... OK
Pool verification process is complete. Tested pool is compatible!
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Lies. :/
Yeah, that's what I was observing as well. But the order always went dead.
I just spun up an Azure machine to screw around with ETH pool settings / etc. If I manage to get NH working, I'll send a Pull Req. :)
Very cool! Thanks for contributing :-)