If an RVN Worker is offline, is that rejected shares or a zero balance?
Read that row's offline flag and last seen. Amounts stay on the address. This page has no rejected-share count.
| What you see | On this page? | Meaning |
|---|---|---|
| Worker offline | Yes, the pool's offline flag | That row is marked offline. Not a zero balance |
| Last seen | Only when the pool sends a time | That row's last heartbeat. No time means unknown |
| Rejected shares | Not shown | Do not infer a reject count from offline |
| Unpaid balance | On the address | Not copied or cleared because one row is offline |
A Worker marked offline means 2Miners marked that rig name offline. It is not a rejected-share ratio, and it does not change unpaid balance on RVN monitoring to zero.
What is on that row
The offline flag is the pool's offline state for that Worker. Last seen appears only when the pool sends a time. No time is unknown. It is not proof the rig was just online, and it is not proof it never connected. That row's hashrate can be unknown as well. The public API has share ranges and Worker hashrate over a range. This page does not show how many shares were accepted or rejected. 2Miners help says share difficulty does not affect miner rewards. That sentence does not mean offline equals zero rewards.
What to inspect
Check that the name is the rig you set. See address and Worker format. Then read that row's last seen and hashrate. Read unpaid, paid, and the 24-hour reward on the address. If address hashrate is still present and only one row is offline, do not treat the whole wallet as stopped.
Branches
- One row is offline and the address amounts are still there: keep reading amounts on the address. See rewards and payouts.
- One row is offline and its hashrate is blank: hashrate is unknown. Do not write it as zero. See how to read hashrate.
- Saving that offline Worker as its own device record counts toward this project's device slots. Seeing it under the original wallet does not add a slot. Free is five saved devices per project. Pro is 50.
Example
Illustrative, not a recorded outage. Unpaid on the address is still 40 RVN. rig-a is online and has a hashrate. rig-b is marked offline and has no last-seen time. Read rig-b as offline with last seen unknown, and keep unpaid at 40. Do not write rejected shares at 100 percent, and do not change 40 to 0. This page cannot say how many shares rig-b rejected.
Next step and limits
Next, check that row's offline flag and last seen on RVN monitoring, then check on the miner whether the network and the software are still submitting to the pool. This page cannot restart a miner, cannot list reject reasons, and cannot turn offline into RVN already lost.
Common questions
Does unpaid become zero when a Worker goes offline?
No. Unpaid stays on the address. An offline row marks that rig name. It does not set the address balance to zero and does not copy the balance onto the row.
Can this page show how many shares were rejected?
No. Offline and last seen are not a rejected-share count. The API has share ranges, and this page does not show accepted or rejected counts.
Does a missing last seen mean the rig never connected?
That conclusion does not follow. No timestamp means that field is unknown. Whether the miner is still submitting has to be checked on the miner and in the pool stats, not decided from a blank heartbeat.