A Bitcoin mining pool can credit a miner for work even on a day when the pool finds no blocks. Another pool can make the same miner wait for a successful block before any reward is allocated. The difference comes from the payment agreement: PPS, FPPS and PPLNS distribute mining uncertainty differently.
Understanding those initials helps explain what a dashboard balance represents, who absorbs an unlucky run and when earned bitcoin can reach a wallet. Operator examples below reflect documentation checked on October 14, 2026; their settings can change.
Shares measure work toward a block
Mining involves repeatedly hashing candidate block headers, looking for a result below Bitcoin's network target. Pools use an easier target to collect more frequent evidence that connected machines are working. A result meeting that easier threshold is called a share.
Most shares do not meet the harder network target. Occasionally one does, allowing the pool to submit the associated block for network validation. A valid block must also satisfy Bitcoin's other consensus rules. Accumulating shares does not gradually assemble a winning hash; each attempt is another chance. Bitcoin's explanation of pool shares
This distinction explains why a miner can submit useful work without personally finding a block. The pool's accounting system turns that evidence into a payment according to its chosen formula.
PPS and FPPS move block luck to the operator
Pay Per Share, or PPS, credits accepted work using its expected reward value rather than waiting for the pool to discover a block. In the basic model, compensation reflects the block subsidy, the newly issued bitcoin available to a successful miner. Full Pay Per Share, or FPPS, adds a transaction-fee component. These names describe reward calculation, rather than an assurance of immediate wallet withdrawals. F2Pool's payout-method definitions
The fee calculation deserves a closer look. Luxor's published FPPS method uses a 144-block lookback, filtering the low and high tails of the transaction-fee distribution before averaging. Braiins describes a calculation based on the network's blocks during a UTC day, normalized to 144 blocks. Identical FPPS labels therefore need not produce identical fee benchmarks. Luxor's FPPS specification, Braiins' reward specification
PPS+ is another label worth recognizing. F2Pool describes it as combining PPS treatment of the subsidy with PPLNS treatment of transaction fees. A PPS+ miner can consequently retain exposure to the pool's success in collecting fees. F2Pool's PPS+ explanation
Payments can still change as difficulty, the subsidy and fee conditions change. Predictability here concerns pool luck, rather than a permanently fixed bitcoin income.
PPLNS keeps more variability with miners
Pay Per Last N Shares allocates rewards when the pool finds blocks, using eligible contributions within a recent share window. Pool luck therefore affects receipts: comparable work can produce different short-term rewards. The window's definition matters. ViaBTC, for example, describes its PPLNS calculation using the last five difficulty rounds and a six-confirmation requirement. Those are its implementation details, rather than universal PPLNS settings. ViaBTC's reward-calculation rules
With PPS and FPPS, the operator instead owes payment for qualifying work even when its own block discoveries fall short of expectations. Our practical conclusion is that reduced exposure to block luck makes the operator's capacity to pay especially important. A formula cannot establish its solvency, security or willingness to honor balances.
PPLNS also leaves counterparty exposure wherever an operator holds miners' unpaid rewards. Braiins' terms provide a concrete custody warning: they say pool balances are not intended for long-term storage, describe potential loss from successful attacks and call for regular payouts. That warning illustrates a separate question from how rewards are calculated. Braiins' custody and payout terms
Follow earnings through to withdrawal
Pool fees reduce earned rewards; withdrawal fees affect getting the balance out. Minimums and payment schedules create another gap between accrual and spendable funds. Luxor currently lists a 0.001 BTC withdrawal threshold plus a 0.000075 BTC withdrawal fee, requiring a balance greater than their combined amount at the scheduled payment cycle. Luxor's payment requirements
Braiins lists a 0.0002 BTC on-chain minimum and a 0.0001 BTC payout charge below 0.005 BTC, with no on-chain payout charge at or above 0.005 BTC. Its Lightning option has different limits and no pool payout fee. These are provider-specific examples, not network-wide prices. Braiins' payout limits and fees
The trade-off follows directly: accumulating a larger balance may reduce withdrawal costs, while leaving more unpaid value with the operator. For a small miner, time to the threshold can matter as much as the advertised percentage fee.
Compare the reward formula, fee benchmark, withdrawal rules and amount left unpaid together. Then assess electricity, equipment and other operating costs separately. Smoother mining receipts can help with budgeting; they cannot establish that a mining operation will make a profit.