Which Crypto Mining Pools Are Worth Considering?
2026-11-19 03:19

Why "best pool" is the wrong question

Mining pools are frequently compared through screenshots of daily revenue or through a single week's share of discovered blocks. Neither measurement captures what determines a miner's actual return over time. A pool becomes worth considering only when its payout method, fee schedule, supported coins, connection options, payout rules, and monitoring tools match the operator's hardware and operating model. This article sets out the criteria that matter and profiles several pools that illustrate different configurations, without declaring a single winner.

Payout method: PPS+, FPPS, and PPLNS

The payout model determines how a pool allocates mining income and how much short-term block-finding variance the miner absorbs. Under PPS (Pay Per Share), a pool pays a fixed amount per valid share submitted, independent of whether the pool actually finds a block. FPPS (Full Pay Per Share) extends this logic to include an allowance for transaction-fee revenue, calculated according to the pool's own methodology. PPLNS (Pay Per Last N Shares) instead rewards miners based on shares contributed within a defined window and depends on the pool actually finding blocks; this can produce more variance than PPS-style accounting, particularly for smaller pools or during periods of bad luck. ViaBTC's help center documentation describes its BTC PPS+ method as a hybrid: the block-subsidy portion is paid on PPS logic and credited hourly at current difficulty, while the transaction-fee portion follows PPLNS-style accounting and is distributed once the relevant block reaches six confirmations. Its separate PPLNS option applies PPLNS logic to both components. This distinction matters because PPS+ should not be described as if the entire BTC payout is fixed; only the subsidy portion behaves that way. No payout model eliminates the underlying variables that drive mining economics: network difficulty, BTC price, transaction-fee conditions, electricity cost, and hardware uptime all continue to apply regardless of which accounting method a pool uses.

Fees only mean something next to the payout method

A headline fee percentage is not comparable across pools unless the revenue component it applies to is also specified. A pool that charges a lower percentage on the block-reward component but a different rate on transaction fees is not necessarily cheaper overall, especially when transaction-fee income as a share of total block reward fluctuates with network congestion. When evaluating fees, confirm (1) which component the percentage applies to, (2) whether the figure is current on the pool's official fee page, and (3) whether the payout method itself already shifts variance in a way that changes the practical value of a lower fee.

Connection quality and share rejection

A pool's share target is the difficulty threshold a miner's submitted work must meet to be credited; it is set independently of, and is normally easier to satisfy than, the Bitcoin network's block target. Because the pool share target is numerically higher (easier to meet) than the network's block target, its corresponding difficulty is lower — this is a separate concept from network difficulty itself, and the two should never be described as interchangeable. Pools may classify and report unsuccessful share submissions differently: some include stale shares in a broader rejected-share metric, while others report stale and rejected shares separately. Before comparing rates across pools, check what each metric includes to avoid double counting. A sustained pattern of rejected or stale shares — rather than an isolated spike — is the more meaningful signal, and it should prompt a check of network latency to the chosen Stratum endpoint, firmware configuration, and whether a nearer regional server or backup URL is available. Miner-side (ASIC) hashrate readings, a pool's estimated hashrate, accepted shares, and credited revenue are related but distinct measurements, and should not be substituted for one another when diagnosing a performance issue.

Payout thresholds and settlement timing

Pool accounting and on-chain settlement are separate steps: the pool first calculates and credits mining income according to its payout method, the account then needs to meet the pool's payout threshold, and only after that does an on-chain withdrawal get processed and subsequently confirmed by the network. ViaBTC's documentation, for example, describes an auto-withdrawal mode based on daily earnings, calculated from the previous complete day's eligible income, with balances below the threshold carried forward to the next day. Because these mechanics are product-specific and can be updated, miners should confirm the current payout threshold and withdrawal timing on the pool's official page for the relevant coin before redirecting hashrate.

Coin support and merged mining

Some pools support merged mining, where a miner's existing proof-of-work contribution to a primary chain also earns rewards on a compatible auxiliary chain without additional hardware. ViaBTC's current documentation, for instance, lists Namecoin (NMC) and Fractal Bitcoin (FB) as auxiliary coins available to its BTC pool under either PPS+ or PPLNS. This illustrates a broader point: miners comparing pools should evaluate total eligible income across the primary coin and any applicable auxiliary coins under the pool's current supported-coin list, rather than comparing only the headline reward for a single coin. Auxiliary-coin reward structures are not automatically governed by the parent chain's settlement method and should be verified separately.

Pool share is context, not a profitability ranking

Public dashboards such as mempool.space publish a trailing-window share of identified blocks per pool. These figures are useful for understanding market concentration — in a one-week snapshot several of the largest pools together can account for the majority of blocks found — but a larger share of discovered blocks does not by itself demonstrate a higher return for an individual miner connected to that pool. Block-discovery share reflects aggregate network contribution and attribution accuracy over a specific window; it says nothing about a pool's fee structure, payout accounting, rejection rate, or connection quality. Because these snapshots shift materially from one week to the next, readers should treat any single figure as a dated reference point rather than a current ranking, and consult a live dashboard for up-to-date numbers.

Practical profiles to evaluate

The following are examples of pools that illustrate different configurations; they are not a ranked list, and the fees, thresholds, and features of any pool should be reconfirmed on its official documentation before use. ViaBTC offers PPS+ and PPLNS for BTC, with documented merged-mining support for NMC and FB. Under PPS+, the block-subsidy portion is credited hourly. Its profit calculator provides theoretical BTC mining revenue estimates based on PPS+ assumptions, the specified difficulty, and average transaction fees over the previous day. These estimates should not be treated as forecasts of PPLNS earnings or as net profit after operating costs. Foundry USA Pool documents an FPPS payout model, with daily earnings calculated over the prior day and distinguishing accepted shares from stale and rejected ones in its share-accounting definitions. F2Pool offers both FPPS and PPLNS for Bitcoin and publishes a pool-side "Daily Average Hashrate" metric based on effective hashrate received over a 24-hour window — a pool-side estimate that should not be read as an ASIC's instantaneous local reading. Braiins Pool documents an FPPS model and has a close technical association with Stratum protocol development, which may be a relevant consideration for miners who weigh a pool's involvement in open mining-protocol work. AntPool offers PPS, PPLNS, and FPPS options across a broad range of supported coins; several of its public help pages have not been recently updated, so its current fee schedule and payout settings should be verified directly on its live interface rather than through older documentation.

Conclusion

The mining pools worth considering are not necessarily the ones with the largest recent share of discovered blocks. A better choice depends on the miner's coin and algorithm, payout-method preference, the fee applicable to each income component, connection quality, withdrawal rules, monitoring needs, and, where relevant, merged-mining support. Before redirecting hashrate, miners should confirm a pool's current terms directly on its official documentation and compare results over a meaningful operating period using consistent hardware and network conditions, rather than relying on a single day's figures.

FAQ

Does a lower pool fee always mean higher net earnings?

Not necessarily. The fee must be compared against the specific revenue component it applies to, alongside the payout method, transaction-fee treatment, rejection rate, and uptime; a lower headline fee does not by itself guarantee a higher realized result over a given period.

Is PPS+ the same as a fixed PPS payout?

No. Under ViaBTC's documented PPS+ method, only the block-subsidy component follows PPS logic; the transaction-fee component follows PPLNS-style accounting and is distributed after the relevant block reaches the stated confirmation threshold, so total earnings still vary with transaction-fee conditions.

Does a pool's share of recent blocks indicate which pool pays more?

No. Block-discovery share over a trailing window reflects aggregate network contribution and attribution during that period. It does not measure fees, payout accounting, rejection rates, or connection quality, all of which affect an individual miner's realized return.

How should a miner interpret a rejected-share spike?

First check how the pool defines its rejected-share metric, including whether stale shares are included or reported separately. A brief spike may be incidental, but a sustained elevated rate across sessions warrants checking network latency to the connected endpoint, firmware settings, and whether a closer regional server is available.

References