← All guides

Mining pool fees and minimum payouts: reading the fine print before you point a miner

Pools · 7 min read

General information only, not financial advice. Pool fees, payout schemes and minimums change, and the comparison tables cited here already disagree with each other; verify every figure on the pool’s own terms page before pointing a miner at it. Nothing here predicts mining earnings.

3 percent. That is the whole spread between a 1 percent pool fee and a 4 percent pool fee, and at 100 TH/s it works out to about 9 cents a day. The fee percentage printed in large type is rarely where a small miner loses the most. The quieter numbers do more damage: a withdrawal fee taken out of every payout, a firmware fee hiding behind a “0 percent pool fee” headline, and a minimum payout threshold that can lock a balance inside a pool for three and a half months. Read the fine print as one total-cost problem, in three layers.

Layer one, two and three: the fees stack

The first layer is the pool fee itself, charged against earnings under the pool’s payout scheme. The scheme matters alongside the percentage: under PPS the pool keeps the transaction fees, under FPPS those fees pass through to the miner, and under PPLNS income varies with the pool’s luck. Two pools quoting the same percentage under different schemes are not quoting the same deal.

The second layer is the withdrawal fee, charged when the balance leaves the pool. It appears in only one of the comparison tables checked for this guide, which is exactly the problem: a cost that most tables omit is easy to miss entirely. The third layer is the firmware fee. One pool in the tables advertises a 0 percent pool fee when its own firmware is used, paired with a 2.8 percent firmware fee. The headline says free. The stack says 2.8 percent.

The pools compared, conflicts left visible

The table below records what two comparison sources listed when checked on 25 October 2026. Where they disagree, both figures stand. Averaging a conflict away would invent a third number that no source published.

PoolFee and scheme, as listedMinimum payout, as listedThe catch to verify
Braiins Pool2.5% FPPS0.0002 BTC on-chain; 1 sat via LightningOne source gives a 0–2.5% fee range instead, check which figure the terms page states
F2Pool2.5% PPS+ in one table; 2–4% in another0.001 BTC in one table; 0.005 BTC in anotherThe widest conflict in the set: fee and minimum both disputed
ViaBTC4% PPS+; 2% PPLNS0.001 BTCScheme choice doubles the fee; auto-withdrawal from 0.001 BTC listed as free
Luxor0–2.5% FPPS; 0% pool fee with its firmware, plus a 2.8% firmware fee0.001 BTC, plus a 0.000075 BTC withdrawal feeTwo extra layers beyond the headline fee
Ocean0% TIDES; 2% Core Lightning0.00001 BTC via Lightning; 0.001 BTC on-chainThe payout route, not just the pool, sets the minimum

Two patterns are worth naming. First, the payout route changes the minimum by orders of magnitude: Braiins lists 0.0002 BTC on-chain against 1 sat over Lightning, and Ocean lists 0.00001 BTC over Lightning against 0.001 BTC on-chain, a hundredfold difference inside the same pool. Second, a fee range is not a fee. A listing of 2–4 percent describes the source’s uncertainty, not a price, and the only document that settles it is the pool’s own terms page.

Convert the minimum into days

A threshold in bitcoin means little until it is converted into time. One worked example, from a pool guide’s figures: at 100 TH/s, a 0.005 BTC threshold takes about 107 days to fill, and a 0.001 BTC threshold about 21 days. Scaling those two points proportionally, an approximation, since earnings vary, puts 0.0002 BTC at roughly four to five days, and 0.00001 BTC inside a day.

Minimum payoutApproximate days at 100 TH/sWhat the wait means
0.005 BTC~107 daysNearly a quarter of a year of earnings held by the pool
0.001 BTC~21 daysThree weeks between payouts
0.0002 BTC~4–5 days (scaled)Balances move before terms are likely to change
0.00001 BTC (Lightning)Under a day (scaled)Threshold stops being a lock-up factor

Now price the withdrawal fee against the threshold it is charged on. A 0.000075 BTC withdrawal fee taken from a 0.001 BTC payout is 7.5 percent of that payout, larger than any pool fee in the table above. The same fixed fee spread over a larger balance costs proportionally less, which creates a genuine tension: a low threshold frees the balance sooner, but frequent small withdrawals hand a larger share to fixed fees. There is no universal answer; there is only the arithmetic for a specific hashrate, done before connecting.

The balance below threshold is not yours yet

Every day spent climbing toward a threshold is a day the earnings sit on the pool’s side of the ledger. If the pool closes, changes its terms, or raises its minimum mid-climb, a balance below the old threshold can be stranded, earned, visible on a dashboard, and not withdrawable.

That risk scales with the days-to-threshold figure, not with the fee percentage. A 107-day climb carries roughly five times the exposure window of a 21-day climb, at the same hashrate. Small miners, whose climbs are longest, have the most reason to weigh the threshold heavily and the headline fee lightly.

The pre-pointing checklist

  1. Open the pool’s own terms or fees page, not a comparison table, and record the pool fee and the payout scheme it applies to.
  2. Find the minimum payout for the exact route that will be used: on-chain and Lightning minimums can differ by a hundredfold.
  3. Find the withdrawal fee, and whether automatic withdrawal changes it. If the page does not state one, treat that as an unanswered question, not as zero.
  4. If custom or pool-linked firmware is in use, record its fee separately and add it to the pool fee before comparing anything.
  5. Convert the minimum into days at the miner’s actual hashrate, using the 100 TH/s reference points above scaled proportionally.
  6. Divide the withdrawal fee by the expected payout size to get its real percentage cost.
  7. Date every figure. Terms change; an undated screenshot settles nothing later.

What success looks like: a one-page record, dated, where the total cost reads as a stack, pool fee plus firmware fee plus withdrawal fee as a percentage of a typical payout, and the threshold reads as a number of days, all taken from the pool’s own page rather than a comparison table.

Choosing: match the stack to the hashrate

At small hashrates, threshold first: a low minimum or a Lightning route shortens the lock-up from months to days, and that protection is worth more than a point of headline fee worth about 3 cents a day per point at 100 TH/s. At larger hashrates, where thresholds fill quickly either way, the fee stack dominates, scheme, firmware fee and withdrawal fee in that order. In both cases the decision framework is the same three questions: What is the total percentage, all layers in? How many days until the balance can leave? What happens to the balance if the pool changes the rules mid-climb? A pool that answers all three clearly on its own pages has earned the hashrate. One that leaves any of them to a comparison table has not.

, Dex Carter, Tech Writer