why mining pool shares get rejected stale invalid duplicate

05 September 2026

A rejected share is a signal. The signal points to a specific problem. Stale shares, invalid shares, low difficulty shares, and duplicate shares each tell you something different about your mining setup. Understanding the difference saves you time and lost earnings.

Stale shares

A stale share arrives too late. The pool has already moved on to the next block candidate. Latency is almost always the cause. Your miner found a solution, but the network delay between your rig and the pool’s server meant the solution was useless by the time it arrived.

Diagnostic steps: Check your ping time to the pool’s stratum server. Anything above 100 milliseconds is a problem. Consider switching to a pool server geographically closer to you. If you mine from a residential connection, latency can spike during peak hours. A wired Ethernet connection beats Wi-Fi for stability. Some miners reduce their submitted hashrate slightly to lower stale rates, but that is a tradeoff.

Invalid shares

An invalid share contains a wrong answer. The pool’s software checked the cryptographic proof and rejected it. This usually means something is wrong with your hardware or your mining software.

Diagnostic steps: If you overclocked your graphics card or ASIC, back off the clock speeds. Memory errors from overheating cause invalid shares. Check your core and memory temperatures. If your rig has been running for weeks without a restart, memory can degrade. Reboot everything. Update your mining software to the latest stable version. If one specific card consistently produces invalid shares while others do not, that card likely needs repair or replacement.

Low difficulty shares

A low difficulty share means the work you submitted was too easy. The pool expects solutions above a certain difficulty threshold. If you set your miner’s difficulty too low manually, or if your worker configuration is wrong, you generate shares the pool will not accept.

Diagnostic steps: Look at your miner’s configuration file. Remove any manual difficulty setting unless you know exactly why you added it. Most pools handle difficulty automatically. If you are using a proxy between your miner and the pool, check that it is not altering difficulty values. On some pools, you can adjust minimum difficulty through the pool’s web dashboard - set it to the pool’s default.

Duplicate shares

A duplicate share means you submitted an identical solution twice. The pool sees the same work, same nonce, same result - and rejects the second copy. This is almost always a worker management error.

Diagnostic steps: Check that each mining rig has a unique worker name. If two rigs use the same worker name, the pool cannot tell them apart. Some mining software will submit the same share from multiple instances if you run two copies with the same configuration. Never run two instances pointing at the same pool with the same wallet and worker name. If you set up multiple workers intentionally, give each one a distinct label like “rig1” and “rig2”.

A note on this site

As of August 31, 2026, taponeth.vip hosts information about THE AMERICA PARTY (TAP) on the Base chain. The contract is 0x818895552650c8bbE89043FAaB16b6E9C906Ec2b. Trading volume over the past 24 hours was zero. Only one transaction occurred. There are 30 trading pairs. The liquidity of $215,324.55 is not thin, but the lack of activity suggests the market is dormant.

None of this affects how mining pool shares work. The rejection categories - stale, invalid, low difficulty, duplicate - apply regardless of the token or chain. They are universal symptoms of mining infrastructure problems.

If you see a high percentage of any single rejection type, start with the diagnostics above. Stale shares point to your connection. Invalid shares point to your hardware. Low difficulty shares point to your configuration. Duplicate shares point to your worker naming. Fix the cause, and the rejection rate drops.

Back to mining