NerdAxe Solo Mining Setup You Can Verify

A NerdAxe solo mining setup is not complicated because the hardware is small. It is complicated because each field in the web interface represents a claim about where your work goes, who builds a winning block, and where the reward lands. Get those right before chasing hashrate screenshots.

A NerdAxe is a compact Bitcoin ASIC miner built around the same basic proof-of-work race as warehouse-scale equipment. It hashes headers. It submits shares. It might find a valid block. The small size changes your probability, not the rules of Bitcoin.

What You Need Before Powering It On

Start with the physical setup. Put the miner on a hard, open surface with clear airflow around the fan and heatsink. These devices are small, but the ASIC and voltage regulation still produce concentrated heat. Do not place it inside a cabinet, on fabric, or directly against a wall.

Use the power supply specified for your exact NerdAxe model and board revision. Check its voltage, connector polarity, and current rating rather than assuming that a plug that fits is safe. A marginal supply can cause brownouts, restart loops, invalid work, or heat at the connector. If the cable or plug becomes unusually hot, disconnect it and investigate before continuing.

You also need a reliable 2.4 GHz Wi-Fi network unless your particular build supports another network path. Many ESP32-class miners use 2.4 GHz only. A combined 2.4 GHz and 5 GHz SSID may work, but a dedicated 2.4 GHz network can make initial provisioning easier. Keep the miner within reasonable range of the access point. A weak connection does not improve through optimism.

Finally, prepare a Bitcoin address that you control. For solo mining, this is the address that should receive the entire coinbase payout if your miner finds a block through a non-custodial pool. Copy it from your own wallet, then compare the first and last characters before saving it. A typo here is not a cosmetic error.

Bring the NerdAxe Online First

After applying power, give the miner time to boot. Most NerdAxe units running AxeOS expose a local setup portal or can be found through your router's connected-device list. Connect it to Wi-Fi, then open the miner's local web interface using its assigned IP address.

Before entering pool details, look at the dashboard. Confirm that the reported board type, firmware version, temperature readings, fan state, and hashrate are plausible for your model. A miner that cannot hold a stable temperature or repeatedly restarts is not ready for overclocking or pool troubleshooting.

Set a DHCP reservation in your router once the miner is working. That keeps its local IP address stable. It is a small administrative step, but it prevents the familiar problem where the miner is fine and the operator is looking at yesterday's IP address.

Firmware deserves the same caution as any network-connected device that controls hardware. Identify the firmware version you are running and obtain updates only from the project or hardware source you trust. Read release notes when available. Do not flash a binary merely because a chat message says it adds hashrate.

Set Conservative Thermal Limits

A stock configuration is the correct starting point. Let the miner run long enough to establish a baseline for temperature, frequency, voltage, accepted shares, and hardware errors. Ambient room temperature matters. A setting that behaves in a cool workshop can become unstable in a warm room.

If you tune later, make one change at a time. Higher frequency can raise hashrate, but it can also raise power draw, heat, error rates, and fan noise. The reported hashrate is not the only number that matters. A machine producing work that is rejected or unstable is not doing useful work.

Configure Your Solo Pool Connection

In the mining configuration page, you will generally enter a Stratum URL, port, worker name, password, and payout address. The precise field labels vary by firmware. Read the labels and the pool's connection instructions rather than pasting a configuration intended for a different miner or protocol.

For a Bitcoin solo pool, the worker name commonly combines your payout address with a label for the device. A format might resemble bc1...youraddress.worker1, but the required separator and naming convention are pool-specific. The worker label helps you distinguish rigs. It does not replace the payout address.

NexusPool accepts Bitcoin connections at nexuspool.io:3350, which resolves to its Los Angeles point of presence. Its geo-steered endpoint, pool.nexuspool.io:3350, directs connections toward the nearer healthy North American point of presence. Use the endpoint format the pool documents for your firmware, then verify on the miner's status page that it has an active Stratum connection and is submitting accepted shares.

Do not treat a green connection indicator as proof that the payout destination is correct. Check the configured address character by character against your wallet. Then use the pool's preflight or payout-verification tooling, where offered, to validate the payout construction before relying on it. The address in your miner, the address the pool recognizes, and the address encoded in any eventual block reward should agree.

Stratum V1, Stratum V2, and What Your Firmware Actually Uses

Stratum V1 remains common on home-mining hardware. It is widely supported and works with standard ASIC configuration screens. Stratum V2 adds capabilities such as encrypted connections and clearer separation of responsibilities, but support depends on the miner firmware and pool implementation.

Do not select V2 because the label sounds newer. First verify that your installed NerdAxe firmware actually supports native V2 and that you have the correct endpoint and authority-key information if key pinning is required. A V2 pool cannot turn a V1-only firmware image into a V2 client.

The useful question is simple: what protocol is on the wire between your miner and the pool, and can you verify that configuration? If your firmware shows only a conventional Stratum URL and no V2 controls, it is probably using V1. That is not a failure. It is a fact to configure correctly.

Read the Numbers Without Lying to Yourself

Once connected, leave the miner alone for a while. A few minutes is enough to confirm connectivity. It is not enough to judge long-term stability. Watch for accepted shares, rejected shares, stale shares, average hashrate, temperature, and reconnects over several hours and then several days.

Accepted shares show that the pool is receiving work that meets its assigned share target. They are evidence of communication and accounting. They are not evidence that you are close to finding a Bitcoin block. Pool difficulty may adjust per rig so a low-hashrate miner submits shares at a useful cadence without changing its actual chance of finding a block.

Solo mining is high variance by design. Your probability is roughly your share of the network hash rate for each block opportunity. A NerdAxe can run for a very long time without finding a block, even when it is configured perfectly. Another miner can get improbably lucky. Neither outcome proves a configuration is good or bad on its own.

That is why a solo setup should be evaluated in two layers. First, verify operational facts: the miner is stable, shares are accepted, the endpoint is correct, and the payout address is yours. Second, accept the statistical fact: no pool, dashboard, or tuning preset changes the underlying lottery.

Troubleshoot in the Right Order

When a NerdAxe stops submitting shares, begin at the miner, not at the pool. Check power, local temperature, Wi-Fi signal, and the miner's log or status screen. A reboot can restore operation, but it also hides the cause if you never read the error.

If the miner is connected but has no accepted shares, confirm the Stratum host, port, and worker format. If it shows frequent reconnects, look for Wi-Fi drops, router behavior, DNS failures, or an overly aggressive power or frequency setting. If rejected shares rise after tuning, return to the prior stable setting before changing network variables.

Keep a simple record of the configuration that works: firmware version, frequency, voltage if adjustable, pool endpoint, worker label, and normal temperature range. This makes recovery possible after a reset and makes a future change testable instead of memorable only in theory.

A home miner is not a passive appliance. It is a small proof-of-work system attached to your network, power circuit, wallet, and chosen mining infrastructure. Set it up slowly enough to know what each part is doing. Trust nothing. Verify your submitted work and payout address.