Solo Miners
What Beginner Solo Miners Need to Know First
Beginner solo miners need a payout address, an endpoint, and realistic expectations. Learn what your rig does, where a found block pays, and what to check.
A small miner does not need an account, a dashboard balance, or a promise about returns. It needs a Bitcoin address, a working connection, and a clear answer to one question: if this rig finds a block, where does the money go? For beginner solo miners, that answer matters more than a pool's graphics or a list of recent winners.
Solo mining is a lottery. Your rig submits work continuously, but a valid block is rare. Network difficulty sets the odds for a given hashrate. Those odds are the same at every pool. A lower network difficulty means a shorter expected wait. It does not mean a block becomes worth more, and an average wait is not a schedule.
That can sound severe because it is. A home miner may run for a long time without finding a block. It can also find one tomorrow. The useful question is not whether anyone can predict the date. They cannot. The useful question is whether you can inspect the route from your rig's work to your own address before that rare event happens.
Connect the miner before you tune it
Start with the connection details your firmware requests. For Bitcoin solo mining at NexusPool (nexuspool.io), point the rig to solo.nexuspool.io:3350 and use a valid Bitcoin payout address. There is no account, sign-up gate, or KYC step.
The endpoint steers a miner to a nearby healthy Bitcoin region. The pool operates complete Bitcoin regions in Los Angeles, Chicago, Frankfurt, and Singapore. Each has its own Bitcoin node. Geographic distance can add round-trip time, so a miner far from those locations will see updates later than a miner nearby. Distance does not change the odds of finding a block.
Most home devices still use Stratum V1. The same port also accepts encrypted Stratum V2. That matters when a device supports V2, but it is not a reason to replace a working V1 miner. Choose the connection method your firmware supports, save the configuration, and confirm that the device begins reporting accepted work.
Do this before changing clocks, fan profiles, or power limits. A miner that looks busy is not necessarily sending valid work to the endpoint you intended. Its local hashrate display describes what the machine thinks it is doing. Accepted shares show that the pool can read work the machine sends.
What a solo miner is actually doing
Your rig receives a block template and tries different hashes against the network target. Most attempts do not meet the target. A share is a lower-difficulty result that lets the pool and rig check that the miner is working as expected. A network-valid block is the rare result that meets Bitcoin's current target.
Shares are not payments in solo mining. They are operational evidence. A found block is the event that matters.
The pool's job begins after your hardware has done its hash work. It must provide fresh work when Bitcoin has a new block. It must read a submitted share as the firmware wrote it. If the share is rejected, the reason should be visible rather than folded into a vague error count. If a winning share arrives, the pool must construct and submit the block without placing its own wallet between the block reward and your address.
That path cannot create luck. It can only avoid losing the luck your machine already had.
A short interruption also needs context. Home miners restart after power changes, Wi-Fi issues, or a quick firmware adjustment. Some difficulty systems react badly when a rig goes quiet for a few minutes, then make the first minutes after reconnecting harder to interpret. NexusPool holds a rig's difficulty through a brief quiet period. That does not alter the chance of a block. It avoids treating a short pause as a new miner with unknown speed.
Where the reward goes when you find a block
A Bitcoin block has two relevant reward parts: the block subsidy and the transaction fees. On a solo setup, the reward should be committed in the block itself to the payout address you supplied.
That is different from waiting for a pool ledger to calculate a balance and send a later payout. A block can be inspected on-chain. Its coinbase transaction shows where the reward was assigned. If your address is there, the subsidy and transaction fees belong to that address subject to Bitcoin's normal maturity rules.
NexusPool uses a 0% pool fee for Bitcoin solo mining. When a rig finds a block through the pool, the whole reward goes to the miner's own Bitcoin address in that block.
Check the payout construction before mining, not after a lucky event. Payout Preflight shows the payout built for your address on the current block. It gives you something concrete to inspect: the destination and the amount represented by the current block's subsidy and fees.
There is one limit worth understanding. Transaction fees change as transactions enter and leave the mempool, and a future block is not the current block. Preflight shows the construction for the current block. It is not a forecast of the exact fees in a block found later.
Beginner solo miners should watch the right numbers
A device interface can show temperature, fan speed, local hashrate, pool-side hashrate, accepted shares, rejected shares, and network difficulty. They do not all answer the same question.
Temperature and fan speed tell you whether the hardware needs attention. Local hashrate tells you what the miner estimates it is producing. Accepted shares tell you whether work is reaching the pool and being read successfully. Rejected shares need a reason. Network difficulty provides the scale for the lottery you entered.
Do not treat a short hashrate window as a verdict on a small miner. A few minutes of noisy readings are normal. A longer pattern of missing accepted shares, repeated connection failures, or hardware errors deserves investigation.
Start with the plain checks. Confirm the payout address character by character. Confirm the endpoint and port. Check that the firmware's clock is sensible. Check power and cooling. If the miner is on Wi-Fi, test whether the connection drops under normal household use. Then look at the rejection reason rather than assuming every rejection is an internet problem.
An invalid address cannot be fixed after a block is found. A typo is more urgent than a modest temperature improvement.
Fresh work matters, but it does not need mythology
When another miner finds a Bitcoin block, everyone needs to work on the next one. Hashing on the old tip after learning about the new block cannot produce the next valid block. The time between a new block arriving and a miner receiving new work is therefore worth measuring.
There is a trade-off at the start of a new block. A pool can prepare an initial job from the new block header before its node finishes validating the prior block. That first job carries no transactions. Later work can include transactions after validation and template construction complete.
For home miners, the practical point is simple: the rig should receive new work promptly, and you should be able to distinguish a normal work change from a connection problem. Do not confuse this with better odds. Fresh work protects time your hardware could otherwise spend on an old block. It does not change the network target.
If your rig finds a block
The event is rare enough that the submission path should be boring. A found block through Los Angeles, Chicago, or Frankfurt is written to disk first, then sent to Bitcoin nodes in all three cities. Each submission is retried 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 describe handling after the find. They are not a guarantee that a candidate block is valid or that Bitcoin will accept it. A block must still meet the network target and follow Bitcoin's consensus rules. If it does, the record to inspect is the block itself and its coinbase payout.
You do not need to sit awake watching for that event. You do need to retain control of the private keys for the address you entered. A pool can direct a block reward to an address. It cannot recover coins from an address whose keys you lost.
A sensible first week
Run one stable configuration before experimenting. Give the miner enough time to establish a pattern of accepted work. Record its power setting, estimated hashrate, temperature, and connection behavior. Change one variable at a time.
Avoid turning the exercise into a return calculation. Electricity use is real. Hardware wear is real. A found block is not regular income. If the device is too loud, too hot, or too expensive to run for your household, no pool setting changes that fact.
The better first goal is operational: know that your miner is connected, know which address it is using, and know how you would verify a found block. Before you let the rig run unattended, check the payout built for your address on the current block. Trust nothing. Verify your payout destination.