
Solo mining and pool mining pay the same expected reward before fees — the real difference is variance, not profit. A single ASIC can wait years for one block; a pool pays out every day. This guide walks through the math, the fees, and the hashrate threshold where going solo actually makes sense.
Solo mining means pointing your own hardware at the Bitcoin network and competing for blocks alone. Find a block, and the full reward — subsidy plus every transaction fee inside it — is yours. Miss, and you earn nothing for that block, no matter how many valid shares you submitted.
Pool mining combines your hashrate with thousands of other miners into one collective search. Every valid share you submit counts toward your slice of whatever the pool finds, paid out on the pool’s own schedule — often daily.
Both approaches mine the same chain at the same network hashrate — only the payout mechanism changes. That split matters more for Bitcoin than for smaller coins, since Bitcoin’s network hashrate runs into the hundreds of exahashes per second and one miner’s share of it is tiny.
Your expected reward, mathematically, is your share of network hashrate multiplied by the block reward — and that formula is identical whether you mine solo or in a pool. Pool mining doesn’t pay more; it just pays the same total more often, in smaller pieces.
A pool doesn’t pay you more — it just pays you more often.
Solo mining turns that same expectation into rare, lumpy, full-block payouts. Over a long enough stretch — years, not weeks — a solo miner and a pool miner with identical hashrate converge on the same total earnings before fees. The only place they actually diverge in raw expected value is fees: a pool takes a cut for aggregating shares and smoothing your variance, while a solo miner keeps the full reward on the rare block they find.
This is why “pool mining is safer” and “solo mining pays less” are two different claims, and only the first one is true. Pool mining reduces the spread of outcomes around a mean; it doesn’t raise that mean. A miner who understands this can make a genuine risk-tolerance decision instead of assuming solo mining is a worse bet by default.
Expected time to a block follows one formula: your network hashrate share, inverted, times the average block interval. Written out, it’s network hashrate ÷ your hashrate × 10 minutes. A miner running 0.001% of the network’s hashrate should expect to wait roughly 0.001% of the time it takes the whole network to find 100,000 blocks. That’s a very long time.
The average, though, hides the real shape of the risk. Block discovery is a Poisson process: blocks arrive at random, independent intervals, not on a schedule. That means a miner can find a block on day one, or wait three times longer than the “expected” figure and still be within normal variance. The formula gives you a mean, not a promise.
Take a single current-generation ASIC at roughly 200 TH/s, against a network hashrate in the range of 900 EH/s at the time of writing (check a live block explorer for today’s exact figure — network hashrate moves weekly). That single machine’s expected time to a block runs into decades, not days.
| Hashrate | Expected time to a block | Chance of a block within 30 days |
|---|---|---|
| 1 ASIC (~200 TH/s) | ~86 years | ~0.1% |
| Small rack (~1 PH/s) | ~17 years | ~0.5% |
| 10 ASICs (~2 PH/s) | ~8.6 years | ~1% |
Every pool payout scheme falls into one of two families, and the difference is who absorbs the pool’s own bad luck. In one family, the pool eats the variance and charges for it. In the other, the miner still shares in the pool’s swings, but pays a lower fee for the privilege.
PPS and FPPS (Full Pay-Per-Share) pay a fixed rate per valid share, regardless of whether the pool itself is running lucky or unlucky that week. If the pool goes a long stretch without finding a block, it still pays you — out of its own reserves. That guarantee is why PPS/FPPS fees typically run higher than share-based alternatives: the fee funds the pool’s buffer against its own bad rounds. It suits miners who want steady, predictable payouts and don’t want their income tied to a specific pool’s short-term luck.
PPLNS, PROP, and TIDES pay based on the pool’s actual performance over a round — if the pool is running lucky, payouts rise above the theoretical average; if it’s running unlucky, they fall below it. Fees are typically lower than PPS/FPPS because the pool isn’t insuring anyone. TIDES, used by pools like Ocean, refines classic PPLNS by smoothing out the edge-case unfairness that let miners “pool-hop” in and out around lucky rounds. That makes long-term participation fairer without changing the core risk-sharing model.
Solo or pool, your costs are identical — mining doesn’t change your electricity bill or your hardware’s purchase price. What changes is the timing and size of the payout you’re weighing those costs against.
Start with electricity: a modern ASIC drawing about 3.5 kW at $0.06 per kWh costs roughly $5 a day to run continuously. Add hardware amortization — spread a $2,000 machine over a realistic three-year useful life before rising difficulty makes it obsolete, and that adds close to $2 a day. Total daily cost lands near $7.
For that same 200 TH/s ASIC against a 900 EH/s network, at an assumed $60,000 BTC price, expected daily reward lands close to $6 — under the $7 daily cost. That miner runs at a marginal loss on pool payouts, and solo mining doesn’t fix it: solo just concentrates that same expected value into one large, rare payment instead of smoothing it.
The right way to frame the threshold is as a share of network hashrate, not an absolute TH/s figure, because network hashrate itself keeps growing and any fixed number goes stale within months.
Below roughly 0.0002% of network hashrate — about 1.5 to 2 PH/s, or eight to ten current-generation ASICs at the numbers above — expected time to a block stretches past any planning horizon a hobbyist or small operation can reasonably hold. At that share, you’re looking at roughly a one-in-ten chance of a block within a year. That’s the point where the tail outcome stops being pure fantasy and starts being a real, if unlikely, scenario worth planning around.
Solo mining isn’t a profitability decision — it’s a risk-tolerance decision dressed up as one.
Above that threshold, the math from the expected-value section still holds: solo and pool converge on the same long-run payout. What changes is whether your capital runway can survive the wait for that first block without running dry first.
The threshold above isn’t purely theoretical. Solo-mining services such as ckpool’s solo endpoint have documented cases of miners with only a handful of older-generation machines — hashrate far below any “sensible” threshold — finding a full block reward on their own.
What made those outliers possible is exactly what the Poisson framing predicts: pure variance, not a repeatable edge. A miner running a tiny fraction of the network’s hashrate still has a small, nonzero chance of a block on day one — like a lottery ticket that occasionally wins. Ocean, a pool built around solo-friendly TIDES payouts, exists partly because that tail risk draws real interest even from miners who know the odds.
One documented block find doesn’t change the underlying math from earlier in this guide — it confirms it. A low-probability event happening once is exactly what a probability distribution predicts, over enough independent attempts across the whole network.
Switching between solo and pool mining on the same pool almost never requires new firmware — only the stratum endpoint you point your hardware at changes. The stratum URL and port for a solo endpoint are typically distinct from the pool’s shared endpoint, even on the same service.
No firmware flash, no hardware change — just the pool URL, port, and worker name.
Solo and pool mining pay the same expected value before fees; they differ in variance, in fee structure, and in how long you can tolerate waiting for a payout. A single ASIC or a small home rack sits well below the threshold where solo makes statistical sense — pool mining is the rational default there. A larger operation running multiple petahashes starts to cross into territory where solo’s lower long-run fee and full-block upside can outweigh the wait.
If your setup can’t survive years without a payout, mine in a pool — the math doesn’t change, only your patience does.
Before switching either way, compare current Bitcoin mining pools by hashrate and fee — payout scheme, fee, and pool hashrate all shift which option actually fits your hardware today.
No. Solo and pool mining use the same firmware — only the stratum URL and port change to point at the solo endpoint instead of the shared one.
It varies by pool, but solo payouts typically require the standard coinbase maturity of 100 confirmations before funds are spendable, on top of any pool-set minimum payout threshold for regular pool payouts.
Neither pays more on average. PPS and FPPS charge a higher fee to guarantee steady payouts regardless of the pool’s luck, while PPLNS charges less but ties your payout to the pool’s actual luck over each round.
It’s possible but statistically rare at current network hashrate. Documented cases exist through services like ckpool’s solo endpoint, but they sit in the tail of the probability distribution, not the expected outcome.