How to Choose a Solo Mining Pool

A solo mining pool is a service that builds block templates, distributes work to your miners, and — when you find a valid block — pays the full reward to your wallet address, minus a small fee. Unlike shared pools, there are no proportional payouts: you win everything or nothing. That makes choosing one simpler in some ways (no payout-scheme math) and more demanding in others: when a single share might be worth an entire block reward, the pool’s security, latency, and payout mechanics deserve real scrutiny before you connect a single machine.

Key takeaways

• Seven criteria cover everything that matters: fee structure, verifiable non-custodial payouts, TLS encryption, latency and regional endpoints, per-worker monitoring, coin support, and operator reputation. Every one of them can be checked yourself, from the outside, before committing hashrate.
• Plaintext stratum is a real, documented risk. Research published in 2025 confirmed hashrate hijacking over unencrypted Stratum V1 as an active attack vector in production, with typical losses of up to 2% of a facility’s hashrate before detection. A pool that offers TLS endpoints removes that entire class of attack.
• Verifiable payouts beat promised payouts. On a genuinely non-custodial pool, the coinbase transaction of every found block pays the winner’s address directly. You can verify this on a block explorer for any block the pool has ever found — no trust required.
• Latency matters most at the moment it matters most. A distant server adds stale shares all year, but for a solo miner the critical event is the winning share: the longer it travels, the larger the window for an orphan race. Regional endpoints are not a luxury.
• There is no single best pool — there is a best pool for your setup. A Bitaxe on a shelf, a rack of S21s, and a rented burst of hashrate weight the seven criteria differently. The decision framework at the end maps each profile to its priorities.

Solo mining has grown from a curiosity into a measurable movement: individual miners collected roughly 66 BTC in block rewards over the past year, up about 17% from the year before, while the Bitcoin network crossed one zetahash per second. That growth brought new pools, new marketing, and new claims. This guide deliberately reviews no pool by name and ranks nothing. Instead, it gives you the checklist a careful miner would apply to any pool — including ours. Ten years of pool history or ten days, the same seven questions apply.

What does a solo pool actually do for you?

Understanding what you’re evaluating helps you evaluate it. A solo pool performs four jobs. First, it runs full nodes for the chain you’re mining and assembles block templates — the candidate blocks your hardware hashes. Second, it runs a stratum server that distributes that work to your miners and adjusts share difficulty (vardiff) so your Bitaxe and your S21 can both talk to it comfortably. Third, it constructs the coinbase transaction — the special transaction that pays the block reward — before anyone knows who will win. Fourth, it provides statistics: hashrate charts, best shares, worker status.

Every criterion below tests one of those four jobs. Fees and payout verification test the coinbase construction. TLS and latency test the stratum layer. Monitoring tests the statistics layer. Coin support and reputation test the node infrastructure and the humans behind it.

Criterion 1 — How is the fee taken, and can you see it?

Solo pool fees typically range from 0% to 2%, and the honest way to charge one is inside the coinbase transaction itself: when a block is found, the coinbase pays (for example) 99% to the winner’s address and 1% to the pool’s address, in the same transaction, visible forever on-chain. That structure means the fee is enforced by the block itself — the pool cannot quietly change it after the fact, and you can audit every block it has ever paid.

How to verify: find the pool’s list of found blocks, open any block in an independent explorer, and inspect the coinbase outputs. The split should match the advertised fee exactly. Also check what happens to transaction fees inside the block: on most solo pools they go to the winner along with the subsidy, but this should be stated. Be cautious with a 0% fee only in one sense: infrastructure costs money, so understand how the pool sustains itself — donations, a company behind it, or paid tiers are all legitimate answers. An unexplained free lunch is a question worth asking, not an automatic red flag.

Criterion 2 — Are payouts non-custodial and verifiable on-chain?

Non-custodial means the pool never holds your coins. The block reward goes from the network’s coinbase directly to the wallet address you mined with — there is no pool balance, no withdrawal button, no minimum payout threshold, and no moment where the operator could freeze or lose your funds. For solo mining, where a single event might be worth a six-figure sum, this is the difference between “the pool pays winners” as a promise and as a mathematical property of the block.

How to verify: take any block the pool claims to have found, open its coinbase transaction on a block explorer the pool doesn’t control, and confirm the reward outputs pay a miner address (plus the fee output from Criterion 1). Then confirm the pool signs its blocks — a recognizable coinbase signature or tag lets explorers and the wider ecosystem attribute blocks to the pool, which keeps its “blocks found” list honest. A pool whose claimed wins cannot be traced on-chain is asking for trust it hasn’t earned. This single check takes five minutes and tells you more than any marketing page.

Criterion 3 — Does the pool offer TLS-encrypted stratum?

Classic Stratum V1 transmits everything as plaintext JSON over an unencrypted TCP connection: your wallet address, your worker names, and every share you submit are readable by anyone on the network path — your ISP, a compromised router, or an attacker in the middle. The consequences are documented, not theoretical: hashrate hijacking, where intercepted traffic is silently redirected, was confirmed by 2025 research as an active production attack with typical losses of up to 2% of a facility’s hashrate before detection, and suspected cases have been reported from miners across several continents.

For a solo miner there is also a quieter cost: plaintext traffic lets any observer on the path infer your hashrate, estimate your hardware, and link it all to your wallet address. Encryption closes both problems at once.

How to verify: check whether the pool publishes TLS stratum ports alongside its standard ones, and test the handshake yourself with openssl s_client -connect host:port. If your firmware supports it, prefer the TLS endpoint permanently. For the deeper protocol picture — including what Stratum V2 changes — see our Stratum V2 vs V1 guide.

Criterion 4 — How close is the nearest endpoint, and does it matter?

Latency creates stale shares: work that was valid when your miner computed it but arrived after the pool had moved to a new job. The physics are simple — every millisecond of round-trip time is a window in which the network can change. As a rule of thumb, connecting at 300 ms instead of 30 ms adds roughly the extra round-trip divided by the block time to your stale rate; a healthy setup keeps stales around 0.2% or below, and a wired Ethernet connection is the single cheapest improvement you can make.

For solo miners, though, averages undersell the point. Your year of hashing produces exactly one share that matters — the winning one. If that share, or the block built from it, travels slowly, you widen the window for an orphan race: another miner finds a competing block and the network adopts theirs. Regional stratum endpoints exist precisely so the decisive share has the shortest possible path.

How to verify: ping every endpoint the pool publishes and pick the lowest round-trip time — but judge the pool by your stale share percentage after a day of mining, not by ping alone. A pool with servers on your continent, or better, in your region, has a structural advantage no software setting can replicate.

Criterion 5 — Can you actually see what your miners are doing?

Solo mining is a long game, and the dashboard is where you live between blocks. The monitoring layer determines whether you notice a problem in hours or in weeks: a worker that silently dropped offline, a hashboard degrading below nominal hashrate, a rising reject rate pointing at a network issue. Since your ASIC burns the same electricity for a rejected share as an accepted one, every undetected problem is money spent on work that earns nothing.

What good looks like: per-worker hashrate (not just an account total), accepted and rejected share counts, best-share tracking (your closest approaches to a block — the heartbeat of solo mining), and enough history to spot trends rather than moments. Bonus points for API access so you can build your own alerts.

How to verify: most pools let you view stats for any address. Look up an active address before connecting anything, and check the pool’s public statistics page while you’re there: a pool that shows its own aggregate hashrate, worker counts, and full block history in public is making itself auditable. Then point one machine — just one — and live with the dashboard for a week before committing the rest.

Criterion 6 — Which coins can you mine, and does optionality matter to you?

Your SHA-256 hardware is not Bitcoin-only. The same ASIC can mine any SHA-256 chain — and because smaller chains have a fraction of Bitcoin’s difficulty, the identical machine faces dramatically shorter expected times to find a block there. The trade-off is symmetrical and must be stated honestly: smaller chains carry smaller block values, thinner exchange liquidity, and higher volatility. Neither choice is wrong; they are different points on the same probability-versus-value curve, and our coin-by-coin breakdown runs the actual numbers.

What matters when choosing a pool is optionality: a pool that supports several SHA-256 chains lets you move between them by changing one stratum URL, without new accounts, new dashboards, or new trust decisions. If you ever intend to experiment — after a difficulty drop on a small chain, say, or when renting a burst of hashrate — multi-coin support turns that experiment into a five-minute change.

How to verify: check the supported-coin list, confirm each coin pays to your own wallet format non-custodially (the Criterion 2 test, per chain), and confirm the pool runs its own nodes for each chain rather than proxying someone else’s.

Criterion 7 — Who runs this, and what is their track record?

Every pool is ultimately people and infrastructure. Reputation is the slowest criterion to build and the hardest to fake, and it deserves respect where it exists: the longest-running solo pools have proven themselves through years of found blocks and paid winners, and that history has genuine value — much of today’s solo mining ecosystem, including open-source pool software that newer operators build on, exists because of that early work. A newer pool isn’t disqualified by youth, but it carries the burden of proof: transparent operations, verifiable blocks from day one, and responsive communication.

How to verify: look for a public block history that satisfies Criterion 2; an operator who answers questions in public (forums, community threads, social channels); published infrastructure facts like server regions and TLS support; honest communication about odds — a pool that tells you solo mining is negative expected value for most miners is telling you the truth, and truth in marketing predicts truth in operations; and listing on independent trackers where uptime and hashrate are recorded by third parties. Finally, check how the pool handled any past incident. Every operator eventually has one; what distinguishes them is whether they explained it.

The decision framework: which criteria matter most for you?

All seven criteria apply to everyone, but their weights change with your setup. Work through these in order:

1. Mining a Bitaxe or small home miner? Prioritize monitoring (Criterion 5), coin optionality (6), and low-friction setup. Your absolute odds are lottery-scale either way; what you’re really buying is a good long-term experience and the option to point your lottery ticket where the odds are least bad.
2. Running a fleet of S19/S21/S23-class machines? Prioritize TLS (3), latency (4), and monitoring (5). At fleet scale, a 2% hijack or a chronic stale problem is real money, and per-worker visibility is how you catch a degrading hashboard before it costs you a season.
3. Renting hashrate for a burst attempt? Prioritize latency (4), fee mechanics (1), and payout verifiability (2). Rented time is metered — every stale share during your window is paid-for probability thrown away, and you want certainty that a win pays your address with no custody step.
4. Mining from a jurisdiction with network surveillance? TLS (3) moves to the top, full stop.
5. Everyone, always: run the Criterion 2 coinbase check before connecting. Five minutes, zero trust, no exceptions.

Where SoloFury stands: since this guide will be read on our site, transparency demands we state our own choices against our own checklist — a 1% fee taken inside the coinbase, non-custodial payouts you can verify on any explorer, TLS endpoints in every region, per-worker dashboards with best-share tracking, five SHA-256 chains under one roof, and public block history from day one. Apply the seven criteria to us as strictly as to anyone. That’s what the checklist is for.

Conclusion

Choosing a solo pool is not about finding the one with the loudest claims — it’s about verification. The seven criteria above share a single property: every one of them can be checked from the outside, by you, without trusting anyone’s word. The coinbase split is on-chain. The TLS handshake either completes or it doesn’t. The ping is measurable, the dashboard is visible, the block history is auditable, and the operator’s communication is public record.

Solo mining already asks you to accept enormous variance in exchange for self-sovereignty. The pool you choose shouldn’t add trust-variance on top of luck-variance. Verify first, connect second — and once you’ve chosen, give the relationship time: solo mining rewards patience above everything else.