After blocking even more ip's and domains exept the ones from nanopool.

2018-01-02 05:05:16|#  connected to: zec-eu1.nanopool.org:16666
2018-01-02 05:05:46|connect failed

What happens here is that the program secretly wants to connect to a dev fee pool waits 30 second for timeout and than shuts down

And we have to block
213.32.74.230
213.32.29.150
94.23.20.210
213.32.29.150
94.23.199.191
188.165.195.21

and the range
213.32.0.0 To
213.32.255.255

This causes the miner to go in Server not responding - retrying mode.
So without flypools server's online this stupid miner does noting

We also have to block 192.99.33.207 3443 seems to be another server of flypool that this program wants to connect with

I can confirm that all the unencrypted mining.submit shared goes to my own wallet entered. But there is an encyptred TLS connection to flypool and i'm not yet sure what it does. It looks for now that no big data that can include share's is going to flypool but i have to monitor for maybe 12+ hours to be sure.

There is some good news, let's mine on nanopool with flypool on 192.99.160.185 3443 blocked. And we will see in a few days if a 1070 can make the reported 505H/s without dev fee.

I advise to keep a good copy of this patched version of zm cos nekidtruth will patch this fix.

Greetingz From,
Dikke Hans Jansen

I analysed this program

While mining on nanopool and blocking flypool in windows firewall(192.99.160.185) an error comes up: connection closed by server r:2

This means one of the developers is still taking fee from me or at least there is always an active keep alive connection to flypool.


I have been mining for 2 days now and avg did go down from 490H/s to 456.5H/s

See image for proof