The reason that the hashrate displayed by the mining pool is lower than the local miner’s might be due to many aspects. The reasons are as follows.
Normal hashrate loss
Miners should note the possibility that not all local hashrate measured by your machines will be converted to valid hashrate for pools thus contributing to finding a block, though there should be a huge difference. Especially mining with GPU devices, some factors below may lead to this normal hashrate loss.
- Network latency: Network latency will cause a small percentage of hashrate loss as failure of submitting hashrate from the miner to the mining pool.
- Devfee setting on mining software: 0.5% to 2% of the hashrate will be deducted and converted into developer fees.
- Excessive overclocking: Excessive overclocking will lead to a big loss on hashrate.
Generally, the error rate within 5% (GPU) and 2% (ASIC) between the local hashrate and the 24-hour average hashrate of the mining pool courts as normal error range.
You may refer to the explanation of this issue by Claymore mining software.
Abnormal hashrate loss
If the deviation between local hashrate and the hashrate displayed on the mining pool is too large, please check the rejection rate and hardware settings.
- If the rejection rate is comparatively high, it is usually due to network issues. It leads to the low submission of hashrate from miner to the mining pool. You may check the routers, switches, network cables, interfaces and so on in order to define the issue.
- If the rejection rate is normal, please check the hardwares of the miner and if there is overclocking, try to restart the miner, replace the hashrate board, and reduce the frequency in order to solve the problem.