Skip to main content

Worker statuses

A look at the three states of your worker devices

Worker statuses, hashrate metrics, and telemetry charts are calculated statistically from submitted valid shares and are provided strictly for monitoring and informational purposes (cl. 4.15 ToS). Maintaining hardware health, firmware stability, and network connectivity is the sole responsibility of the user (cl. 5.6–5.8 ToS)

Once you connect a worker to EMCD, it appears in your account within 20 minutes.

The device is then given one of three statuses:

Active

A worker counts as active when it submits shares to the pool steadily and without rejects for several hours. The indicator for such a worker is green.

We have a set of articles on how to connect a device to EMCD. You can find them in our connection guides.

Unstable

A worker gets this status in two cases:

1. When the hashrate changes sharply and significantly

For example, when a device connects or disconnects and the hashrate swings from 0 to 100%, or when rejects spike.

The first time you connect, or after you switch stratums, your worker shows up in the list of unstable devices, because it spends the first hour after connecting syncing with the pool. After that, the device moves to the active list.

2. When rejects stay above the normal level
For example, if a worker has been running for several hours with a reject rate of 15% or higher.

A high reject rate can come down to a few things:

  1. Network latency, which affects how quickly data travels from your worker to the pool. Always select the geographically closest stratum server.

  2. Late or invalid shares, which also add to the number of rejects. To prevent disconnections, ensure you configure all three stratum addresses (primary, secondary, backup) on your device (cl. 5.2–5.5 ToS).

  3. Third-party firmware fees (Dev Fee): Custom firmware periodically switches hashrate to developer pools, which may register as temporary reject spikes or drops. The pool is not responsible for the performance, compatibility, or side effects of third-party firmware (cl. 5.9 ToS)

A reject rate of up to 1–2% is standard, and a small variation in hashrate is normal in mining.

If your reject rate goes up, that can point to an issue with your worker settings or your internet connection. We recommend checking how stable your connection to the stratums with a ready-to-use command line.

The indicator for an unstable worker is yellow.

Offline

A worker counts as offline when it hasn't submitted shares to the pool for one hour. The indicator for an offline worker is red.

If you've disconnected a worker from the pool and want it gone from your device list, just leave it disconnected. The worker disappears from the list automatically after 24 hours without activity. There's no need to delete it manually.

If mining status notifications are turned on for your account, you get a push, an email, or a Telegram message every time a status changes. We explain how to set up worker status notifications in this article.

Please note: Notifications are provided as an auxiliary monitoring tool. The pool is not liable for delayed, intercepted, or undelivered alerts caused by third-party communication networks, mobile operating systems, or Telegram service disruptions (cl. 5.9, 6.4 ToS).

Did this answer your question?