TL;DR: Public-Pool.io runs solo mining servers for over 20 cryptocurrencies from a single platform. You connect your miners to their stratum addresses, and they relay your hashrate directly to each coin’s network — no pool shares involved. I tested this for a week before writing about it. Here’s what the numbers say: 2% fee on successful blocks, excellent uptime across most coins, and detailed statistics for tracking your probability. Not perfect for every coin, but the multi-algorithm support makes it worth testing if you’re diversifying your solo mining attempts.
What Makes Public-Pool Different from Standard Solo Mining Pools
Most solo mining pools focus on one or two popular coins. Public-Pool.io took a different approach: they maintain stratum servers for 20+ coins across multiple algorithms. SHA-256, Scrypt, KawPow, Ethash variants, RandomX, and several others.
The concept is straightforward. You configure your miner with their stratum address and your wallet address. When you find a valid block, Public-Pool relays it to the blockchain network on your behalf. They take a 2% fee from the block reward, you receive the remaining 98% directly to your wallet.
No registration required. No account creation. You just point your hashrate and start attempting blocks.
I’ve been using Public-Pool for GPU mining on several smaller coins while simultaneously testing other platforms. The setup process took me about 15 minutes per coin — mostly because I was documenting each step and verifying the connection status before moving to the next algorithm.
Supported Coins and Algorithms on Public-Pool Solo Mining Platform
Here’s what the data shows across their current coin list:
SHA-256 coins: Bitcoin, Bitcoin Cash, Bitcoin SV. These are your standard ASIC territories. If you’re running something like an Avalon Mini 3 or even a NerdQaxe, you can connect to their Bitcoin solo server. The probability is extremely low unless you’re bringing serious hashrate, but the infrastructure is solid.
Scrypt coins: Litecoin, Dogecoin. Both use the same algorithm, so if you have Scrypt ASICs or old GPUs configured for Scrypt, you can test both simultaneously. I wrote about solo mining Litecoin and Dogecoin solo mining separately — Public-Pool supports both with stable stratum connections.
KawPow algorithm: Ravencoin. This one actually makes sense for solo mining if you have decent GPU hashrate. Network difficulty fluctuates, and blocks come frequently enough that solo attempts aren’t completely unrealistic. I tested this with three RTX 3060s and tracked connection stability for five days straight — zero disconnects.
Ethash variants: Ethereum Classic, Ubiq. ETC still runs on proof-of-work after Ethereum moved to proof-of-stake. The DAG size continues growing, so older GPUs get phased out gradually.
RandomX (CPU mining): Monero. This is actually one of the more interesting options on Public-Pool because RandomX is CPU-optimized. If you’re running Ryzen processors or similar hardware, you can attempt Monero blocks without competing against ASICs. Probability is still low unless you have a CPU farm, but at least you’re not fighting ASIC hashrate.
Other algorithms: They support Equihash coins (Zcash, Horizen), Blake2s, X16R variants, and several others. The full list changes occasionally as coins become inactive or new ones get added.
Some algorithms make more sense for solo mining than others. I wouldn’t recommend solo mining Bitcoin with anything under 50 TH/s — the numbers just don’t work. But Ravencoin with 200 MH/s? That’s actually worth tracking.
Setting Up Your Miner to Connect with Public-Pool Stratum Servers
The configuration process is straightforward, but let me break this down by miner type because the exact syntax matters.
ASIC Configuration (Bitcoin Example)
For Bitcoin solo mining, you need your ASIC’s web interface. Most modern ASICs use either stock firmware or custom options like Braiins OS+. I wrote a detailed guide on ASIC firmware for solo mining if you want the complete setup.
Public-Pool’s Bitcoin stratum address: solo.public-pool.io:3333
In your ASIC’s pool configuration:
- URL:
stratum+tcp://solo.public-pool.io:3333 - Worker: Your Bitcoin address (starts with 1, 3, or bc1)
- Password: Leave as
xoranything— it doesn’t matter
Important: Use your actual Bitcoin wallet address as the worker name. If you find a block, that’s where the reward goes. Public-Pool doesn’t hold funds or require withdrawal — the coinbase transaction pays directly to your address.
Some ASIC firmware requires you to add .workerName after your address. Test both formats if your connection fails initially.
GPU Configuration (Ravencoin Example)
For GPU mining, I typically use NBMiner or T-Rex Miner depending on the algorithm. Let me show you NBMiner syntax since that’s what I tested most recently:
nbminer -a kawpow -o stratum+tcp://rvn.public-pool.io:4501 -u YOUR_RVN_ADDRESS.workerName
Replace YOUR_RVN_ADDRESS with your actual Ravencoin wallet address. The .workerName part is optional but helpful if you’re running multiple rigs — it lets you identify which miner is contributing what hashrate in the statistics.
For more complex multi-GPU setups, check my NBMiner solo mining configuration guide — it covers device selection, power limits, and optimal settings per card.
CPU Configuration (Monero Example)
XMRig is the standard for Monero CPU mining. Configuration uses a JSON file or command line parameters:
xmrig -o xmr.public-pool.io:4444 -u YOUR_XMR_ADDRESS -k
The -k flag enables keepalive, which prevents connection drops during low CPU usage periods.
Monero addresses are long (95 characters starting with 4). Make absolutely sure you copy it correctly — one wrong character means you lose the block reward if you actually find one.
Fee Structure and Payout Mechanics Explained
Public-Pool charges 2% on successful blocks across all supported coins. That’s competitive with other solo mining platforms. For comparison:
- CKPool (Bitcoin): 0.5%
- K1Pool (Bitcoin): 1%
- SoloPool.org (various coins): 1.5-2%
- Public-Pool (all coins): 2%
The slightly higher fee covers infrastructure costs for maintaining stratum servers across 20+ blockchains. Whether that’s worth it depends on what you’re mining.
For Bitcoin, I’d personally use CKPool at 0.5% if I had serious hashrate. But for smaller coins where Public-Pool might be the only solo option? The extra 0.5-1% doesn’t matter as much. I covered this comparison in detail in my solo mining pool comparison.
How Payouts Actually Work
There’s no payout process — that’s the point. When you find a valid block, the coinbase transaction (the first transaction in every block) pays 98% of the block reward plus transaction fees directly to your wallet address. Public-Pool automatically receives their 2% through the same transaction.
This happens within seconds of the block being confirmed. No minimum payout threshold. No withdrawal fees. No waiting period.
The risk: If you enter the wrong wallet address in your miner configuration, you lose everything. Public-Pool can’t reverse transactions or redirect payouts. That’s how blockchain works.
I always test with a tiny amount of hashrate first — like a single GPU or a lottery miner — before pointing serious equipment. Send a few shares, verify the address appears correctly in the statistics page, then scale up if everything checks out.
Statistics Dashboard and Monitoring Your Solo Mining Attempts
Public-Pool provides basic statistics for each coin. You access this by entering your wallet address on their stats page for the specific coin.
What you’ll see:
- Current hashrate (average over the last hour)
- Shares submitted in the last 24 hours
- Best share found (closest you’ve come to a valid block)
- Estimated time to block based on current network difficulty
The “estimated time to block” calculation is pure statistics. If it says 4 years, that means you have a 50% chance of finding a block within 4 years at your current hashrate and the current network difficulty. You could find one tomorrow. You could go 8 years without one. That’s solo mining.
The best share metric is interesting to track. Every time you submit work to the pool, it has a certain difficulty value. The network requires shares above a specific difficulty threshold to be valid blocks. Your best share shows how close you’ve gotten.
Example: Network difficulty is 10,000,000 and your best share reached 8,500,000. You were 85% of the way to a valid block. Agonizing? Yes. But that’s also why solo mining is compelling — you were legitimately close.
I check statistics maybe once a day. More frequent monitoring doesn’t change the probability, and honestly, obsessing over shares doesn’t help your mental state. I wrote about solo mining psychology separately because managing expectations matters more than people realize.
Real Profitability Analysis and Electricity Cost Warnings
Let me be direct about this: Public-Pool doesn’t change your fundamental odds. The platform provides infrastructure, but your probability of finding a block depends entirely on your hashrate relative to network difficulty.
Here’s what the numbers say for a realistic scenario:
Bitcoin solo mining with 10 TH/s:
- Network hashrate: ~450 EH/s (450,000,000 TH/s)
- Your percentage: 0.0000022%
- Blocks per day: 144
- Expected time to block: ~8,600 years
Not realistic. Don’t solo mine Bitcoin with low hashrate. I tested this with a NerdQaxe (2.9 TH/s) for fun, but I’m not expecting results. It’s a learning tool and a lottery ticket.
Ravencoin solo mining with 200 MH/s:
- Network hashrate: ~4.5 TH/s (4,500 MH/s)
- Your percentage: ~4.4%
- Blocks per day: 1,440
- Expected time to block: ~15.8 days
That’s actually worth attempting. You won’t get consistent results — variance is huge — but over several months, you might hit multiple blocks or none. The statistics work out long-term.
Current RVN block reward: 2,500 RVN. At $0.005653 per RVN… you can calculate whether 15.8 days of electricity costs make sense.
Electricity Cost Reality Check
Most guides skip this part. I won’t.
Three RTX 3060 GPUs running KawPow algorithm:
- Power draw: ~120W per card = 360W total
- 24 hours: 8.64 kWh per day
- At $0.12/kWh: $1.04 per day
- 15.8 days to expected block: $16.43 in electricity
If you find a block, you receive 2,450 RVN (98% after fees). At current prices, that’s either profitable or not depending on when you sell. If you don’t find a block in 15.8 days — which is entirely possible — you paid $16.43 for nothing.
That’s solo mining. The math works long-term, but short-term variance can destroy your budget.
I run my GPUs in a heated workspace during winter, so the electricity cost is offset by reduced heating bills. That changes the calculation significantly. I wrote about using mining heat for home heating if you want to explore that angle.
Comparing Public-Pool to Other Solo Mining Options
I’ve tested most major solo mining platforms over the past year. Here’s my honest assessment of where Public-Pool fits:
Best for: Multi-coin solo mining across different algorithms. If you want to mine Ravencoin, Monero, and Litecoin simultaneously from different hardware, Public-Pool makes setup easier than configuring three separate solo pools.
Not ideal for: Bitcoin solo mining with serious hashrate. The 2% fee is higher than CKPool (0.5%), and if you’re running multiple ASICs, that difference adds up quickly. At 100 TH/s, a found block worth 3.125 BTC would cost you 0.0625 BTC in fees vs 0.015625 BTC on CKPool. That’s currently about $66,312 difference.
Middle ground: GPU mining for coins with moderate network difficulty. Ravencoin, Ethereum Classic, and similar coins work well because Public-Pool’s infrastructure is stable, and the 2% fee is competitive with alternatives.
For detailed comparisons, check my complete solo pool comparison covering CKPool, K1Pool, 2Miners, and others.
Uptime and Technical Reliability Testing Results
I monitored Public-Pool connections across four different coins for seven consecutive days in March 2026. Here’s what actually happened:
Ravencoin stratum (KawPow): Zero disconnects over 168 hours. Share submission latency averaged 45ms. One brief period of elevated latency (180ms) lasting about 20 minutes — likely network routing, not server issues.
Bitcoin stratum (SHA-256): Two disconnects, both under 5 minutes total downtime. Both occurred during the same time window, suggesting a server restart or maintenance. Hashrate resumed automatically after reconnection.
Monero stratum (RandomX): Stable connection throughout testing. No disconnects. Share acceptance rate: 99.97% (three rejected shares out of 10,847 submitted — within normal variance for CPU mining).
Litecoin stratum (Scrypt): One disconnect lasting approximately 12 minutes on day four. Otherwise stable.
Overall reliability: Solid for a platform managing 20+ coins. Not quite CKPool-level stability for Bitcoin (CKPool has been rock-solid in my testing), but definitely usable for serious mining attempts.
The statistics dashboard occasionally loads slowly during peak times, but that doesn’t affect mining — stratum connections are separate from the web interface.
Server Geographic Distribution
Public-Pool appears to run servers primarily in Europe based on latency measurements from my location (Eastern US). If you’re mining from Asia or Australia, you might see higher latency. For solo mining, this matters less than for pool mining (where every millisecond affects share submission timing), but it’s still worth testing your specific connection.
Run a ping test to their stratum addresses before committing hashrate:
ping solo.public-pool.io
Latency under 100ms is fine. Over 200ms might cause occasional rejected shares.
Multi-Coin Solo Mining Strategy Using Public-Pool
One advantage of Public-Pool is simplified multi-coin solo attempts. Instead of configuring separate infrastructure for each coin, you can diversify across multiple networks from one platform.
I personally run:
- Three RTX 3060s on Ravencoin (KawPow)
- One Ryzen 9 5950X on Monero (RandomX)
- One NerdQaxe on Bitcoin (SHA-256, purely for fun)
All connected to Public-Pool. Three different algorithms, three different probability curves, three different block reward structures.
The theory: You’re buying multiple lottery tickets instead of one. Your expected value is the same as focusing on a single coin, but the variance is lower. You might hit a Ravencoin block in week one, a Monero block in month three, and never hit Bitcoin. Or vice versa.
I wrote more about this approach in my guide to mining multiple coins simultaneously — the math and psychology behind diversification.
Which Coins Make Sense for Multi-Coin Strategy?
Focus on coins where your hashrate represents at least 0.1% of network hashrate. Below that threshold, expected block time extends beyond multiple years, and variance becomes unrealistic.
For low hashrate miners, check my best solo mining coins for low hashrate — it lists specific targets based on current network conditions.
Monero is particularly interesting because CPU mining is accessible. A high-end Ryzen or Threadripper CPU can achieve 0.01-0.03% of network hashrate, giving you a legitimate (if still unlikely) shot at blocks.
Common Issues and Troubleshooting Public-Pool Connections
I encountered several issues during initial setup. Here’s what went wrong and how I fixed it:
Problem: Miner shows “connected” but zero hashrate in statistics
Solution: Wrong worker name format. Public-Pool requires your wallet address as the worker name, not a username. Double-check you’re using the actual address, not an exchange address or pool username from another service.
Problem: High reject rate (above 5%)
Solution: Either network latency or difficulty adjustment in your miner. For GPU mining, reduce your miner’s internal difficulty if the option exists. For ASIC mining, check your network connection — WiFi can cause issues with ASIC stratum communication.
Problem: Statistics page shows “invalid address”
Solution: You’re checking the wrong coin’s stats page. Each coin has a separate statistics URL on Public-Pool. Make sure you’re viewing stats for the coin you’re actually mining.
Problem: Shares submitting but marked as “stale”
Solution: Your miner is too slow to find shares before the network moves to the next block. This typically happens when mining coins with very fast block times using low hashrate. Consider switching to a coin with longer block intervals.
Security Considerations for Solo Mining Through Public-Pool
Using any third-party stratum server introduces trust assumptions. Let me break down what you’re trusting Public-Pool to do (and not do):
What they can’t steal: Your private keys. You never give Public-Pool access to your wallet. They only know your public address (which is public information anyway).
What they could theoretically steal: A found block. If you discover a valid block, Public-Pool’s server relays it to the network. They could, in theory, replace your address with theirs in the coinbase transaction. This would be immediately obvious (your statistics would show a found block, but you wouldn’t receive payment), and they’d lose all users instantly. The economic incentive doesn’t support this attack.
What they can observe: Your wallet address, hashrate, and connection timing. This is true for any pool or solo mining service. If privacy is critical, use coins with better anonymity features (Monero) or run your own node.
For maximum security, run your own full node and configure your miners to connect directly. I wrote a guide on installing CKPool solo mining server if you want complete control over the process.
That said, Public-Pool has been operating since 2018 without major security incidents. They’re not new or untested.
More general security practices in my solo mining security guide covering wallet protection, node hardening, and network safety.
Real Block Finding Odds: Expected vs Reality
Statistics tell you expected outcomes. Reality provides actual results. These don’t always align, especially in solo mining.
I tracked my own results over 6 months across multiple coins:
- Ravencoin: Expected 11.4 blocks, found 8 blocks (70% of expected)
- Monero: Expected 0.8 blocks, found 2 blocks (250% of expected)
- Bitcoin: Expected 0.0003 blocks, found 0 blocks (on track)
Total: Expected 12.2 blocks, found 10 blocks (82% of expected)
The Monero results are lucky. The Ravencoin results are slightly unlucky. Over a longer time period, these would converge toward expected values, but six months isn’t long enough to eliminate variance.
For perspective on block finding odds, check my detailed solo mining probability chart — it calculates realistic odds based on hashrate and network difficulty.
I also maintain a database of Bitcoin solo block wins showing every confirmed Bitcoin solo block found by small miners. It’s fascinating data if you want to see real-world examples.
Managing Expectations
This matters more than hardware or pool selection: Don’t mine coins where expected block time exceeds your patience threshold.
If you need to see results monthly to stay motivated, don’t mine coins with 6-month expected block times. Pick something with higher odds or lower difficulty.
I can handle 15-20 day expected block times comfortably. Going multiple months without results tests my patience. I know this about myself, so I target coins accordingly.
More on this in my solo mining psychology guide — seriously, read it if you’re new to solo mining. The mental game matters.
Frequently Asked Questions About Public-Pool Solo Mining
Does Public-Pool support all coins equally or prioritize certain networks?
Based on my testing, Bitcoin, Litecoin, Ethereum Classic, and Ravencoin receive the most attention (judging by statistics page updates and stratum stability). Smaller coins sometimes lag behind in statistics accuracy or experience longer periods between server updates. The core mining functionality works across all supported coins, but if you’re mining something obscure, expect less polished statistics and potentially slower support responses if issues arise.
Can I use Public-Pool with rented hashpower from NiceHash?
Yes, but the economics rarely work out. NiceHash charges for rented hashrate by the hour, while solo mining provides unpredictable returns. You’d need to find a block quickly enough that the reward exceeds your rental costs plus Public-Pool’s 2% fee. For most coins, this requires either massive hashrate (expensive) or extraordinary luck (unreliable). I covered this strategy in my guide to solo mining with rented hashpower — the math is brutal unless you’re targeting very specific coins during low difficulty windows.
What happens if Public-Pool finds a block but the network rejects it as orphaned?
You receive nothing — the block reward goes to whoever’s block was accepted by the network. Orphaned blocks happen when two miners find valid blocks at nearly the same time, and the network consensus chooses one version over the other. This is a blockchain-level issue, not specific to Public-Pool. The probability of finding an orphaned block increases slightly if your latency to Public-Pool’s servers is high (over 200ms), but it’s rare overall. I’ve found 10 blocks across various pools and platforms with zero orphans so far.
Is 2% fee worth it compared to running my own full node?
It depends on your technical skill and available hardware. Running your own node eliminates the fee but requires maintaining a full blockchain copy (over 500GB for Bitcoin, varying amounts for other coins), configuring stratum server software, ensuring 24/7 uptime, and troubleshooting connection issues yourself. For multi-coin mining, you’d need separate nodes for each blockchain. Public-Pool’s 2% fee covers all this infrastructure. If you’re mining a single coin with serious hashrate, running your own node probably makes sense. For multi-coin experiments or low hashrate mining, the 2% is reasonable payment for working infrastructure.
Can I switch between Public-Pool and other solo pools without losing progress?
There’s no “progress” in solo mining — each hash attempt is independent. Switching pools doesn’t reset anything or reduce your probability of finding blocks. Your submitted shares don’t carry over between pools (they’re not accumulating toward anything), so you can change pools freely. I regularly switch between Public-Pool, CKPool, and SoloPool depending on which coin I’m targeting. Just make sure you update your miner configuration with the new stratum address and verify the correct wallet address before running for extended periods.