Why the headline fee is an incomplete comparison
Mining pools commonly advertise a single fee percentage next to their payout method, and it is tempting to treat that number as the entire basis for choosing where to point a fleet of ASICs. In practice, the advertised fee only becomes meaningful once a miner knows what revenue the fee applies to, how that revenue is calculated, when it is settled, and what the miner's own equipment actually produced over a comparable period. Two pools can list the same percentage while applying it to different reward components, using different settlement windows, and delivering materially different operating results. A rigorous comparison therefore starts with the payout method and then works through connection quality, share handling, settlement and withdrawal terms, and transparency, before any conclusion is drawn from the fee line alone.
Start with the payout method, not the percentage
The Bitcoin block reward paid to whichever pool finds a block consists of two components: the block subsidy (currently 3.125 BTC following the April 2024 halving) and the transaction fees included in that block. A pool's fee structure can apply differently to each component, so the payout method has to be understood before the percentage can be compared.
Under a PPS-style method, the pool pays miners based on submitted valid shares according to its own published formula, absorbing more of the short-term variance in block-finding. Under PPLNS, miner rewards are tied more directly to blocks the pool actually finds within a defined recent-share window, so results are more exposed to the pool's own luck over any short observation period.
ViaBTC's PPS+ method illustrates why the two percentages in a split fee schedule cannot simply be added together. The block-subsidy portion is settled under PPS logic at a published rate of 4%, while the transaction-fee portion is distributed under PPLNS logic at a published rate of 2%. These two rates apply to different reward bases, not to the same total, so describing the method as a flat "6% fee" would misstate how it works. Under ViaBTC's PPLNS method, by contrast, both the subsidy and transaction-fee components are distributed together under PPLNS at a single published rate of 2% (ViaBTC Fees).
To see why the blended cost of PPS+ depends on the relative size of the two components, consider a simplified, hypothetical example (not a real settlement record): if the subsidy allocation (B) for a given period is 10 units and the transaction-fee allocation (F) is 1 unit, the blended fee is (10 × 4% + 1 × 2%) ÷ (10 + 1) ≈ 3.8% of the combined total. If transaction fees were instead 4 units against the same 10-unit subsidy, the blended fee becomes (10 × 4% + 4 × 2%) ÷ 14 ≈ 3.4%. The published rates do not change, but the effective share of gross earnings they represent shifts with network conditions that are outside the pool's control. This is not a standardized industry metric; it is simply an illustration of why a single percentage cannot summarize a split-fee method on its own.
ViaBTC's help documentation distinguishes PPS+ and PPLNS in plain terms and notes that pool luck, transaction-fee income, and network difficulty all affect actual results independent of the fee schedule itself (How to Choose the Optimal Payment Method). Neither method guarantees a higher payout; PPS+ reduces exposure to short-term block-finding variance on the subsidy portion, while PPLNS ties results more closely to the pool's actual block production over its stated window.
Separate miner-side readings from pool-side records
A second comparison layer that is easy to overlook is the difference between what a miner's own equipment reports and what the pool records and credits. These are related but not interchangeable measurements, and conflating them produces misleading comparisons between pools.
- ASIC-reported hashrate is the device's own local estimate of hashing activity, read from firmware or management software.
- Pool-estimated hashrate is the pool's estimate derived from the shares it has received over its own stated averaging window; different pools may use different windows, so an instantaneous reading should not be compared with a 24-hour rolling average.
- Accepted shares confirm that a submission was validated under the pool's assigned share target; this is a pool-accounting event, not proof of income or an on-chain event. The Bitcoin developer documentation describes shares as evidence of contributed work, a small fraction of which also happen to satisfy the Bitcoin network target and become block candidates (Bitcoin Developer Guide: Mining).
- Rejected shares are an umbrella category; reasons such as stale, invalid, or duplicate submissions are subcategories reported underneath it, not separate peer metrics. If 100 shares are accepted and 5 are rejected out of 105 total submissions, the rejection rate under a simple count-based definition is 5 ÷ 105 ≈ 4.8%, not 5%; pools that weight rejections by submitted work or report stale shares separately will produce a different figure from the same raw counts, so the exact definition matters before any cross-pool comparison is made.
- Credited earnings are the amount the pool records to the account under its payout method, which is distinct from a wallet balance until withdrawal and on-chain confirmation have occurred.
When comparing two pools, these layers should be recorded separately for a matched period: local hashrate and its averaging window, pool-reported hashrate and its averaging window, accepted and rejected shares with reasons where available, and the resulting credited earnings. Raw share counts should not be compared directly across pools unless share difficulty is accounted for; use difficulty-weighted work or pool-estimated hashrate with clearly defined, matched averaging windows instead. Combining figures from different windows, or treating an accepted share as realized income, will distort the comparison regardless of which pool is actually performing better.
Connection quality and rejected shares
A lower advertised fee can be offset by avoidable lost work if the connection between the miner and the pool is unstable or poorly routed. Where available, it is worth reviewing a pool's stratum endpoints and regional routing options relative to the mining site, and examining ASIC logs and pool-side worker records for reconnects and rejected-share trends over a period rather than relying on a single dashboard snapshot. If the rejection rate rises, pool documentation on troubleshooting typically recommends checking, in order, the reported rejection reasons, coin and algorithm settings, address and port configuration, network latency or disconnections, and hardware conditions such as temperature and frequency, since any of these can produce the same symptom. There is no universal rejection-rate threshold that applies across all coins and algorithms; a figure cited in older documentation for one specific setup should not be generalized into a guaranteed benchmark.
A backup or failover pool configuration can reduce the impact of a connection outage, but switching between pools, where used, should be evaluated carefully, since frequent switching complicates PPLNS comparisons by interrupting the contribution window on which that method depends.
Settlement and withdrawal terms
Fee comparisons are also incomplete without accounting for when earnings actually become available. A meaningful review separates four distinct points in time: when earnings are calculated, when they are credited to the pool account, when they become eligible for withdrawal under the pool's minimum-payout rules, and when the corresponding on-chain transaction is confirmed in the destination wallet. On-chain confirmation is a separate stage from the pool's internal settlement and processing. The wait after broadcast depends on network congestion, block arrival times, and the transaction fee rate used for the withdrawal, so it should not be treated as a direct measure of the pool's internal settlement speed.
ViaBTC's current documentation describes Auto Withdrawal as processed once daily, within a stated window of 10:00–18:00 (UTC+8), once the applicable minimum-payout condition is met; amounts below that threshold remain in the account balance until the condition is satisfied (What Is Auto Withdrawal?). This distinction between pool-side processing and blockchain confirmation applies generally: a miner evaluating two pools should compare stated processing schedules and minimum thresholds on the same basis, rather than treating a faster-looking dashboard figure as equivalent to funds already received externally.
What pool size does and does not tell you
Pool size, usually expressed as a share of recently found blocks over a stated trailing period, is a legitimate input to a comparison but a limited one. A larger pool may find blocks more frequently under PPLNS, which can shorten the typical interval between block-dependent settlement events and provide a broader recent sample for reviewing block-finding patterns. Pool size does not, by itself, establish better net earnings, lower rejected-share rates, better connection quality for a specific location, more favorable withdrawal terms, or stronger account-security controls. Any ranking of pools by block share should be read as a snapshot over the stated window, not as a permanent or quality-adjusted ranking, and it should not be combined with hashrate or difficulty figures drawn from a different time window.
A practical comparison process
For an operator deciding between pools, it is reasonable to run a short, controlled comparison rather than relying on advertised fees alone:
- Read each pool's payout documentation first: the payment method, the fee basis, how the block subsidy and transaction fees are treated, and the applicable settlement window.
- Where feasible, use comparable hardware, site conditions, and firmware settings so that differences in results are not attributable to the equipment itself.
- Align the reporting period across both pools — do not compare a 24-hour hashrate estimate from one pool with a multi-day payout total from another.
- Record accepted shares, rejected shares with reasons where available, credited earnings, and withdrawal timing separately for each pool over the same period.
- Treat a difference in credited BTC over a short PPLNS sample with caution, since it may reflect pool luck during that window rather than a durable difference in service.
This process is a practical method for comparing documented terms and measured results; it is not a certification standard, and operators with different risk tolerances, cash-flow needs, or coin preferences may reasonably weigh these factors differently.
Conclusion
The lowest advertised pool fee is not necessarily the lowest cost of mining. A meaningful comparison begins with the payout method and the specific reward components to which the fee applies, and it extends through share handling, connection quality, settlement and withdrawal terms, and the operator's own measured results over a matched period. The objective is not to identify a single universally superior pool, but to understand which documented terms and which measured outcomes actually apply to a given mining operation before fees are compared at all.
FAQ
Does a lower pool fee always mean higher net earnings?
Not necessarily. The fee applies to a specific reward base defined by the payout method, and actual earnings also depend on difficulty, submitted valid work, transaction-fee income, and pool luck under PPLNS. A pool with a slightly higher published fee but better connection quality or more favorable settlement terms can still produce a better outcome for a given operation.
Can a PPS+ fee and a PPLNS fee be added together to compare methods?
No. In a split schedule such as ViaBTC's PPS+, the subsidy component and the transaction-fee component carry separate published rates applied to different reward bases; they should not be summed into a single percentage, and the blended effect depends on the relative size of each component during the period measured.
Is an accepted share the same as confirmed income?
No. An accepted share confirms that the pool validated the submission under its assigned share target. Whether and when that contributes to credited earnings, and when those earnings can be withdrawn on-chain, are separate steps governed by the pool's calculation and settlement rules.
Does joining a larger pool guarantee better results?
No. A larger pool's share of recently found blocks is a measure of observed block production over a stated period, not a direct measure of net earnings, connection quality, rejected-share rates, or account security. These factors should be evaluated independently.


