Quote from: Doucesti on November 14, 2018, 10:25:06 PM

Quote from: kerney666 on November 12, 2018, 07:53:15 PM

You know, this is a little interesting. Nanopool has a broken rpc implementation which causes issues when e.g. submitting two or more shares in quick succession. Now, we assumed that we'd still get replies for all submitted shares, but there could cases where they actually drop rpc requests. I didn't do the fix though, need to check with todxx.

Comparing pool payouts is a different thing though. Unless you're sure the pools hit exactly 100% avg luck over the same period, it doesn't say much. The poolside hashrate displayed in the miner should match your miner hashrate minus dev fee and any rejected shares. If that looks good, we can't really do much more from a miner dev perspective. If that number is ok, but the pool reports a different hashrate, something is fishy.

After mining for a while on supportxmr, everything was good, readings on miner were avg 1850h/s and pool 1790h/s.
Yesterday my readings were avg 1850h/s and pool was down at 1750, now I'm down at avg 1850h/s and pool 1662h/s.

I've also switched to this pool yesterday, two really slow miners sometime before readings. I'll try switching them back to another pool..!

Supportxmr is generally nice allowing a static diff for maybe 1 share every 5 secs. Its not super nice to run that way 100% of the time, but if youre nervous about poolside hashrate not lining up with miner hashrate, thats the way to go. 10k diff is the lowest allowed though, so add +10000 after your wallet.