Solo Mining
Bitcoin Solo Mining Setup Guide for Home Rigs
A Bitcoin solo mining setup guide for home rigs: connect with your own address, check the block payout, and understand the lottery before mining begins.
Your miner needs three things before it starts: a Bitcoin address you control, a network connection, and a pool endpoint. This Bitcoin solo mining setup guide starts there because the rest is secondary. If your rig finds a valid block, the question is not when a dashboard says you were paid. The question is which address appears in that block.
Solo mining is a lottery. Network difficulty sets your odds, and it sets the same odds at every pool. More hashrate shortens the expected wait, but an average is not a schedule. A small home miner can run for a long time without finding a block. That is the normal outcome, not a setup error.
What a Bitcoin solo setup actually does
A solo pool gives your miner candidate work for the current Bitcoin block. Your rig hashes that work and submits shares, which show that it is operating at its assigned difficulty. Almost all shares are not blocks. A block is a rare share that meets Bitcoin's network target.
When a rig finds one, the block reward can be built directly to the Bitcoin address you supplied. That reward includes the block subsidy and transaction fees. There is no balance sitting in a pool account waiting for a withdrawal.
This is why your payout address deserves more attention than the worker label, dashboard theme, or hashrate chart. A mistyped address can turn a successful block into someone else's reward. Check it character by character before you save the configuration.
What you need before connecting
Use a Bitcoin address from a wallet whose recovery phrase and keys you control. Do not use an exchange deposit address. An exchange can change deposit rules, reject unusual deposits, or close access to an account. A self-custody wallet gives you an address you can keep and verify yourself.
Your miner also needs stable internet access. Wi-Fi can work for a small ESP32-class miner if the signal is reliable, although Ethernet is usually easier to diagnose. A dropped connection does not change your underlying chance of a block, but it does stop the rig from receiving current work while it is offline.
Finally, find your miner's web interface. Bitaxe-style devices commonly expose a local configuration page after joining your network. Standard ASICs do the same through their local IP address. Your router's connected-device list can help if you do not know the address.
Keep the miner on a safe circuit and give it airflow. Solo mining does not make a hot power supply less hot. A home miner may be small, but heat, fan noise, and failed USB power adapters remain ordinary hardware problems.
Bitcoin solo mining setup guide: the connection fields
Open your miner's pool configuration page. Add a new pool or replace an unused one. For Bitcoin on NexusPool (nexuspool.io), enter this server address and port:
solo.nexuspool.io:3350
Put your own Bitcoin payout address in the username or worker field. If your firmware supports a worker name after the address, use a short label that helps you identify the machine, such as a room or device name. The payout address is the part that matters for the block reward.
The password field is usually optional for a solo connection. If your firmware requires one, use a simple placeholder rather than a wallet password. Never enter your wallet recovery phrase, private key, or exchange login into mining firmware. A pool has no reason to ask for any of them.
Save the settings and restart the mining process if the firmware does not reconnect on its own. The Bitcoin endpoint accepts Stratum V1 and encrypted Stratum V2 on the same port. Most home hardware currently uses Stratum V1. Select Stratum V2 only when your firmware explicitly supports it and gives you the relevant connection settings.
Do not confuse a server address with a website address. The correct mining endpoint is solo.nexuspool.io:3350. Entering a homepage address into a pool field will not produce work.
Check the connection before leaving the rig alone
A miner can show a hashrate number even when its pool settings are wrong. Wait for the log or status page to show that it connected, received work, and submitted accepted shares. The words vary by firmware, but you are looking for a live connection rather than a saved configuration.
A newly started miner may need several minutes before it submits a share at its assigned difficulty. That delay can be normal, especially on low-hashrate hardware. Do not keep rebooting it every minute. Reboots interrupt hashing and make the log harder to read.
If the miner reports rejected shares, read the reason before changing settings. A stale share means the work was replaced by a newer block before the submission arrived. Invalid work can point to a clock problem, unstable overclock, firmware issue, or hardware error. Authentication failures usually mean the address field, endpoint, or format is wrong.
Check the obvious items in order: your payout address, the port number, the selected protocol, the miner's system clock, and the network connection. Change one thing at a time. Five changes at once create a new mystery.
For a miner far from Los Angeles, Chicago, Frankfurt, and Singapore, network round-trip time can be longer. That affects how quickly work and status updates arrive. It does not change the chance that a given hash finds a block. Distance is a connection issue, not a luck setting.
Check the payout before a block exists
A solo setup should let you inspect the destination before you need it. Payout Preflight shows the payout constructed for your address on the current block. It lets you check where a found block's subsidy and transaction fees would go before your rig finds anything.
Use the exact address from your miner configuration when you run that check. Compare the displayed address against the address in your wallet and against the address saved in the rig. Do not compare only the first and last few characters. Clipboard mistakes are real, and so is malware that replaces copied addresses.
The current block changes often, so the displayed transaction details will change with it. The useful check is the destination: your address is the output that matters. A pool cannot promise when your rig will hit. It can show where the reward lands if it does.
What happens when the network finds a new block
Bitcoin miners must move onto new work after a new network block appears. The pool can prepare work from a block header before its own node finishes validating the block. On the Frankfurt server, the median header-to-work time was 0.49 ms across 162 mainnet blocks on September 10 and 11, 2026. That work arrived 205 ms before validation completed.
There is a limit worth understanding. The first job based on a newly seen header carries no transactions. It gets a miner hashing on the new height quickly. A later job can include the transaction set after validation. This does not alter your chance of a winning hash. It reduces time spent on work for an old block.
A pool also has to handle the rare event that matters most: a valid block submission. For blocks found through Los Angeles, Chicago, or Frankfurt, the block is written to disk first and then sent to Bitcoin nodes in all three cities, with retries for up to five minutes. Singapore sends a found block to its own node. After a restart, a pending block is submitted again.
Those details do not predict a win. They describe what happens after one.
Avoid the common home-miner mistakes
Do not treat pool hashrate as income. It is a measurement of recent work, and short windows are noisy. A fan slowing down, a Wi-Fi dropout, or an aggressive overclock can make the number jump without telling the full story.
Do not point multiple miners at different payout addresses by accident. Decide whether every rig should pay to one wallet address or whether each device needs its own destination. For most home setups, one address is simpler to audit. Label the devices in your own notes so you can tell which physical miner matches each configuration.
Do not assume a lower difficulty setting creates more value. Lower share difficulty can make a low-hashrate device report shares more often, but shares are not block rewards. Network difficulty decides the block target.
If you change firmware, reset a device, or move it to another network, repeat the address check. Configuration backups are useful, but they are not evidence that a payout address is still correct.
Before leaving the miner running, open Payout Preflight and check the address that would receive a block today. That is the check worth doing while the outcome is still under your control.