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. :)

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. :/

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?