Rejected Shares in Pearl / PRL Mining Explained
Published: June 2026 · Category: Troubleshooting
What Is a Rejected Share?
A rejected share is a result submitted by your miner that the pool does not count as valid work. Rejected shares can happen on every mining pool, but the rate should normally stay low. A small number of rejects is not automatically a problem. A high reject rate should be investigated because it can reduce your effective contribution to the pool.
Accepted Shares vs Rejected Shares
An accepted share means your miner submitted work that matched the pool difficulty and was counted by the pool. A rejected share means the submitted work was not counted. PearlPool.cloud shows both values openly so miners can verify their connection quality and pool behaviour.
| Accepted share | Counts toward your pool contribution and PPLNS share window. |
| Rejected share | Not counted for payout accounting. |
| Candidate | A gateway-submitted block candidate/proof, not a confirmed block. |
| Confirmed block | A real block accepted by the network and shown separately in the Blocks API. |
Common Reasons for Rejected Shares
- Stale job: Your miner submitted work for an old job after a new block/job was already sent.
- Network latency: The miner or pool connection is slow or unstable.
- Duplicate submit: The same share was submitted more than once.
- Wrong wallet or worker format: The miner login format is malformed.
- Unstable overclock: GPU memory/core settings are too aggressive.
- Miner compatibility: The miner version may not fully match the pool protocol.
- Pool-side timeout: Backend gateway or candidate submission can time out.
What Is a Healthy Reject Rate?
For a stable mining setup, the accepted share rate should normally be high. A few rejected shares over time can be normal. If your reject rate stays above a few percent for a long period, check your miner logs, connection and GPU stability.
Very small miners can show high reject percentages with only a few shares. For example, 1 reject out of 5 total shares looks like 20%, but the sample size is too small to judge long-term stability.
PearlPool.cloud Candidate Submissions
PearlPool.cloud shows Candidate Submissions separately from confirmed blocks. Candidate submissions are gateway-submitted proofs or block candidates being tracked transparently. Confirmed pool blocks are shown separately through the Blocks page and API.
Candidate Submissions = submitted gateway proofs/candidates, not confirmed pool blocks.How to Troubleshoot Rejected Shares
- Check your worker format:
YOUR_PRL_WALLET.WORKER. - Confirm the pool endpoint is
stratum+tcp://pearlpool.cloud:5566. - Reduce aggressive GPU overclocks and test again.
- Check your miner version and miner logs.
- Make sure your internet connection is stable.
- Compare accepted and rejected shares over at least 15–30 minutes.
- Check the Leaderboard and Stats page for your wallet.
Pool Transparency
PearlPool.cloud exposes accepted shares, rejected shares, candidate submissions, workers, hashrate and readiness data through public pages and API endpoints. This helps miners verify whether the pool is healthy and whether their rig is contributing correctly.
Mine Pearl / PRL with Transparent Stats
Use PearlPool.cloud to monitor accepted shares, rejected shares, workers and candidate submissions openly.
stratum+tcp://pearlpool.cloud:5566