Bitcoin miners using ViaBTC Pool encounter several related statistics: local ASIC hashrate, pool-side hashrate, share submissions, pool luck, and earnings. These figures measure different things and may cover different periods. Understanding those differences helps you assess mining performance without mistaking normal fluctuations for hardware problems or lost income.
What Pool Hashrate Means
A mining pool estimates hashrate from the work represented by accepted shares over a defined period. It does not directly read an ASIC’s internal performance counters.
A share is a submitted proof of work that meets the pool’s assigned target. Its assigned difficulty determines how much expected computational work it represents. Pool-side hashrate therefore depends on accepted work and elapsed time, rather than simply the number of submissions. If share difficulty changes, equal submission counts can represent different amounts of work.
The same principle applies at worker, account, and pool level. Third-party services may instead estimate a pool’s hashrate from the blocks attributed to it over a selected period. Those external estimates should not be treated as equivalent to the share-based figures on a miner’s account dashboard.
Why Local ASIC Hashrate and ViaBTC Hashrate May Differ
ViaBTC defines real-time hashrate as the average over the preceding 10 minutes and daily hashrate as the average over the preceding 24 hours. An ASIC may display several readings, including a short-term estimate and an average since startup. Its display refresh rate does not tell you which averaging period a reading uses. ViaBTC’s hashrate explanation.
A miner that has only recently started can show a normal local runtime average alongside a lower pool-side 24-hour average, because the latter includes time when the machine was not contributing work.
Share arrivals also vary randomly. Even when a machine operates steadily, the work represented by shares accepted during one 10-minute interval may differ from the next interval.
For a useful comparison, check the averaging period of the ASIC field and compare readings covering the same interval. Where matching short-term averages are unavailable, compare longer averages covering the same period under stable operating conditions. Successive 10-minute readings should not be expected to converge toward a rolling 24-hour figure that includes different operating conditions.
How Shares Become Pool Statistics
Pools assign an easier target than Bitcoin’s network block target so miners can submit frequent proofs of work. A higher numerical target is easier to satisfy, so share difficulty is lower than network difficulty. Occasionally, a submitted share also meets the network target, allowing the pool to submit the corresponding block to the network. Bitcoin Developer Guide.
Accepted shares represent work recognized by the pool. Rejected submissions are not credited as accepted shares; rejection reasons can include stale work, duplicate submissions, or results that fail validation.
When reading share statistics, distinguish actual submission counts from difficulty-normalized share totals. A simple count is comparable as a measure of work only when the shares have the same assigned difficulty. Accepted work, weighted by that difficulty, supports hashrate estimation and reward accounting; rejected submissions help identify work that did not receive credit.
ViaBTC identifies network problems, overheating, and firmware issues as possible contributors to elevated rejection rates. Persistent rejection problems can reduce accepted work and credited earnings even when a local hashrate reading appears normal. ViaBTC’s rejection-rate guidance.
Reading ViaBTC’s Core Mining Statistics
Read each statistic according to what it measures and the period it covers:
- Real-time and daily hashrate: Estimates of accepted work per second over the preceding 10 minutes and 24 hours, respectively.
- Worker status and activity: Indicators that help you check whether a worker is contributing work and investigate interruptions.
- Accepted and rejected share statistics: Information about credited work and unsuccessful submissions. Check whether the displayed values are counts, difficulty-normalized totals, or a rejection percentage before comparing them.
- Pool luck: A comparison of actual block discovery with statistical expectation. It is a pool-wide measure, not a measure of an individual ASIC’s performance. Recent luck does not predict the next block. ViaBTC’s pool-luck explainer.
- Estimated earnings: A projection based on assumptions about mining conditions, rather than a guaranteed amount.
- Credited earnings: Mining rewards recorded to the account under the applicable settlement rules.
- Withdrawal records: Transfers from the account balance. An external withdrawal sends funds to an on-chain address; ViaBTC also supports auto-withdrawal to the user’s own main or sub-account.
A short-term hashrate dip will not necessarily produce an immediate, proportionate change in the earnings figure you are viewing. The figures can cover different intervals and follow different settlement rules.
How the Payout Method Affects Earnings
ViaBTC currently offers PPS+ and PPLNS for BTC mining. These methods handle Bitcoin’s block subsidy and transaction fees differently. Current mining pool information.
Under PPS+, the subsidy component follows PPS accounting and is settled hourly based on current difficulty. The transaction-fee component follows PPLNS accounting and depends on fees in blocks the pool finds. The published fees are 4% on the subsidy component and 2% on the transaction-fee component.
For gross allocated amounts B and T, both measured in BTC, the corresponding net amount is:
Net BTC earnings = (B × 0.96) + (T × 0.98)
Here, B is the gross subsidy allocation and T is the gross transaction-fee allocation for the same accounting period. The two fee rates apply to separate components; they do not form a combined 6% fee.
Under PPLNS, both components depend on blocks the pool finds, with a published 2% pool fee. Allocation uses the miner’s share of pool hashrate over the last five difficulty rounds, and distribution follows six confirmations of the relevant block. These rules also apply to the PPLNS transaction-fee component of PPS+. ViaBTC’s reward calculation rules.
Pool luck can therefore affect PPLNS-related earnings even when the miner’s own hashrate is steady. Transaction-fee variation also changes the rewards available for distribution.
Why Daily Earnings and Withdrawals May Not Match
ViaBTC’s Profit Detail uses UTC+8. A calendar day in that reporting system is different from the rolling 24-hour period used for daily hashrate. Check the date boundaries before comparing earnings with hashrate. Profit statistics timing.
Settlement and withdrawal are separate steps. For external BTC auto-withdrawals, ViaBTC publishes a minimum of 0.001 BTC and a daily processing window of 10:00–18:00 UTC+8. Transfer eligibility also depends on the selected payout settings. Auto-withdrawal to the user’s own ViaBTC main or sub-account does not use that external minimum, provided the amount is greater than zero. Auto-withdrawal guide.
An amount credited as mining earnings may therefore remain in the account before it is transferred. Withdrawal timing does not change how the underlying mining reward was calculated.
Troubleshooting a Hashrate Discrepancy
- Match the measurement periods. Check the ASIC reading’s averaging period, then compare it with the corresponding pool interval. Include downtime when comparing a full 24-hour period.
- Check worker activity and share statistics. Look for interruptions or a rise in rejection rate during the same period as the discrepancy.
- Investigate persistent rejection problems. Check network connectivity, latency, device temperature, and firmware compatibility. Consult the manufacturer or ViaBTC support if the issue persists.
- Check hardware if the gap persists with normal rejection rates. Review device status, hashboard operation, and operating settings using manufacturer guidance. ViaBTC also recommends checking hardware when rejection rates are normal but the discrepancy is large. Hashrate troubleshooting guidance.
A short-term mismatch alone does not establish a hardware fault. Persistent differences over matching periods deserve investigation.
FAQ
Why does ViaBTC show a lower hashrate than my mining machine?
Different averaging periods can explain the discrepancy. ViaBTC uses 10-minute and 24-hour windows, while the ASIC reading may use a short interval or its runtime since startup. Check the actual averaging period, then investigate persistent differences, elevated rejection rates, connectivity, and hardware.
Do rejected shares count toward mining rewards?
Rejected submissions are not credited as accepted shares. Reward accounting uses accepted work under the selected payment method. Assigned share difficulty matters, so raw submission counts alone do not necessarily measure contributed work.
Is pool luck a measure of my mining rig’s performance?
No. Pool luck compares the pool’s block discoveries with statistical expectation. Use worker activity, accepted work, rejection statistics, and local device information to assess your rig.
Does PPS+ eliminate the effect of pool luck on earnings?
No. Its PPS subsidy component is independent of whether the pool finds a block during that period, but the PPLNS transaction-fee component depends on the pool’s actual block discoveries.
Are estimated earnings the same as credited earnings or withdrawals?
No. Estimates project possible earnings, credited earnings are recorded mining rewards, and withdrawals transfer funds from the balance. Each can follow different timing and rules.