How to Choose a Zcash Mining Pool With a Small Amount of Hashrate
2026-11-19 03:19

Why Small Zcash Miners Need Different Selection Criteria

A miner running a single Equihash ASIC or a modest GPU rig faces a different set of trade-offs than a large-scale operation. Headline pool size and advertised fee percentages matter less than whether the pool actually supports the miner's hardware, whether the payout method matches the miner's tolerance for day-to-day variance, and whether the withdrawal threshold is reachable within a reasonable time. This article sets out a practical, evidence-based order of priorities for selecting a Zcash (ZEC) pool at small scale, using ViaBTC's published documentation as a worked example of the relevant product mechanics.

Confirm Equihash(200,9) Compatibility First

Zcash's proof-of-work uses Equihash with the specific parameter set n=200, k=9, as defined in the Zcash protocol specification [1]. A device marketed only as "Equihash-compatible" should not be assumed to support Zcash without verification, because other Equihash-based networks use different parameter sets. Before comparing fees or payout thresholds, confirm that the miner's hardware, firmware, and mining software are built for Zcash's specific implementation, and that the pool endpoint you intend to use accepts ZEC shares under that same parameter set. This is a compatibility check, not a performance metric, and it should be resolved before any other selection criterion.

Compare Payout Methods by Variance, Not Just Fee

Pool payout methods affect how evenly a small miner's earnings arrive.

ViaBTC lists two payout methods for ZEC: PPS+ and PPLNS. Under PPS+, the published fee is 4% on the block-reward component and 2% on the transaction-fee component; under PPLNS, the published fee is 2% on both components [2]. Under PPS+, the block-reward component is described as settled hourly based on current difficulty, while the transaction-fee component is distributed through the PPLNS mechanism and therefore remains variable. Under PPLNS, distribution is based on a miner's contribution across the prior five difficulty rounds, with payout occurring after a block reaches six confirmations [2]. Because PPLNS earnings depend on the pool actually finding blocks within the relevant scoring window, a small miner's daily PPLNS earnings can fluctuate even when local hashrate is stable—a function of pool luck and timing, not a flaw in the pool's accounting.

A lower fee on paper does not establish higher realized earnings for any single day or week. The practical question for a small miner is whether steadier settlement of the block-reward portion (PPS+) is worth the higher fee on that component, or whether the lower PPLNS fee is acceptable given its wider variance.

Calculate Whether the Payout Threshold Fits Your Hashrate

For a small miner, the time required to reach a pool's minimum withdrawal amount can matter more than a one- or two-percentage-point fee difference. ViaBTC's current minimum for ZEC auto-withdrawal to an on-chain address is 0.001 ZEC, with balances below that threshold retained and carried forward until it is met [3].

As a hypothetical illustration only—not a profitability forecast—suppose a miner averaging 1 KSol/s earns 0.00005 ZEC per day after pool fees. Starting from a zero balance, the miner would need 0.001 ÷ 0.00005 = 20 days to accumulate the 0.001 ZEC threshold if daily earnings stayed constant. A miner at one-tenth that hashrate (0.1 KSol/s), earning proportionally less under the same assumptions, would need 200 days. These are assumed earnings for demonstrating the calculation, not a current ViaBTC earnings estimate. Actual accumulation time will depend on changing difficulty, uptime, the selected payout method, and other factors affecting earnings.

Reaching the threshold is also different from receiving an automatic withdrawal. ViaBTC states that an on-chain auto-withdrawal address becomes invalid after 90 consecutive days without a payment [3]. A miner whose accumulation period exceeds 90 days should therefore check the auto-withdrawal settings and reconfigure the address as needed, rather than assume the original setup will remain active until the threshold is reached. Readers should also verify the current minimum, the auto-withdrawal schedule, whether the threshold is configurable, and any network fee applied to manual withdrawals before relying on a specific pool.

This is why checking the withdrawal threshold and payout rules against your own expected hashrate is a more useful first step than comparing fee percentages alone.

Evaluate Connection Quality and Rejected Shares

A small miner gains little from joining a large pool if the connection is unstable or a meaningful share of submitted work is rejected. ViaBTC's Mining Pools Information page lists multiple ZEC stratum endpoints, including region-specific options and a failover port, alongside an SSL endpoint [4]. In most ASIC and GPU mining software, multiple configured pool URLs function as priority-ordered failover addresses rather than a way to increase submitted hashrate or rewards; the firmware determines actual switching behavior. Where the mining software supports it, configuring a secondary endpoint can reduce downtime from a single connection failure.

Rejected shares should be reviewed as a distinct figure from hashrate. A rising rejection rate, rather than a drop in displayed hashrate alone, is often the more direct signal of a connection or configuration problem and is worth checking before concluding that a pool is under-crediting submitted work.

Align Measurement Windows Before Judging Pool Performance

A pool dashboard and a miner's own screen do not necessarily use the same averaging period, and comparing them without adjustment can produce a misleading impression of underperformance. ViaBTC's documentation states that its real-time pool-side hashrate estimate uses a 10-minute average, while its daily figure reflects the previous 24 hours. A local device display using a much shorter refresh interval will often diverge from either of these pool-side figures simply because of the different time windows involved, not because of lost work.

When testing a newly configured worker, it can help to allow the pool some time to begin producing a stable estimate, then compare pool-side and local readings over the same period rather than at a single instant. This is practical guidance rather than a fixed industry test duration, and actual behavior can vary by device and firmware.

A Practical Pool-Selection Checklist

For a small Zcash miner, the following order of checks reflects the priorities discussed above:

  1. Confirm the miner, firmware, and pool endpoint all support Zcash's Equihash(200,9) parameters.
  2. Decide between PPS+ and PPLNS based on how much day-to-day variance is acceptable, not fee percentage alone.
  3. Check the pool's current withdrawal threshold and auto-withdrawal schedule against your expected hashrate.
  4. Confirm the pool supports your intended payout address type.
  5. Configure a stable primary endpoint and, where supported, a failover address.
  6. Monitor hashrate and rejected shares separately, using aligned measurement windows.

Applied to ViaBTC as a worked example: a small ZEC miner would verify Equihash(200,9) support, choose between PPS+ and PPLNS based on variance tolerance and the applicable fees for each earnings component, check the current 0.001 ZEC auto-withdrawal minimum against expected daily output, select a listed primary endpoint with an available failover port, and use the pool's hashrate and rejection-rate monitoring to distinguish a genuine device issue from a simple difference in measurement windows.

FAQ

Can any Equihash-compatible miner mine Zcash?

Not automatically. Zcash uses the specific Equihash(200,9) parameter set, and a device, its firmware, and the pool endpoint must all support that exact implementation rather than Equihash in general.

Is PPLNS always more profitable than PPS+ because its listed fee is lower?

No single payout method can be said to outperform the other on every day or measurement period. PPLNS depends on the pool's block discovery and the scoring window, so realized earnings can vary even when local hashrate is constant; PPS+ settles the block-reward portion more predictably but at a higher fee on that component, with its transaction-fee component still variable.

Why does my pool-reported hashrate differ from what my miner shows?

Pool-side and device-side hashrate readings typically use different averaging windows. A pool's real-time figure may use a short rolling average (for example, 10 minutes) while a daily figure reflects a full 24-hour period; comparisons should align these windows before concluding there is a problem.

Does a lower minimum withdrawal threshold matter for a small miner?

Yes. A low-hashrate miner can take considerably longer to reach a higher threshold, which affects how often earnings actually move to an on-chain address. Checking the threshold against expected hashrate is a practical step before comparing pools on fee alone.

References

[1] Zcash Protocol Specification

[2] ViaBTC Fees

[3] ViaBTC Help Center, "What Is Auto Withdrawal? How to Set Up and Manage It?"

[4] ViaBTC Help Center, "Mining Pools Information"