Stratum Protocol Mining Guide for Home ASICs

Your home ASIC does not mine Bitcoin by simply connecting to Wi-Fi. It needs a clear line of communication to a mining pool, and that line is usually Stratum. This Stratum protocol mining guide explains what happens between your Bitaxe, NerdQaxe, NerdQX, NerdOctaxe, or Avalon Nano and the pool - and how to configure it without guesswork.

For a compact miner running quietly on a desk, shelf, or home office network, Stratum is the practical link that turns hash rate into valid work. Get the pool address, port, wallet settings, and worker format right, and your miner can begin submitting shares within minutes. Get one character wrong, and it may show hash rate locally while earning nothing remotely.

What Stratum does for a Bitcoin miner

Stratum is a lightweight protocol used by mining pools and miners to exchange work. The pool sends your device a block template and a mining job. Your ASIC hashes that job as fast as it can, looking for results that meet the assigned target. When it finds one, it submits a share back to the pool through Stratum.

A share is proof that your miner is doing useful work. It is not usually a Bitcoin block. Pool difficulty is set low enough that miners can submit shares regularly, allowing the pool to measure each worker's contribution. A valid block is far rarer. In solo mining, that rare event is the entire point: your miner could independently find a block and claim the block reward plus fees, but there is no predictable schedule.

That distinction matters for hobby miners. A steady stream of accepted shares means the connection is working. It does not mean you are close to finding a block. With solo mining, every valid hash is another independent chance, while the outcome remains highly variable.

The Stratum connection details you need

Most home ASIC dashboards ask for three core values: a pool URL, a port, and credentials. The labels vary by firmware, but the information is the same.

The pool URL tells the miner where to connect. It often looks like `stratum+tcp://pool.example.com` or may be entered as a hostname without the prefix. The port tells it which service endpoint to use. Pools can provide multiple ports for different miner sizes, connection types, or regions.

Your username is commonly a Bitcoin payout address, sometimes followed by a worker name. For example, a pool may expect a format like `bc1...youraddress.worker1`. Other pools use a registered account name, subaccount, or a pool-specific identifier. The password field is often optional or used for simple worker settings. Do not assume that a password protects your wallet - on many pools, it does not.

Use the exact connection format supplied by your chosen pool. Do not borrow an example from another pool's setup page. A pool URL can look nearly identical while requiring a different username structure or port.

Picking the right endpoint

For most Canadian home miners, the nearest available pool server is usually the sensible starting point. Lower latency can reduce stale shares, although a compact ASIC has modest bandwidth needs and does not require a special network connection.

If your pool offers a standard Stratum TCP endpoint and a secure TLS endpoint, check whether your firmware supports the secure option before selecting it. TLS can protect the connection from local network observation or tampering, but older or lightweight firmware builds may only support standard TCP. Compatibility comes first. A reliable TCP connection is better than a secure endpoint your miner cannot maintain.

Some pools also offer Stratum V2. It is a newer protocol design with improvements around efficiency, security, and job negotiation. Support is still dependent on the pool and the miner firmware. Many home ASICs continue to use classic Stratum V1 without issue, so do not treat V2 as a mandatory upgrade unless both ends explicitly support it.

How to configure Stratum on a home ASIC

Start by connecting the miner to your local network and opening its web dashboard. The exact menu may be called Pools, Mining, Stratum, or Settings. Before changing anything, record the current configuration or take a screenshot. That makes it easy to return to a known working setup.

Enter the primary pool URL and port exactly as provided. Then enter your wallet address or pool account in the worker field. If worker names are supported, add a simple label such as `office-bitaxe` or `desk-miner`. Clear names make it much easier to identify a device later when you have more than one miner online.

Save the configuration, then restart the mining process if the dashboard does not do it automatically. Within a few minutes, look for a successful pool connection and accepted shares. The pool dashboard may take longer to display your worker, especially when a low-hashrate device needs time to submit enough shares for reporting.

Set up a backup pool as well. A secondary endpoint gives the miner somewhere to work if your primary pool has maintenance, a routing issue, or an outage. For solo miners, the backup can be another endpoint from the same service or a second solo pool, depending on your preference. The key is that the backup credentials must also be valid.

Avoid changing pool settings repeatedly while waiting for results. Every restart interrupts hashing and makes troubleshooting harder. Make one change, wait long enough to see connection logs and shares, then move to the next possibility.

Reading accepted, rejected, and stale shares

The status page tells a better story than the raw hash rate number alone. A miner can report its expected speed while having no usable connection to the pool.

Accepted shares are the signal you want. They confirm the pool received and credited valid work from your miner. A small number of rejected shares is not automatically alarming, but a consistently high rejection rate deserves attention.

Rejected shares can come from an unstable overclock, excessive heat, a poor power supply, firmware issues, or an incorrect clock and voltage setting. If you have recently tuned your Bitaxe or other open-source ASIC for more performance, return it to a stable profile before blaming the pool connection. More TH/s is only useful when the miner can submit valid work consistently.

Stale shares arrive too late for the current job. They can be caused by network latency, Wi-Fi dropouts, pool server distance, or a router that is struggling under load. One occasional stale share is normal. A pattern of them points to the connection. If possible, use reliable Wi-Fi close to the access point or a wired Ethernet connection where the hardware supports it.

Wallet details are not a minor setting

A wallet address typo can direct a potential payout to an address you do not control. Copy and paste your Bitcoin address directly from your wallet, then compare the first and last several characters before saving. Never use an address from a screenshot, a chat message, or an old note without verifying it.

For solo mining, understand the pool's coinbase payout process before you start. Some pools require a Bitcoin address in the worker name. Others require an account setup step. Some support payout thresholds for pooled mining, while a solo pool may only pay when your miner finds a block. These are operational differences, not minor details.

Your pool password should also be unique if the service uses one for account access. Enable available account security features, and keep your miner dashboard password separate from your pool account password. Your home ASIC may be small, but the wallet attached to it deserves the same care as the rest of your Bitcoin setup.

Common Stratum problems and practical fixes

When a miner will not connect, start with the simplest checks. Confirm that the device has an IP address and internet access. Check that the pool hostname, port, and worker format match the pool's current instructions. A missing character in a wallet address or an extra space at the end of a field is enough to stop mining.

If the dashboard says connected but shows no accepted shares, give it time based on the miner's hash rate and the pool's share difficulty. Tiny miners may not submit shares as frequently as a large industrial ASIC. Check the local logs for messages such as authorization failed, socket closed, reconnecting, or job not found. Those messages narrow the problem much faster than changing settings at random.

If the miner repeatedly reconnects, test your home network first. Rebooting a router can help, but also check for weak Wi-Fi signal, power-saving settings, DNS issues, or a network firewall blocking the assigned port. Switching to a pool's alternate port can help when a network provider or router configuration interferes with the default one.

Temperature and power are part of connection reliability too. An overheated miner may throttle, crash, or submit invalid work. Use the correct power supply, keep airflow clear, and monitor chip temperature after any overclock. Quiet home mining works best when the hardware is treated like electronics, not like an appliance you can forget behind a cabinet.

A better way to think about pool setup

Stratum is not the exciting part of solo mining, but it is the part that makes every hash count. Once it is configured properly, it should fade into the background: the miner stays online, shares are accepted, temperatures remain sensible, and your wallet information is correct.

That is the goal for a home setup. Plug in, start hashing, then check the dashboard with enough understanding to spot a real issue before it costs you days of uptime. A clean Stratum connection will not change the odds of finding a block, but it makes sure your miner is actually taking every chance it has.