Quote from: martynw2000 on April 10, 2014, 12:24:37 PM

I have a question about the reported hash speeds on LeaseRig.

I have two rigs that are mostly hired out all the time. The reported speeds they are running at when being hired are NOWHERE NEAR the speed of the rig itself. For example, I'm running at a constant speed of 7.2Mh/s, and on the site its telling me 0.89Mh/s. Sometimes it's higher, perhaps fluctuating between 1 and 5 Mh/s. When it's not being hired, I'm mining at clevermining.com or perhaps multicoin.us and the reported speed is about right at 7.2mh/s. So what's going on?

I'm thinking that perhaps the pools my hirers are choosing aren't so good, and therefore the share rate is down because of it. However this destroys my reputation - because people can see a graph of my rig's reported speed, and if they see it hovering between 1-5Mh/s when I'm saying it's 7.2Mh/s, they are going to go elsewhere. It's not my fault my hirers are choosing bad pools.

I also suspect the reported speed on Leaserig.net is completely different to that shown at a pool for some reason. If my rigs really were mining at only 1Mh/s then people would have complained - but none have yet, so I can only assume all is well. I just wish the hash rate on the site could be a true figure of my rig's performance.

Anyone else noticed anything or has any comments?

It's because you are using LeaseRigProxy.
That thing reports hashrates based on accepted shares. If the pool has a high share difficulty (512, 1024 or so on) your hashrate will be shown much lower than it should be.
If the pool has a high share difficulty (16, 32, etc.) your hashrate will be shown higher than it should be.

The fix to this is:
Don't be lazy, set up "Method B", which is the API.
Instructions here: >>>CLICK HERE<<<

I myself used the proxy since I was lazy, but the hashrate was highly incorrect, so I took some time and setup method B.