Why mining farms evaluate more than pool fees

For an individual miner, pool selection is often a simple decision based on a headline fee. For a mining farm running dozens or thousands of ASICs, the pool is part of the operating stack. It determines how contributed work is recorded, how block-subsidy and transaction-fee revenue are settled, how connection failures are handled across many machines at once, and how operators monitor and organize accounts across sites or tenants. A fee comparison alone does not capture these operational dependencies.

This article focuses on Bitcoin mining farms and uses ViaBTC’s official rules to illustrate four areas that matter specifically at farm scale: settlement mechanics, connection reliability, monitoring, and account controls. The evaluation principles apply more broadly, but the listed fees, settlement windows, and product features are specific to ViaBTC. It does not replace decisions about ASIC maintenance, power procurement, cooling, or financial planning, which remain separate from pool selection.

How a mining pool records a farm's work

A Bitcoin block is valid only if its hash meets the network's current difficulty target. Because that target is extremely hard to meet, a solo miner may go long periods without finding a block even while contributing real computational work. A mining pool addresses this by setting a separate, easier-to-meet share target. Each time a miner's hash meets the share target, it submits a share to the pool. A share demonstrates that work was performed. Most shares meet only the pool’s easier target; a small fraction also meet the network target and can be used to submit a candidate block (Bitcoin Developer Guide).

The pool uses submitted shares to estimate each worker’s contributed hashrate. How that work translates into credited income depends on the payment method: PPS pays for valid shares independently of whether the pool finds a block, while PPLNS distributes rewards from blocks the pool actually finds (ViaBTC Help Center). This distinction matters operationally: local ASIC hashrate, pool-estimated hashrate, valid shares, rejected shares, and credited mining income are related but separate measurements, and a farm's monitoring practices should treat them as such.

Compare payout methods before routing hashrate

This section compares the two payment methods available for BTC mining on ViaBTC: PPS+ (Pay Per Share Plus) and PPLNS (Pay Per Last N Shares).

Under ViaBTC’s published BTC PPS+ rules, the block-subsidy component is calculated as a theoretical PPS reward based on valid shares, the current network difficulty, and the block subsidy, with a listed 4% fee. It is settled hourly regardless of whether the pool finds a block in that period. The transaction-fee portion is instead distributed under PPLNS logic — based on a miner's share of work over the prior five difficulty rounds — and is settled after the relevant block reaches six confirmations, with a listed 2% fee. Under ViaBTC's BTC PPLNS method, both the block subsidy and transaction fees are allocated under PPLNS rules, with a listed 2% fee applied to the combined amount (ViaBTC Help Center).

The practical difference is exposure to pool luck. PPS+ shifts the short-term variance of the block-subsidy component to the pool, since payment for that portion does not depend on whether the pool actually finds a block in a given period. The transaction-fee component under PPS+, and both components under PPLNS, remain tied to the pool's actual block-finding results over the relevant window. Neither statement — "PPS+ guarantees fixed income" or "PPLNS always pays more" — is accurate; a lower listed fee does not by itself determine realized revenue in any specific period. These figures reflect ViaBTC's documentation as published and should be verified against current official terms before a farm finalizes its settlement assumptions, since fee schedules and rules can change.

Settlement into a pool account is separate from withdrawal to a wallet. ViaBTC’s Auto Withdrawal is free and is processed once daily between 10:00 and 18:00 (UTC+8), subject to the selected payout mode and applicable conditions. For an external BTC address, the documented minimum payment is 0.001 BTC; operators should check their configured threshold and receiving address before relying on that schedule. Auto Withdrawal to the miner’s own ViaBTC main or sub-account has no minimum payment requirement as long as the amount is greater than zero. Withdrawal processing is also separate from on-chain confirmation, so an hourly PPS credit does not mean hourly receipt in an external wallet (ViaBTC Help Center).

Build a resilient pool connection

At farm scale, a single misconfigured connection can affect many machines simultaneously, so connection setup deserves the same attention as payout method. ViaBTC's BTC mining documentation lists official Stratum endpoints in this form:

stratum+tcp://btc.viabtc.io:3333
stratum+tcp://btc.viabtc.io:443

The documentation recommends configuring more than one port so a miner can move to an alternate connection if the first becomes unavailable, rather than idling (ViaBTC Help Center). Workers are identified using a userID.workerID format, which farms can use to label machines by row, container, or site for easier troubleshooting.

For large deployments where many ASICs share constrained or unstable upstream bandwidth, a mining proxy or miner-agent architecture may be worth evaluating. ViaBTC describes its Miner Agent Server as a function that consolidates miner connections, distributes pool jobs locally, and forwards results upstream, which it presents as a way to reduce bandwidth use and help miners receive new work promptly during job changes (ViaBTC Help Center). Whether this is relevant depends on the farm's network topology; it does not substitute for correct DNS and routing configuration, current ASIC firmware, or physical network maintenance, and any agent software should be obtained only from official pool channels.

Stratum V2’s Job Declaration Protocol is designed to let a miner or farm declare its own block template to a supporting pool, while the Mining Protocol handles job distribution and share submission. These protocol capabilities do not establish that a particular pool has deployed them; firmware compatibility and pool-side support should be confirmed before a farm plans a migration (Stratum V2 specification).

Monitor the right measurements

Farm operators frequently compare a miner's local hashrate display against the pool's dashboard and interpret any gap as a fault. This comparison is only valid if the measurement windows match. ViaBTC's documentation states that its real-time pool hashrate reflects the prior 10 minutes of submitted shares, while its daily statistic reflects the prior 24 hours — both are pool-side estimates derived from share submission rates, not instantaneous readings of ASIC output (ViaBTC Help Center). A miner that just restarted, or that experienced a brief interruption, will show a lower rolling average until the window fills with normal activity again.

When diagnosing a discrepancy, align the time window first, then check for rejected shares and their stated reason, before concluding that hardware is underperforming.

Organize a multi-site or multi-tenant farm account

Farms operating multiple sites, or hosting machines on behalf of different customers, typically need more than a single login. Sub-accounts allow hashrate and mining income to be tracked separately — for example, by site, equipment group, or payout address — which simplifies reconciliation (ViaBTC Help Center). ViaBTC’s Worker Offline and Worker Rejection Rate alerts can supplement, though not replace, on-site network and power monitoring (ViaBTC Help Center). API access, where enabled, allows automated retrieval of worker and earnings data for integration with a farm’s own monitoring systems (ViaBTC Pool API documentation). API keys should be treated as sensitive credentials; ViaBTC supports an IP allowlist for restricting API access (ViaBTC Help Center).

These are account-administration and connection-monitoring features, not mining-protocol functions, and they should be configured based on the operation's actual structure rather than adopted as a fixed checklist. Regardless of account structure, operators should use only official pool URLs and officially distributed proxy or agent software, since credential and configuration security depends on the integrity of that connection.

Questions to ask before selecting a mining pool

• Which payment methods (e.g., PPS+, PPLNS) are supported for the coin being mined, and what exact fee applies to each reward component?
• How is settlement timed, and what confirmation requirements apply before a reward component is credited?
• Separately, what withdrawal thresholds, processing times, fees, and receiving-address settings apply before funds reach the farm’s wallet?
• What are the official Stratum endpoints and backup ports, and does the pool publish guidance on failover configuration?
• What monitoring tools, alerts, sub-account functions, and API controls are available for multi-site or multi-tenant operation?
• Where is the pool's current, official documentation for these rules, since fee schedules and settlement logic can change over time?

Conclusion

Pool selection for a mining farm is a settlement, connectivity, and account-administration decision as much as a fee comparison. PPS+ and PPLNS allocate pool-luck exposure differently across the block-subsidy and transaction-fee components of mining income; Stratum endpoint configuration and, where relevant, proxy or agent architecture affect how reliably work reaches the pool; and monitoring requires keeping local, pool-side, and payout data distinct rather than treating them as interchangeable. Matching these mechanics to a farm's actual network design, settlement preferences, and operational structure is a more reliable basis for choosing a pool than the headline fee alone.

FAQ

What is the difference between PPS+ and PPLNS for a mining farm?

Under ViaBTC’s BTC PPS+ method, the block-subsidy portion is calculated from valid shares using PPS logic and settled hourly based on current difficulty, regardless of whether the pool finds a block in that period. The transaction-fee portion is distributed under PPLNS logic. Under PPLNS, both components depend on the pool's actual block-finding results over a defined window. Listed fees differ between the two methods and should be checked against current official documentation.

Why does my pool dashboard show a different hashrate than my ASIC's local display?

The two figures are measured differently. A local ASIC display may show an instantaneous, short-window, or running average, depending on the device, firmware, and selected metric. A pool’s real-time and daily hashrate figures are rolling estimates based on submitted shares over a stated window, such as ViaBTC’s 10-minute and 24-hour windows. Align the measurement windows before comparing them. Recent restarts or brief interruptions will temporarily lower the pool-side rolling average even if the device is otherwise performing normally.

Should a mining farm use a mining proxy or miner agent?

This depends on the farm's network topology. A proxy or agent that consolidates connections and relays jobs may be worth evaluating where many ASICs share limited or unstable upstream bandwidth, but it does not replace correct network configuration, current firmware, or physical maintenance, and only officially distributed software should be used.

Does a lower pool fee always mean higher realized revenue?

No. The listed fee is only one factor; realized revenue also depends on the payment method's exposure to pool luck, the pool's actual block-finding performance over the relevant period, and the farm's own connection stability and share-acceptance rate. A lower fee under PPLNS does not guarantee higher income than a higher-fee PPS+ arrangement in any specific period.

How many Stratum endpoints should a farm configure?

Pools generally publish more than one endpoint or port so that miners can switch to an alternate connection if the primary one becomes unavailable. The exact number and configuration should follow the pool's current official setup documentation rather than a fixed rule.

References

• ViaBTC Help Center, "How are profits calculated?"
• ViaBTC Help Center, "BTC Mining."
• ViaBTC Help Center, "Why is the Hashrate Shown in the Mining Pool Lower than that of the Mining Machine?"
• ViaBTC Help Center, "An Introduction to Miner Agent Server."
• ViaBTC Help Center, "What are Sub-Accounts for? How Can I Add One?"
• Bitcoin Developer Guide, "Mining."
• ViaBTC Help Center, "How to Choose the Optimal Payment Method (PPS+, PPLNS)?"
• ViaBTC Help Center, "How to Set Up Auto-Withdrawal？"
• ViaBTC Help Center, "Announcement on Hashrate Alert Feature Upgrade."
• ViaBTC Help Center, "What is API and How to Set Up?"
• ViaBTC Pool API documentation.
• Stratum V2 specification, "3. Protocol Overview."