Why am I getting a high percentage of stale shares?

  • Updated

A stale share occurs when your miner submits a share to the mining pool after the pool has already moved on to the next block.

What Causes a Stale Share?

Since a new block is mined about every 10 minutes, sometimes your miner will still be submitting shares to a block that has already been found while the mining pool has moved on to the next block. As a result, a small percentage of stale shares is expected during regular operation, with an average stale rate of .5% or lower, depending on your miners.

Stale Shares Spike-1If you see a spike in stale shares, it could be due to network latency or an issue affecting your connectivity to the mining pool. The slower your network is, the longer it takes for your miners to receive notification about a new block.

One thing to remember: Some mining pools will merge stale and rejected shares into one rejected shares count without differentiating between the two. Foreman shows shares reported by the mining pool, which can cause only rejected shares to be shown depending on the pool you are using.

Reducing Network Latency

Should you determine that high network latency is causing your operation to experience an abnormally high percentage of stale shares, there are a couple of things you can check. The first thing you can check is the speed of your internet connection. Upgrading to the best available package from your provider, preferably fiber optic, will ensure your miners are submitting their shares to the mining pool as soon as possible. Another thing you can try is reducing the amount of non-mining related activity occuring on your network. Removing non-essential activity allows your miners to take advantage of the full capacity of your network.

If you need assistance with a network audit to determine the cause of your spike in stale shares, please email us at contact@obm.mn, and we'd be happy to help.





Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request



Article is closed for comments.