Pool Fees: How Much Does a Mining Pool Cost?

Pool fees pay the coordinator: Stratum servers, block construction, accounting, payouts, and sometimes the variance insurance an FPPS scheme implies. They are deducted from what your shares would otherwise have earned. They cover neither electricity, nor colocation rent, nor ASIC depreciation: mixing those line items ruins any profitability calculation.

Schedules differ by pool, by scheme, and sometimes by volume. What follows therefore describes where to look and how to measure, rather than quoting a typical percentage that would be wrong the day it was published.

What the fee covers

The advertised percentage is meant to cover pool operations. Under the contract it also funds the risk the pool takes by paying you before it has found a block, which is the whole logic of FPPS and PPS.

It generally does not cover:

• stale and rejected shares caused by your latency, a wrong URL, or a firmware setting;
• orphaned blocks beyond what the scheme explicitly promises;
• Bitcoin network fees when the pool pays you on-chain, sometimes deducted, sometimes absorbed above a threshold;
• an availability guarantee. Many pools publish no numeric SLA, and the absence of a written commitment means exactly that.

Where fees hide

The headline percentage is one lever among six.

The scheme's perimeter. FPPS smooths network transaction fees, while strict PPS may omit them entirely. Comparing a "0 %" on one scheme against a "2 %" on another, without aligning the perimeter of subsidy alone against subsidy plus transaction fees, means nothing: the perimeter gap dwarfs the percentage gap.

The payout threshold and frequency. A high minimum, or infrequent payouts, leaves a balance sitting at the pool. That is not a fee, it is counterparty exposure, and it measures in days of production tied up.

Rounding. On small workers, an aggressive rounding policy can weigh more than the advertised percentage. It only shows on your own statements.

Withdrawal fees. Separate from the pool fee, sometimes documented on another page, sometimes not documented at all.

Volume terms. Some institutional pools negotiate off their public page. Until that is your signed contract, it is not your rate.

Server quality. A pool that sets share difficulty poorly, or whose jobs expire too quickly, raises your stale share rate. No fee line appears, and yield still falls.

Computing your effective rate

This is the only measurement that counts, and it comes from your statements.

Over a period long enough for share variance to wash out, a month at minimum, record the satoshis received and the accepted shares the pool counted. Compute the revenue per share obtained, then compare it against the theoretical rate the pool publishes for your scheme.

An example makes the operation concrete. Take an FPPS pool advertising a 2 % fee, and a theoretical gross of 0.00320000 BTC over the month for your accepted shares. The advertised rate implies 0.00313600 BTC net. If your statement shows 0.00298000 BTC, your effective rate is 6.9 %, not 2 %. That 4.9-point gap needs explaining line by line: unpaid stale shares, rounding, withdrawal fees, or an accounting window that shifted at month end.

The gap almost always traces back to stale and rejected shares, which appear as no fee at all and cost exactly like one. That is why the effective rate is driven as much by your network as by your choice of pool.

Comparing two pools without error

1. Start from the primary source, the pool's fees and payout page, dated where possible. Third-party comparisons age and err.
2. Check the unit. A percentage of what: FPPS gross, the PPLNS block, excluding transaction fees?
3. Look at subaccounts. Some interfaces apply one rate to every worker, others let you choose the product worker by worker.
4. Keep a dated copy of the schedule in force, as a screenshot or PDF. Pools change their rates, and a retrospective audit without proof of the applicable rate goes nowhere.
5. Then measure your effective rate across a full month, before concluding anything from an advertised gap of a few tenths of a point.

Fees, variance, and treasury

A higher fee is not automatically worse. Under FPPS, part of the rate pays to smooth your revenue. Under PPLNS, a lower rate leaves you carrying the variance. Picking only the smallest percentage compares an insurance premium to a deductible without looking at what is covered.

For a site that must settle a hosting invoice every month, predictability is often worth more than a fee gap of a few tenths of a point. Conversely, an advertised "0 %" erases neither counterparty risk nor a payout threshold that locks your balance for weeks.

If your effective rate stays unexplained after this calculation, ask the pool for the share-level detail. A serious pool provides it; a refusal is itself an answer.