Why Switching Mining Pools Is One of the Highest-ROI Moves You Can Make

A one-percentage-point difference in effective pool fees on a 10 PH/s operation at current hashprice levels translates to roughly $1,200 per year in lost revenue. Scale that to 100 PH/s and you are leaving $12,000 on the table — before accounting for payout timing delays, stale share rates, and transaction fee calculation differences that vary widely between pools.

Yet most miners pick a pool when they first power on their ASICs and never revisit the decision. Pool economics shift. Fee structures change. New entrants like OCEAN and Demand offer transparency features that did not exist two years ago. This guide provides the analytical framework and step-by-step migration checklist to evaluate, compare, and switch pools with zero hashrate downtime.

The True Cost of a Mining Pool: Beyond the Listed Fee

Every pool advertises a fee percentage. That number tells you roughly half the story. The real cost of mining through any pool is determined by five factors working together.

1. Stated Pool Fee

The headline number. Ranges from 0% (Foundry USA, OCEAN) to 4% (some smaller PPLNS pools). But a 0% fee pool is not necessarily cheaper than a 2% fee pool once you account for the other four factors below.

2. Transaction Fee Handling

This is where the real money hides. In FPPS pools, the transaction fee component of block rewards is estimated and paid to miners as a fixed rate. How the pool calculates that estimate varies significantly:

• Generous estimation: Some pools use a rolling 24-hour average of actual transaction fees, paying miners close to real mempool conditions.
• Conservative estimation: Others use a 7-day trailing average or apply a discount factor, systematically underpaying the transaction fee component by 5-15%.
• Embedded margin: Pools advertising 0% fees (like Foundry USA) typically embed their margin in the FPPS rate calculation itself. The pool keeps the difference between actual transaction fees collected and the rate paid to miners. This is not disclosed as a fee but functions identically.

At current network conditions with BTC near $80,000 and transaction fees averaging 10-15% of total block rewards, the transaction fee handling methodology alone can represent a 0.5-1.5% effective cost difference between pools.

3. Stale and Rejected Share Rates

Shares submitted after a block is found (stale shares) earn nothing. The stale rate depends on your network latency to the pool’s servers and the pool’s block propagation efficiency. A pool with servers in Virginia offers lower latency for East Coast U.S. miners than one with its nearest node in Amsterdam.

Typical stale rates range from 0.1% to 1.5%. On a 10 PH/s operation, the difference between 0.2% and 1.0% stale rates costs approximately $960 per year at current hashprice.

4. Payout Threshold and Timing

How quickly you receive your BTC matters for cash flow and opportunity cost:

• Foundry USA: Daily settlement at 01:00 UTC for prior day’s work. No minimum threshold for established accounts.
• AntPool: Daily payouts, 0.001 BTC minimum.
• F2Pool: Daily payouts, 0.005 BTC minimum.
• ViaBTC: Daily payouts, configurable minimum.
• OCEAN: Payouts per block found (TIDES model), variable timing.
• Luxor: Daily payouts, Net 1 settlement.

Higher minimum thresholds effectively create an interest-free loan from miners to the pool. For smaller operations, a 0.005 BTC minimum at $80,000/BTC means $400 in mining revenue held by the pool until the threshold is met.

5. Luck and Variance (PPLNS Pools Only)

PPLNS pools distribute actual block rewards only when blocks are found. Pool luck — the ratio of expected blocks to actual blocks found — introduces variance. A pool running at 95% luck over a month pays 5% less than expected. Over a year, luck normalizes toward 100%, but short-term variance can severely impact cash flow for smaller miners.

FPPS pools absorb this variance entirely, guaranteeing consistent payouts regardless of block-finding luck. The fee premium (typically 1-2.5% higher than PPLNS) is the price of that insurance.

Pool Transparency: What to Demand Before Committing Hashrate

Not all pools provide the same level of operational transparency. Before pointing your ASIC fleet at any pool, verify these metrics are accessible:

Must-Have Transparency Features

• Real-time hashrate dashboard: Your submitted hashrate, accepted/rejected/stale share counts, updated at least every 5 minutes.
• Block-by-block payout records: Every block the pool found, your proportional share, and the exact payout calculation for each.
• Fee calculation methodology: A published, detailed explanation of how FPPS rates or PPLNS windows are calculated.
• Historical luck data: The pool’s actual-vs-expected block discovery rate over 30, 90, and 365 days.
• Server status page: Real-time latency and uptime metrics for each stratum server endpoint.

Red Flags That Signal Hidden Costs

• No published fee methodology: If the pool cannot explain exactly how your payout is calculated, you cannot verify you are being paid correctly.
• Aggregated payout reports: Pools that show only daily totals without block-level detail make it impossible to audit individual payouts.
• Missing stale share reporting: If you cannot see your stale rate, you cannot optimize your stratum connection.
• Vague “0% fee” claims: Zero-fee pools must generate revenue somehow. Understand where the margin comes from before assuming you are paying nothing.

Head-to-Head: Major Pool Economics in September 2026

The following comparison reflects published rates and community-reported effective yields as of September 2026. Network hashrate sits near 900-1,000 EH/s, difficulty at approximately 125-128T, and BTC trading around $80,000.

FPPS Pools (Predictable Revenue)

• Foundry USA (~37% of network hashrate): Listed at 0% fee. FPPS model with margin embedded in rate calculation. Daily settlement. Best for large operations (100+ PH/s) where account-level terms are negotiated directly. U.S.-based stratum servers with low latency for North American miners.
• AntPool (~14% of hashrate): 2.5% FPPS fee. Bitmain-affiliated. Supports S21/S23 firmware features natively. 0.001 BTC minimum payout. Strong Asian server infrastructure, competitive for miners hosting in facilities with Asian-routed connectivity.
• F2Pool (~8% of hashrate): 2.5% FPPS fee. One of the oldest pools. Multi-coin support. 0.005 BTC minimum payout — the highest threshold among major pools. Global server distribution.
• Luxor (~3% of hashrate): Varies by account (typically 1-2% negotiated). FPPS with daily Net 1 settlement. Strong hosting provider partnerships. Hashrate derivatives and forward contracts available for hedging.

PPLNS and Alternative Pools (Lower Fees, Higher Variance)

• Braiins Pool (~5% of hashrate): 0% fee for PPLNS (Score model). 2% for FPPS. Requires Braiins OS+ firmware for 0% tier. Deep integration with Braiins firmware autotuning. Strong choice for miners already running Braiins OS+.
• OCEAN (~2% of hashrate): 0% fee on TIDES (Transparent Index of Distinct Extended Shares) payout model. Coinbase-level transparency — every miner’s share visible on-chain. Non-custodial: payouts directly in the coinbase transaction. Lower hashrate means higher block-finding variance.
• ViaBTC (~7% of hashrate): 2% PPLNS fee, 4% FPPS fee. Auto-switch between payout methods. Shenzhen-based with global coverage.

How to Split-Test Pools With Your Own Hashrate

Never commit your entire fleet to a new pool based on advertised rates alone. Split-testing reveals real-world effective yield differences that published fees cannot capture.

The 48-72 Hour Split Test Protocol

1. Divide your fleet: Assign 50% of your hashrate to your current pool and 50% to the candidate pool. Use your mining management dashboard to route specific workers to each pool via their stratum configuration.
2. Standardize the comparison: Both groups must run identical hardware, firmware, and power profiles. If you are comparing an S21 fleet, do not put overclocked units on one pool and stock units on the other.
3. Run for a minimum of 48 hours: 72 hours is better. Shorter tests are dominated by variance noise, especially for PPLNS pools. FPPS pools stabilize faster, but 48 hours captures daily settlement cycles.
4. Record these metrics per pool:
   • Total BTC received per TH/s of submitted hashrate
   • Stale share percentage
   • Rejected share percentage
   • Payout timing (hours between earning and receiving BTC)
   • Dashboard responsiveness and data granularity
5. Calculate effective yield: Divide total BTC received by total hashrate contributed (in TH/s) and total hours. Express as satoshis per TH per hour. The pool with the higher effective yield wins, regardless of stated fees.

Important: A single 48-hour test is directional, not definitive. Network conditions, mempool congestion, and pool luck all fluctuate. If the difference is less than 0.5%, run a second test the following week before making a permanent switch.

Step-by-Step Pool Migration Checklist

Once you have decided to switch, follow this checklist to migrate without losing a single share of hashrate.

Pre-Migration (24 Hours Before)

• Create and verify your account on the new pool. Set your BTC payout wallet address. Complete any KYC requirements (Foundry requires institutional verification; OCEAN requires none).
• Configure payout settings: Set minimum payout threshold, payout frequency, and wallet address. Enable 2FA on the new account immediately.
• Record your current pool’s stratum endpoints: Server address, port, and worker naming convention. You will need these as backup failover targets.
• Copy the new pool’s stratum URLs: Primary server, backup server(s), and port numbers. Select the server geographically closest to your mining facility.
• Verify your current pool’s final payout: Check minimum payout thresholds. If your balance is close to the minimum, consider waiting until the next payout before migrating to avoid leaving dust behind.

Migration (Execute During Low-Revenue Period)

Schedule the switch during a period of low transaction fees (typically weekends or early morning UTC) to minimize the revenue impact of any brief interruption.

1. Update Pool 1 stratum on each worker/ASIC to the new pool’s primary server, port, and worker name.
2. Set Pool 2 to the new pool’s backup server for failover.
3. Set Pool 3 to your old pool’s server as a tertiary failover. This ensures hashrate never goes idle if the new pool experiences issues during your first 48 hours.
4. Apply changes and verify: Confirm workers appear on the new pool’s dashboard within 5-10 minutes. Check that submitted hashrate matches your expected total.
5. Monitor stale and rejected rates for the first hour. If stale rates exceed 1.5%, try the new pool’s alternate server endpoint before reverting.

Post-Migration (First 7 Days)

• Compare daily yields to your historical average on the old pool. Account for BTC price changes and difficulty adjustments when comparing.
• Verify payout delivery: Confirm the first payout arrives on schedule and in the correct amount.
• Remove the old pool from Pool 3 failover after 7 days of stable operation on the new pool.
• Withdraw any remaining balance from your old pool account. Some pools expire balances after 90-180 days of inactivity.

When to Switch Pools: Five Trigger Events

Do not switch pools impulsively. These five events justify re-evaluation:

1. Fee structure change: Your pool raises fees or changes its FPPS calculation methodology. Even a 0.5% increase on 50 PH/s costs $600+ per year.
2. Persistent high stale rates: Stale rates consistently above 1% after optimizing your network connection indicate server infrastructure problems on the pool side.
3. Hashrate concentration risk: If your pool exceeds 40% of network hashrate, decentralization principles and censorship risk argue for diversification. Foundry USA’s current ~37% share is approaching this threshold.
4. New pool with better economics: A split test confirms measurably higher effective yield (more than 0.5% difference sustained over 72+ hours).
5. Transparency breach: The pool changes reporting without notice, removes block-level payout detail, or cannot explain a payout discrepancy when questioned.

Multi-Pool Strategy for Larger Operations

Operations running 50 PH/s or more should consider distributing hashrate across two or three pools simultaneously rather than concentrating on one. Benefits include:

• Failover redundancy: If your primary pool experiences downtime, only a portion of your hashrate is affected.
• Continuous benchmarking: Running 70/20/10 splits across three pools provides ongoing yield comparison data without dedicated test periods.
• Negotiating leverage: Demonstrating hashrate committed to competitors strengthens your position when negotiating custom fee tiers with your primary pool.
• Network decentralization: Distributing hashrate across pools reduces the risk of any single pool gaining censorship-capable network share.

Rax Mining’s hosted mining infrastructure supports multi-pool configurations, allowing hosted clients to split their fleet across pools through per-worker stratum settings managed via the facility’s monitoring dashboard.

FAQ

How much hashrate downtime should I expect during a pool switch?

Zero, if done correctly. ASICs reconnect to a new stratum endpoint within seconds. By setting your old pool as the tertiary failover (Pool 3), your miners maintain connectivity even if the new pool’s server is temporarily unreachable during configuration. Total share loss during a properly executed migration is typically under 30 seconds per machine.

Is it worth switching from a 2.5% FPPS pool to a 0% FPPS pool?

Not necessarily. A pool advertising 0% fees may embed its margin in the FPPS rate calculation, potentially resulting in lower net payouts than a transparent 2.5% pool that pays a higher base FPPS rate. The only way to know is a split test comparing actual BTC received per TH over 48-72 hours. Effective yield, not listed fees, determines the better deal.

Should I use FPPS or PPLNS?

FPPS suits most miners, especially those relying on predictable cash flow for electricity payments and estimated tax obligations. PPLNS offers lower fees and potentially higher long-term yields, but introduces block-finding variance that can create cash flow gaps. Operations with cash reserves to absorb 30-day variance swings may benefit from PPLNS. Miners living close to breakeven should stay on FPPS.

How often should I re-evaluate my mining pool?

Run a formal split test every six months, or immediately after any of the five trigger events listed above. Pool economics shift with network conditions, and a pool that was optimal six months ago may no longer be the best choice after a difficulty adjustment cycle or fee structure change.

Optimize Every Layer of Your Mining Operation

Pool selection is one piece of the profitability puzzle. Pair the right pool with industry-leading hosting rates at $0.075/kWh, efficient next-generation ASICs, and professional fleet management. Contact Rax Mining to discuss hosted mining configurations, multi-pool setups, and strategies to maximize your operation’s net yield.