Accepted means a submitted share met the current share difficulty target and passed validation.
Rejected means the share did not pass one or more checks.
On this pool, Accept Always is disabled. Share quality is enforced by the active difficulty target, so invalid or stale shares are rejected instead of being force-accepted.
Common reject reasons
- Share hash does not meet the assigned share target (difficulty too low).
- Stale share after a new job arrived (high latency or delayed submit).
- Duplicate share already submitted for the same job.
- Invalid nonce or malformed submit payload.
How to reduce rejects
- Use the closest stratum endpoint and stable low-latency network path.
- Keep miner software and firmware updated.
- Avoid overloaded rigs and verify clocks and power tuning are stable.
- Use correct worker credentials and avoid duplicate worker sessions.
Tip: a small reject rate can happen naturally, but persistent spikes usually indicate network delay, unstable tuning, or a worker configuration issue.