Reduced shares received by pool with Claymore 9.7 + proxy 1.1

[jimmykl]

I'm running Claymore 9.7 with the new v1.1 proxy, using fake WAN addresses and mining at ethermine.org. I restarted my rigs after setting it all up and the good news is I don't get the local proxy warning any more and the fee address swap is working.

But the number of shares received by the pool has dropped (see screenshot). I understand the effective hashrate varies a lot and Claymore and the pool's reported rate are the same but the actual shares received in the bottom graph before using the proxy were ~380–430 and with proxy I'm getting ~330–390.

Is this expected? Maybe something to do with how Claymore processed his fee's shares? Or is there a known slowdown due to using the proxy? Or something else?

[drdada]

Hello, No obviously, this is not expected. Did you set some DNS redirection ?

[jimmykl]

Hi @drdada Not that I'm aware of… the rigs network adapter settings are:

I haven't touched the hosts file

[drdada]

It sounds good. Are you familiar with Linux ? I would recommand to build a linux gateway and redirect devfee via this way. I also detect a hashrate drop sometimes and i'm wondering if the proxy is still undetected. I'm still testing this "gateway tricks"

[drdada]

Can you send me a PM on gitter please, we will try something together.

[jimmykl]

I am familiar with some aspects of linux but not sure how to build a gateway. I have a raspberry pi I use for pihole (dns based ad blocking) and it would be perfect for this as it's on all the time. I'll pm you shortly

[paullee29]

Hi DrDada Thanks for your work, but I think I am having the same problem, it seems that when I am redirecting the packets, I get a reduced share count and a reduced effective hashrate, even though it reports the proper one to ethermine.

I will test again and will do 24 hour testing on each and report back.

[jimmykl]

Yes I tried a virtual network adapter and redirecting the port and both seem to get picked up. It looks like Claymore has a foolproof way to detect when this is happening and reduce the shares. I'll probably just pay the fee when dual mining or use ethminer.

[khaman1]

Try Claymore 9.8. They also claim that their newest code willl do much less invalid and outdated shares

[drdada]

I'm aware of the detecting issue. We are working on it. ATM you have choices:

• Pay the fee
• Use the -nofee 1 arg (and still having reduce share)
• Use Ethminer (free but with lower hashrate speed) - You can also use MinerLamp as addon.

[khaman1]

I have been using Ethminer in a month and I'm pretty sure 99% people will say ethminer hashrate is always higher than or probably equal to Claymore. The problem of ethminer is no watchdog but we can run a code to check the GPU states continuously. I also have the share stale when using your code but I didn't check the loss. I'm switching back to ethminer. Still ethminer is an open source and contributed by community, so it would be intuitively better.

[khaman1]

I didn't try the dual mining of Claymore. Its latest version claims no effect on Eth hashrate when mining another coin during the "extra cycle" (I don't get this term btw). But it seems like ethminer uses that to mine more Eth because the reported hashrate after submitting the share is remarkably higher.

[drdada]

@khaman1 Try MinerLamp (see link above) if you want watchdog for Ethminer.

[khaman1]

I have written a short code to monitor it. My rigs sometimes get GPU error and have to restart the computer, not just the application. Not pretty sure how MinerLamp handles that but doing restart and copy the shortcut of the code and ethminer to Start-up application (Run shell:startup) can do the job. Anyway, I will try MinerLamp

[MichaelA2014]

Is there any benefits of 9.7 over 9.6? I am using 9.6 and it's churning away just fine. No noticable drop. Of course maybe I was loosing shares all this time on Nanopool? Who knows...

[vctender]

Any updates? How is the proxy (technical) recognized by claymore?

[sb3rg]

Seeing warning from Claymore miner v11.1 that using a stratum proxy will result in more stale shares. I'll let it run over night to see if it's legit, but perhaps someone else on this feed has already tested it? An update would be very helpful. Thank you!

[drdada]

@sb3rg If you got warning it means Claymore spotted the proxy and apply some slowdown (stale share, reduced shares or higher power consumption). https://github.com/JuicyPasta/Claymore-No-Fee-Proxy#claymore-warns-me-something-about-local-proxy If you did the Wan trick you should bypass the detection system (and not having warnings). So v11.1 (and probably higher versions) are not compatible anymore.

@MichaelA2014 Try to mine with ethermine, you'll got more stats about stales shares.

@vctender Since the software is closed-source we don't know how it detect proxies. The only way to know that is via multiples tests (wireshark, process monitor, ...).

[JsBergbau]

This are my rates with devfee removal Proxy. I've used another so far, however it is not compatible with v11.2 so I've now switched to your python proxy. Switch occured right now, so lets see. But I think Claymore can't detect it like so far right now. The whole occured when switchting to 11.2, Did some other maintanance stuff at well- However I have sometimes the same low effective hashrates as jimmykl after running proxy. I think its another issue, because when claymore would detect my proxy, it would always give lower hash rates and not only sometimes.