Oh, this! Proxy is working in "compatibility mode" by default, to ensure that all, even very old miners, will work with it with no issues. If you have some modern miner (cgminer, poclbm or so), you can run it with --real-target. Currently the proxy is filtering low-diff shares, so you may see different numbers in the miner and on the pool. Thanks to --real-target, your numbers in miner won't be screwed anymore.
yes, I do that:
user 27107 1.6 1.3 28920 13692 ? Sl 00:42 1:06 python ./mining_proxy.py -o stratum.btcguild.com -p 9332 -rt
there is no difference, still around 5% missing (I am using some custom miner):
Example vardiff worker:
total_unsolved_gws(superK)=4640(41.46%), total_solved_gws(superK)=6552(58.54%), (solved+unsolved)=11192
Example diff1, DE server worker:
total_solved_workunits_count=30078.00
total_failed_workunits_count=16128.00
If you compute second, total_solved_workunits_count is 65% of (total_solved_workunits_count + total_failed_workunits_count)
So I need a diff1 stratum connection to test if vardiff causes this difference or something else (network, etc.)
