Solo Block Discovery Guide for Home Miners

A solo miner does not need an account, a balance, or a payout schedule to begin. It needs a valid Bitcoin address, a Stratum endpoint, and hardware that can submit valid work. If the miner finds a valid block, the block reward belongs at the address the miner supplied. That is the point of solo mining.

This solo block discovery guide covers the part that matters before you connect: what your miner is actually doing, what a pool can and cannot prove, and how to set a connection up without confusing shares with blocks.

Start with the fact that decides your odds

A Bitcoin block is hard to find by design. Your chance of finding one depends on your hashrate relative to the network hashrate and the current network difficulty. A pool cannot change that underlying probability.

Solo mining has high variance. A small home miner may run for a long time without finding a block. That outcome is normal. A valid block can also arrive on any hash attempt. That outcome is possible, not promised.

Do not treat submitted shares as partial Bitcoin rewards. In a solo arrangement, shares are evidence that your miner is working against assigned jobs. They are also useful for connection statistics and diagnostics. A share is not a block unless it meets the Bitcoin network target.

This distinction prevents a common mistake. A dashboard can show accepted shares, a stable hashrate estimate, and a long uptime while your block count remains unchanged. The work is real. The block-level result is still governed by probability.

Choose a payout address before connecting

Your payout address is not a username with a payment system attached. It is the destination for a coinbase transaction if your miner finds a valid block. Write it down. Verify every character. Use an address you control.

For a home miner, the simplest setup usually looks like this:

1. Set the pool URL and port in your miner.
2. Enter your Bitcoin payout address as the worker name or username field.
3. Add an optional worker label if the endpoint supports one.
4. Leave the password field empty or use the documented placeholder.
5. Save the configuration and confirm that shares receive accepted responses.

The exact field names vary by firmware. A Bitaxe interface may label them differently from an ASIC control panel. The meaning does not change. The payout address must reach the pool exactly as you entered it.

An optional worker label helps you identify a specific rig. Use a label that tells you something useful, such as garage-bitaxe or rack-03. It does not change ownership of a found block. The payout address does that.

NexusPool accepts Stratum V1 and native encrypted Stratum V2 on the same port. That matters for home hardware because many ESP32-class miners and standard ASICs still use Stratum V1. You can connect the hardware you have now without pretending it speaks a protocol it does not support.

What to check after the miner starts

A green status light is not enough. Check the information that can expose a bad configuration or a bad assumption.

First, confirm that the miner is receiving jobs. A miner that has no jobs cannot produce shares. Next, confirm that submitted shares are accepted. A rejection reason matters. “Low difficulty” can mean the share did not meet the assigned target. “Stale” can mean the miner submitted work after the job changed. An explicit reason is better than a red counter with no explanation.

Then confirm the payout address shown by the service. This is the address a reward would use if you find a block. Check it against the address in your wallet, character for character. A worker label is not a substitute for this check.

Finally, watch hashrate over enough time to separate signal from noise. A five-minute reading is a short sample. Small miners produce noisy estimates because share timing is random. Look for a sustained result near the capability of your hardware, while accounting for frequency settings, heat, power limits, and rejected shares.

A closer pool region can reduce round-trip time for job updates and share responses. NexusPool operates complete regions in Los Angeles, Chicago, Frankfurt, and Singapore. Lower latency can reduce stale work in some conditions. It does not change your probability of finding a Bitcoin block. Your hashrate and network difficulty still set that probability.

A solo block discovery guide to verification

Mining infrastructure should not ask you to accept invisible behavior. The useful question is not whether a pool says it is non-custodial. The useful question is what you can inspect before a block is ever found.

Start with the reward path. A solo pool should show the address that would receive a found block. The coinbase output is the relevant fact. If the reward first lands in an operator-controlled wallet, you have introduced a payment promise between your work and your coins. That may be a deliberate choice in another setup. It is not direct payment.

Next, check whether the pool can account for your submitted work without turning that accounting into a custody claim. NexusPool signs an hourly custody receipt for every address from which it counts shares. The receipt is a cryptographic statement about the address and the covered data. The pool publishes the exact bytes that each signature covers. A signature only proves what those bytes say and that the corresponding key signed them. It does not prove facts outside that stated scope.

That limit matters. Cryptography is not decoration. A signature is useful when you know the public key, the exact message, and the claim being made. If one of those pieces is missing, you are back to taking a statement on faith.

For Stratum V2, encryption has a separate purpose. Native encrypted Stratum V2 uses Noise-based session encryption and authority-key pinning. Pinning lets a miner recognize the authority key it expects. Encryption protects the connection against passive observation and some active interference. It does not make an invalid payout address valid, and it does not improve block-finding odds.

Know what happens when a block is found

A block template contains more than a target and a header. It also includes a coinbase transaction, which creates the block subsidy and collects transaction fees. In a direct-to-miner design, the coinbase transaction specifies the miner’s payout address before the block is submitted.

A valid block is not useful until it reaches the Bitcoin network. Submission is an operational problem with a short time window. A pool should have a defined process for recording the found block and relaying it to nodes. NexusPool writes a found block to its own journal on disk before submission, then submits it to Bitcoin nodes across multiple regions with automatic retries.

This does not guarantee that every submitted block becomes part of the active chain. Bitcoin can produce competing valid blocks near the same time. A block can be stale if another valid block reaches the network first. That is a network event, not a fee category and not a reason to invent certainty where none exists.

If a block is accepted into the chain, its coinbase output is subject to Bitcoin’s maturity rule. Coinbase funds cannot be spent immediately. Your wallet will show the transaction according to its own indexing and confirmation behavior. The chain is the source of truth.

Keep the setup simple enough to audit

The best home-mining configuration is usually boring. Use a wallet you control. Use a label you can recognize. Save a copy of the endpoint and address outside the miner interface. Check the displayed destination after every firmware reset or configuration change.

Do not paste an address from an untrusted chat message or screenshot. Do not assume a browser extension, clipboard manager, or remote management panel preserved the address. Compare the beginning, middle, and end at minimum. A full character-by-character check is better when you first configure a device.

If your miner begins rejecting shares, start with the plain causes. Check the endpoint, port, clock behavior, firmware logs, internet stability, temperature, and frequency settings. A rejected-share reason narrows the search. It is operational evidence, not a moral judgment about your miner.

Solo mining is an honest lottery with real work behind every ticket. The hardware hashes. The pool assigns work and relays valid blocks. Bitcoin decides whether any given hash meets the network target. Keep ownership direct, keep each claim scoped, and verify the path your reward would take before you need it.

Trust nothing. Verify your block path.