When an MDS worker looks offline, accepted shares are not paid MDS
Read the last share time, then that row’s nonces/s. The balance still belongs to the whole MSS. With no last share, online is unknown, not offline, and the balance is not set to 0.
| What you see | On this page | Do not treat it as |
|---|---|---|
| Worker online | That name’s last share is within 15 minutes | A machine heartbeat, or a slice of the balance |
| Worker offline | The last share is older than 15 minutes | Unpaid becoming 0 |
| No last-share time | Online is unknown | Offline |
| Miner screen 142 acc / 0 rej | A sample count from that program | Paid MDS on this page |
| Account nonces/s disagrees with the sum of rows | Both are shown as the pool returned them | A requirement to force one number |
When one machine seems to have stopped, read that worker’s last share on MDS monitoring before you change unpaid to 0. “Online” on this page means the name had a share within 15 minutes. It is not a machine heartbeat. The accepted count on the miner screen is not paid MDS.
What one worker row holds
Each row has a name, that row’s nonces/s, and the last share time. A share inside 15 minutes is online. Older than 15 minutes is offline. If the last share time is missing, or it sits in the future, online stays unknown and is not labeled offline. Unpaid, paid, and the 24-hour allocation belong to the whole MSS. They are not split by worker name and not divided in proportion to rate.
Share counts on the miner screen
The official status sample shows Your Shares: 142 acc / 0 rej, an expectation of 1 block per 4096 shares. Those are counts and an expectation in that program’s terminal. This page does not show accepted, rejected, or luck. The guide’s note for share rejected: Duplicate share or Low difficulty says a block just solved by the network makes a stale share, or latency makes a duplicate, and the miner fetches a new job. That is a submit result between miner and pool. It is not a condition that clears the balance here.
Which step to take
- Last share inside 15 minutes and the rate still in nonces/s: that row is submitting.
- An older last share: that row is offline by this page’s rule. Check that the miner still points at LuckyPool and still uses this MSS.
- Not-found for the whole page is not an offline worker. Go back to whether the address and the pool match.
- If the account rate and the sum of the rows disagree, both stay as the pool returned them. This page does not collapse them into one number, and it does not rewrite unpaid.
A diagnosis marked as an illustration
The case below is an illustration. Unpaid on the address is still 1,049,600 MDS. The worker named cpu has a last share 20 minutes ago, so this page marks it offline and leaves unpaid unchanged. The worker named gpu has a last share 2 minutes ago and is online. If the account rate is 1,500, it shows 1.5 Knonces/s. If the two row rates do not add to 1,500, unpaid is not split in proportion, and the offline row is not given a balance of 0. If the miner terminal still prints 142 acc / 0 rej, 142 does not enter paid.
Limits
Fifteen minutes is how this page reads “still submitting”: a last share inside that span marks the row online. Next, check whether the address is this MSS and why the three amounts stay apart.
Common questions
Does an offline worker clear unpaid?
No. Offline only means that name’s last share is older than 15 minutes. Unpaid, paid, and the 24-hour allocation still belong to the whole MSS. With no last-share time, the state is unknown, not offline.
Where do I read 142 acc / 0 rej on the monitor?
This page has no such line. That pair is the accepted and rejected count in the official miner status sample. Paid is MDS the pool has transferred, not a share count.
Should worker rates add up to the account rate?
This page does not require that and does not add them for you. The account rate and each row are shown as the pool returned them, in nonces/s. When they disagree, keep both. Do not rewrite unpaid from either side.