Solo mining means your hardware competes against the entire Bitcoin network alone, and if it finds a block, you keep the whole reward. Most people who try it connect to a public solo pool, which handles the infrastructure for them. Running your own solo pool at home is the next step: you operate the node, you build the block templates, and your miners work for you directly, with no intermediary at all. It is a satisfying project, and it is also a real piece of infrastructure that has to stay up, stay synced, and stay secure. This guide walks through what the pieces are, what you need, and how to set it up in generic terms, so you can decide whether it is worth doing before you commit a weekend to it.
First, the expectation-setting, because it decides everything else. Solo mining does not change your odds. Whether you mine through a pool, a public solo pool, or your own node, a given amount of hashrate has the same expected time to find a block. At October 2026 network conditions, roughly 1.08 zettahashes per second, a single 234 TH/s machine has an expected wait of about 88 years for one block. That is not a reason to avoid the project, but it is the reason to treat a home solo pool as a learning project, a decentralization statement, or a lottery ticket you fully understand, rather than as an income plan. If you need steady income to cover electricity, mine in a regular pool.
The three pieces of a solo pool
A home solo pool has three parts, and understanding the boundaries between them makes every later decision easier. First is the Bitcoin node. This is software that downloads and validates the entire blockchain, tracks the set of unspent coins, and talks to other nodes on the network. Your node is your independent view of Bitcoin. It does not trust anyone else's copy of the ledger. It checks every block and transaction itself, which is the whole point of running one.
Second is the block template builder. When it is time to mine, somebody has to decide which pending transactions go into the next block and assemble them into a candidate block header. In a regular pool, the pool operator does this. In your own solo setup, your node does it, using its view of the mempool, the waiting area for unconfirmed transactions. This is a meaningful distinction: running your own templates means you are choosing the transactions, not accepting a pool operator's choices. It is also why solo mining appeals to people who care about decentralization. The more miners building their own templates, the less any single pool operator decides what gets into blocks.
Third is the stratum server. Miners do not talk to a Bitcoin node directly. They speak a lightweight protocol called stratum, designed for mining hardware, and the stratum server translates between that protocol and your node. It hands work to your miners, collects their submitted shares, checks whether any share is actually a valid block, and, when one is, hands it to your node to broadcast to the network. When people talk about "pool software," they usually mean this stratum layer plus the template logic around it. Several open-source implementations exist. Pick one that is actively maintained, that documents its configuration clearly, and that other solo miners are actually running, rather than the first one you find.
What hardware and network do you need?
The good news is that a solo pool node does not need mining hardware to run on. It needs a reliable small computer, storage, and an internet connection, and it can live on hardware you may already own. A small single-board computer or a refurbished mini PC with a solid-state drive is a common choice. The demanding part is storage and patience: the blockchain is several hundred gigabytes and growing, and the initial download and validation, called the initial block download, can take days on a slow connection or a slow drive. Use an SSD, not a spinning hard drive or an SD card, and start the sync well before you plan to point miners at the node. A node that is still syncing cannot build current templates.
On the network side, you need a stable internet connection and a stable local network for your miners. Your miners connect to your stratum server on your local network, which keeps latency low and avoids exposing the mining port to the internet. Your node itself connects outward to other Bitcoin nodes, which is normal and does not require opening ports to the world, though some operators choose to accept inbound connections to help the network. Keep it simple at first: outbound-only node connections, miners on the local network only, and a wired ethernet connection for the node machine. Wi-Fi dropouts that are invisible during web browsing will show up immediately as stale work and disconnected miners.
Plan for uptime. A solo pool that is down is a miner earning nothing, and unlike a public pool, there is nobody else keeping it alive while you sleep. A small uninterruptible power supply (UPS) that lets the node ride through short outages and shut down cleanly during long ones is worth the cost. So is a setup you can check from your phone: at minimum, a way to see whether the node is synced, whether the stratum server is accepting connections, and what hashrate your miners are reporting. If you cannot check it remotely, you will discover outages hours later than you needed to.
Setting it up, step by step
The exact commands depend on the software you choose, so this is the shape of the process rather than a copy-paste recipe. Skipping a step here is how people end up with a pool that looks alive but is mining on stale templates, which is worse than a pool that is visibly down.
- Install and sync the node first. Install your node software on its dedicated machine, configure it to store the blockchain on the SSD, and let the initial block download finish completely. Verify it reports the current block height and a synced status before going further. Do not point miners at a syncing node.
- Choose and install the stratum software. Follow that project's own documentation for connecting it to your node. The key configuration is the connection between the stratum server and the node, usually over a local interface, and the payout address your miners will use. Double-check the payout address character by character. A typo here sends a found block's reward somewhere you do not control, and there is no undo.
- Configure your miners. In each miner's web interface, set the stratum address to your server's local address and port, and set the worker name and payout address according to your stratum software's format. Start with one miner, confirm it connects, submits shares, and shows up in the stratum server's status output, then add the rest.
- Verify end to end before trusting it. Confirm the node is at the current tip, the stratum server is distributing fresh work, miners report a hashrate close to their rated figure, and rejected or stale shares are low, generally a few percent at most. High stale rates usually mean latency or an overloaded node machine, not bad luck.
- Test your monitoring and recovery. Reboot the node machine and confirm everything comes back on its own: node, stratum server, and miners reconnecting. Write down the restart steps while you still remember them. The version of you that gets paged at 2 a.m. will be grateful.
Security: the part people skip
A home solo pool holds two things worth protecting: the private keys or payout address associated with any block you might find, and a computer connected to your home network. Keep the node's administrative interfaces bound to the local network only, never exposed to the internet. Use strong, unique passwords on the node machine, the stratum dashboard, and every miner's web interface, and keep the software updated. Miners in particular ship with default credentials that are widely known, and an exposed miner interface is an easy target for anyone scanning the internet.
Think carefully about wallets. The payout address in your stratum configuration should be an address you control, ideally one whose keys live somewhere other than the node machine itself, such as a hardware wallet. If the node machine is ever compromised, you do not want the keys to a found block sitting on the same disk. And back up your configuration and any wallet information separately, offline, in a place you can find again. Losing a configuration is an annoyance. Losing keys is permanent.
One more caution: do not open ports on your router for the stratum server or the node's administrative interface unless you have a specific reason and understand the exposure. The common home setup needs no inbound ports at all for mining to work. Port forwarding feels like progress when you are troubleshooting a connection problem, but it is usually the wrong fix for a local-network problem, and it turns a private service into a public one.
Solo pool at home vs. a public solo pool vs. a regular pool
These three options differ in control, effort, and failure modes, and the right one depends on what you actually want. A regular pool gives you steady, predictable payouts and zero infrastructure to run, in exchange for a small fee and accepting the pool's block templates. A public solo pool gives you the full block reward if you find one, with no infrastructure to run, in exchange for trusting the operator's uptime and templates. Your own solo pool gives you full control over templates and no operator at all, in exchange for all of the uptime, security, and maintenance work described above.
The expected Bitcoin earned per unit of hashrate is essentially the same across all three over a long enough period, minus fees where they apply. What changes is variance and workload. Regular pools smooth variance to nearly nothing. Both solo options keep the full variance: long stretches of zero, punctuated, if you are lucky, by an entire block. Running your own pool does not improve your luck. It improves your independence. Be honest about which of those you are optimizing for, because the maintenance bill arrives whether or not a block ever does.
Common problems and what they usually mean
Miners connect but show no accepted shares: check that the node is fully synced and that the stratum server can actually reach it. A stratum server pointed at a syncing or misconfigured node will often accept connections and hand out useless work. High stale or rejected share rates: look at latency first, then at whether the node machine is overloaded, especially during initial sync or if it is sharing a drive with other tasks. Miners disconnecting regularly: suspect the local network, particularly Wi-Fi, and move miners to ethernet before blaming the software. Node falling behind the chain tip: check disk space, disk speed, and internet stability, in that order.
Keep a log of what you change. Solo pool troubleshooting has a way of involving three layers at once, and the fix that worked last month is easy to forget. A short note with the date, the symptom, and the fix turns the second occurrence of a problem into a five-minute job instead of another evening of guessing.
My own solo pool is a real example, with one twist: it mines Bitcoin Cash, not Bitcoin. It runs on my Umbrel node using MiningCore, and it has already found a block — block 931655 on December 30, 2025, paying 3.13 BCH at only 4% effort. The fiddliest part of the setup was the payout configuration: the pool's config file carries its own payout address and a small reward-recipient cut, so I had to verify character by character that block rewards actually land in the wallet I mine to. That check is worth doing on any solo pool, because a wrong address there has no undo.
The bottom line
Running your own solo pool at home is a genuinely good project for someone who wants to understand Bitcoin mining past the point of plugging in a machine. It is not a way to earn more, and it is not a shortcut around the lottery math. If you go in knowing that, with a synced node, a maintained stratum server, and realistic expectations, you will learn more about how Bitcoin actually works than most miners ever do. If you need the income, use a regular pool, and keep the solo pool as the project it is.
For the odds in detail, read the solo mining guide and the pool vs. solo comparison.
Before you spend anything, run your numbers through the free Faith Mining ROI calculator with your real hashrate, wattage, and electricity rate.
Check the solo odds first
The solo mining guide works through the expected time to find a block at your hashrate, with current network numbers.
Read the solo mining guide →Want your own numbers? Run them through the Solo Mining Odds Calculator to see your probability of finding a block over a day, week, month, and year at your hashrate.