Mining Pool Monitoring With a Mobile App: What Miners Should Track

When monitoring a Bitcoin mining pool through a mobile app, miners should track worker status, pool-reported hashrate trends, rejection rates, alerts, and earnings and withdrawal records. Interpret changes over the relevant measurement window before treating them as evidence of a problem. The app provides remote monitoring and account management without requiring an operator to be physically present at the mining site. It is not a substitute for the ASIC's own management interface, and it does not turn a smartphone into a mining device. Understanding what each figure in the app actually measures—and what it does not measure—is necessary to use it correctly for day-to-day operations.

What a Mining Pool App Can Show

A mining pool app brings operational data and account records into one interface, but each serves a different purpose. ViaBTC's app, for example, documents real-time hashrate monitoring, miner-group management, alert settings, and Watcher URLs for view-only sharing, available on both iOS and Android (ViaBTC). Each of these features answers a distinct question—whether a worker is submitting shares, how much work the pool has recently credited, or how earnings have accumulated—and none of them should be treated as interchangeable with another.

How to Read Hashrate on a Phone

The hashrate shown on a mining pool app is a pool-side estimate calculated from the work represented by shares accepted by the pool for a worker or account over a defined measurement window. It is not a direct read-out of the ASIC's internal hashrate counter. According to ViaBTC's published explanation of its statistics, the platform displays real-time hashrate as an average over the preceding 10 minutes and daily hashrate as an average over the preceding 24 hours (ViaBTC).

This distinction matters in practice. If a miner has just been powered on or restarted, its local display may already show a stable hashrate, while the pool's 24-hour figure remains lower because it still reflects the period before the worker resumed submitting shares. Comparing an ASIC's instantaneous reading against a pool's rolling 24-hour average, without accounting for the different time bases, can create a false impression of underperformance. For a useful comparison, first check the averaging period of the ASIC field. Compare it directly with the pool's 10-minute figure only if both cover the same interval; otherwise, use longer averages covering the same period. After 24 hours of continuous operation, the pool's rolling 24-hour window no longer includes the earlier downtime, but the local and pool readings are still not guaranteed to match exactly.

Short-term variation in share submission is also expected. A mining pool assigns each worker a share target that is deliberately easier to satisfy than the Bitcoin network's block target, so that the pool can measure contributed work far more frequently than blocks are actually found. Because share arrival has an inherent statistical spread, brief fluctuations in the real-time hashrate reading do not necessarily indicate a hardware or network problem.

Worker Status and Alerts

Beyond hashrate figures, a pool app assigns each worker a status label based on observed activity. ViaBTC's documentation defines a worker as active when it is connected and submitting hashrate, offline when no hashrate has been observed for between 20 minutes and one day, and inactive when no hashrate has been observed for more than one day (ViaBTC Help Center). These are pool-defined classifications based on the absence of submitted shares; they do not by themselves identify whether the underlying cause is a power interruption, a network fault, a configuration error, or an ASIC malfunction. Determining the cause still requires checking the miner's local interface, logs, and site conditions.

Alerts reduce the time between a status change and an operator noticing it. ViaBTC's Watcher URL alert feature, available only through the ViaBTC app, checks for worker-offline conditions every 10 minutes and evaluates rejection-rate conditions every hour. It also offers an optional Do Not Disturb period (ViaBTC Help Center). These are alert-evaluation schedules, not continuous hardware-health monitoring; a worker can technically change status between checks. Separately, ViaBTC's account alert settings support app push notifications, email, and Telegram, with notification methods configured through the account's alert settings (ViaBTC Help Center). Rejected shares, meanwhile, are a diagnostic signal rather than a standalone verdict—an isolated rejection or a brief spike within a short window does not confirm a hardware fault, but a sustained increase may justify reviewing the miner's network path, firmware, temperature, and configuration.

A Practical Mobile-Monitoring Routine

For an operator checking on a mining setup remotely, the following sequence can help separate a routine fluctuation from a condition that warrants further investigation:

1. Confirm whether the worker shows an active status.
2. Check pool-reported hashrate using the appropriate time window—real-time for a quick check, daily for a broader view.
3. Review rejected-share information if hashrate appears persistently weak rather than momentarily variable.
4. Compare the same time period against the ASIC's own interface and local logs before assuming a fault.
5. Review earnings and payout records separately from worker and hashrate status, since they follow different calculation and settlement logic.
6. Treat a pattern that persists over multiple checks as more informative than a single short-window reading.

This routine is offered as practical guidance rather than a fixed operational standard; the appropriate checking frequency and alert thresholds depend on the scale of the operation, the hosting environment, and the miner's own risk tolerance.

It is also worth keeping mining-activity monitoring separate from payout accounting. Estimated earnings shown in an app are a projection, credited earnings are amounts recorded under the account's selected payout method, and a withdrawal is a transfer of the account balance. Pools commonly offer more than one payout method—for instance, PPS-based and PPLNS-based accounting—and these differ in how and when rewards are calculated, so a stable worker-status screen does not guarantee identical short-term earnings across methods or across days with different numbers of blocks found by the pool.

Sharing Monitoring Access Without Sharing Account Control

Mining operations that involve a site technician, a partner, or a hosting provider often need to share visibility into worker status without granting control over the account itself. ViaBTC's Watcher URL is documented as a view-only link: it allows a designated recipient to monitor hashrate and worker information without the authority to modify account settings (ViaBTC Help Center). This is a practical example of limiting shared access to only what a task requires—monitoring—rather than distributing full login credentials.

A Watcher URL should still be treated as sensitive information, since it can expose linked mining details to anyone holding the link. Where appropriate, operators may consider sharing such links only with people who currently need visibility and revoking access once it is no longer needed, though the specific process should follow the account owner's own operational judgment rather than a fixed rule.

FAQ

Why is pool hashrate lower than the hashrate shown by my ASIC?

The two figures use different measurement methods and time windows. The ASIC reports a local operating estimate, while the pool estimates hashrate from the work represented by accepted shares over a stated period. ViaBTC uses 10-minute and rolling 24-hour averages. Check the ASIC field's averaging period before comparing the two. A lower pool figure after a restart or brief interruption often reflects the averaging window rather than a fault.

How long should I wait before a new worker appears in a pool app?

This depends on the pool's polling and reporting cycle, and no universal figure applies across all pools. If a worker does not appear within the time you would normally expect based on your pool's documentation, check the miner's configuration and network connection before assuming an app-side issue.

What does an offline worker mean?

Under ViaBTC's definitions, an offline worker is one for which no hashrate has been observed for between 20 minutes and one day; beyond one day, the worker is classified as inactive. The label reflects an absence of submitted shares and does not by itself identify the cause.

Are rejected shares the same as an offline miner?

No. Rejected shares are submissions that were not credited as valid work, which can occur even while a worker remains connected and otherwise active. Worker status and rejection-rate data are related but separate signals, and both should be reviewed together when diagnosing a problem.

Can I share monitoring access without sharing my main account login?

Yes. View-only links, such as ViaBTC's Watcher URL, allow another person to see worker and hashrate information without account-modification rights. This differs functionally from sharing an account password or API key.

Are mobile-app earnings the same as a withdrawal?

No. Estimated earnings are a projection, credited earnings are amounts recorded under the account's payout method, and a withdrawal is a separate transfer of the account balance. These figures should be reviewed independently rather than treated as equivalent.

References

• ViaBTC. ViaBTC App.
• ViaBTC. ViaBTC Pool Hashrate and Mining Statistics Explained.
• ViaBTC Help Center. How to Manage Workers.
• ViaBTC Help Center. How to Set Alerts in the Watcher URL.
• ViaBTC Help Center. New Feature: Watcher Online.
• ViaBTC Help Center. How to Set Hashrate or Rejection Rate Notification?