dzer916

Just finished setting up... it doesn't seem to work with 10.0.

It seems that in v10.0 Claymore does not use the specified pool and falls back to using ~~us1.ethpool.org:3333~~ an arbitrary pool and bypasses the request_handler. @JuicyPasta @drdada any ideas? ...

[Wireshark](https://www.wireshark.org/), but my experience with it is limited I found another proxy for Claymore, check it out [https://github.com/LostSoulFly/MinerProxy](url) I have not tried it yet.

@drdada I had allpool set (I changed the WAN IP from before) New script looks like this: `ethdcrminer64.exe -epool 175.5.10.15:8008 -ewal .Miner01 -epsw x -mode 1 -tt 68 `

@drdada @mhousser OK, after removing the -allpool option it seems to work. However, the time to transmit the share to the pool seems to increase little by little and eventually...

Going to run CM v10 without the proxy for a bit and see if the transmission times are the same... for science.

I only have one miner set up, but the additional one comes from the proxy (it creates a new worker .rekt) I enabled the email notifications for "down" workers and...

Nope, I got only 4 email notifications, and yes I see the second miner. Correct me if I am wrong, but I assume Claymore will not find a share every...

Alright, so using the proxy with CM v10 after Byzantium adds a to the transmission time. It can go as high as ~800ms. This translates to roughly 6-9% stale shares...

Well it is always easier to hack stuff up in Linux :) Have you tried those?