How to Point a Bitaxe at Bitmern Solo (AxeOS Setup)

How to Point a Bitaxe at Bitmern Solo (AxeOS Setup)

Bitaxe owners usually want one thing from pool setup: open AxeOS, enter three fields, and see accepted shares without fighting firmware jargon meant for rack ASICs.

In AxeOS, set Stratum URL to the coin host plus VarDiff port (BTC: stratum+tcp://btc.bitmernsolo.com:3132), Username to YOUR_WALLET.worker1, Password to x, then confirm shares on Bitmern Solo and in AxeOS.

This guide is AxeOS-only. It does not replace the full multi-ASIC stratum walkthrough - for Antminer, Whatsminer, Braiins, and the complete ten-coin port table, use How to Connect Your ASIC to Bitmern Solo. Here you get the Bitaxe path: why solo fits a home board, what each AxeOS field means, exact BTC settings, a high-level coin switch, how to verify workers, and the fails that actually show up on Wi‑Fi hardware (including the 2.4 GHz gotcha).

Bitmern Solo is solo infrastructure: flat 1% fee, you keep 99% of blocks you find. Fee detail lives in Bitmern Solo Fees Explained - this post only wires the miner.

Why point a Bitaxe at Bitmern Solo

A Bitaxe is small hashrate by farm standards, but it still speaks stratum like any other SHA-256 (or supported-algo) miner. Solo economics fit that profile when you can absorb variance: you are not chasing fractional drip payouts; you are pointing hashrate so that if your work finds a block, nearly the whole reward is yours.

What Bitmern Solo adds for a home Bitaxe:

• A stable stratum endpoint so you are not self-hosting Miningcore
• VarDiff ports sized so smaller boards can get first accepts (BTC easy-start is :3132)
• Dashboard workers, shares, and alerts without building ops tooling
• The same wallet.worker username pattern as larger ASICs - one mental model if you grow the fleet later

If you need predictable cash flow every week, shared pools may still fit better. For the payout-model comparison (certainty vs upside), see Solo Mining vs Pool Mining. This article assumes you already chose solo and only need AxeOS filled in correctly.

Before you open pool settings: create a Bitmern Solo account, register a receive wallet for the coin you will mine, and confirm the Bitaxe is on the network and AxeOS loads in a browser. No KYC. One account covers all supported coins.

AxeOS fields - what each one is

AxeOS pool (or stratum) screens vary slightly by firmware build, but the three values Bitmern Solo needs are always the same. Map them once; ignore extra slots until Pool 1 works.

Stratum URL / Pool URL

Full form:

stratum+tcp://HOST:PORT

• Host is the coin hostname (btc.bitmernsolo.com, bch.bitmernsolo.com, and so on).
• Port is a VarDiff port for that coin. Lower starting-difficulty ports are easier for Bitaxe-class hashrate to land first accepts.
• Paste the full string into the primary pool field. Do not split host and port into unrelated boxes unless AxeOS forces separate fields - then host and port must still match the same coin.

For BTC, the locked easy-start URL is:

stratum+tcp://btc.bitmernsolo.com:3132

Never treat :3102 as the default for a Bitaxe on Bitmern Solo. Other BTC VarDiff ports exist for larger hashrate once you are stable; start on :3132.

Username

Format:

YOUR_WALLET.worker1

Rules that matter on Bitaxe as much as on a rack:

• Wallet must be a valid address for that coin, and should match the wallet you registered on Bitmern Solo for that coin.
• Worker label is yours (bitaxe1, desk-ultra, shelf-a). Use letters, numbers, and hyphens.
• One dot between wallet and worker - not an underscore, not a space, not a second address.
• Example shape only (replace with your real address): bc1qexamplewalletaddresshere.bitaxe1

Password

Set to exactly:

x

Bitmern Solo does not use a custom pool password. Blank fields, exchange passwords, or long random strings are unnecessary and can trip firmwares that expect a non-empty password. Use x.

Save / apply / reboot

Apply the config. Give the board a minute or two to reconnect. Watch AxeOS for accepted shares before you assume the Bitmern Solo dashboard is wrong.

BTC example - exact AxeOS settings

Use this as a copy checklist for Bitcoin on a Bitaxe in AxeOS.

AxeOS field Value Stratum / Pool URL stratum+tcp://btc.bitmernsolo.com:3132 Username YOUR_BTC_WALLET.worker1 Password x

Walkthrough:

1. Open AxeOS in your browser (usual path: Bitaxe LAN IP).
2. Go to pool / stratum settings for the primary pool.
3. Paste stratum+tcp://btc.bitmernsolo.com:3132 as the pool URL.
4. Set username to your BTC receive address, a single dot, then a short worker name.
5. Set password to x.
6. Save and apply (reboot if your build requires it).
7. Leave secondary pool slots empty until primary shows accepts.

That is the whole BTC connect. Fee on finds remains flat 1% (fees post); connection plumbing for other ASIC brands is in the connect-ASIC guide.

Switch coin (high-level)

AxeOS does not need a different “mode” for each coin beyond algo support on the board and a new stratum host:port. Keep username format and password x. Change only the URL to the coin you want.

Easy-start ports you are most likely to use from a Bitaxe context (verify live on bitmernsolo.com if anything moved):

Coin Recommended stratum URL BTC stratum+tcp://btc.bitmernsolo.com:3132 BCH stratum+tcp://bch.bitmernsolo.com:13123 LTC stratum+tcp://ltc.bitmernsolo.com:13052 DOGE stratum+tcp://doge.bitmernsolo.com:13053 DGB stratum+tcp://dgb.bitmernsolo.com:4052

Algo must match hardware. SHA-256 Bitaxe builds belong on BTC / BCH / DGB (and related SHA-256 coins), not on Scrypt or RandomX endpoints. For the full ten-coin table, alternate VarDiff ports, and non-Bitaxe UIs, use the connect-ASIC post - this page stays on the AxeOS path and the ports above.

When you switch coins: register that coin’s wallet on your Bitmern Solo account, put that address in the username, and point at that coin’s host:port. Do not reuse a BTC bech32 address on an LTC stratum line.

Verify - shares and worker showing

Success is two places agreeing, not one.

In AxeOS

After apply:

• Pool status shows connected (wording varies by build).
• Accepted share count increases.
• Rejected / stale stays low once stable.

If AxeOS never shows accepts, fix local config and Wi‑Fi before debugging the dashboard.

On Bitmern Solo

Log in and open the miner / workers view for that coin.

You should see:

• Worker - the suffix after the dot (worker1, bitaxe1, …)
• Hashrate - may take a short window to settle; do not invent targets here
• Shares - accepted counts moving
• Effort - coin effort updating as shares land

If AxeOS shows accepts but the dashboard is empty: wait a few minutes, refresh, then re-check that the wallet prefix on the miner matches the wallet registered on the account for that coin. A one-character typo creates a “working” Bitaxe that never maps to your login.

Turn on email alerts after the first clean connect so offline workers and hashrate drops page you later - not during the first save/reboot cycle.

Common fails (Bitaxe / AxeOS)

Wi‑Fi is 5 GHz only (or the board never joins)

Symptom: AxeOS unreachable, stratum timeouts, or the Bitaxe never appears on the LAN after power-on.

Fix: Bitaxe-class boards typically need 2.4 GHz Wi‑Fi. A 5 GHz-only SSID, client isolation, or a guest network that blocks device-to-device access will strand the miner. Put the Bitaxe on a 2.4 GHz SSID (or a mixed AP with 2.4 enabled), confirm you can open AxeOS from a phone or laptop on the same LAN, then set stratum. This is the most common home-setup fail and has nothing to do with Bitmern Solo ports.

Wrong port (especially BTC :3102 as “default”)

Symptom: disconnect loops, no accepts, or stubborn rejects after a clean-looking URL.

Fix: For BTC start on :3132. Do not default to :3102. Copy host and port together from the table; never mix a BTC host with an LTC/DOGE port.

Username format wrong

Symptom: auth errors, missing worker labels, or shares that never appear under your account.

Fix: WALLET.workerName with a single dot. No spaces. Worker label simple. Wallet must match the coin and the address on your Bitmern Solo account.

Password not x

Symptom: auth failure on builds that require a non-empty password.

Fix: password exactly x. Not blank. Not your exchange password.

Stale secondary pool still primary

Symptom: hashrate still landing on an old pool; Bitmern Solo idle.

Fix: Bitmern Solo on Pool 1 (or only enabled pool). Clear leftover URLs. Save and reboot so AxeOS is not bound to cached settings.

Algo / coin mismatch

Symptom: hashing locally with zero useful accepts.

Fix: only point at coins your Bitaxe firmware and chip can hash. Wrong algo never becomes right because the URL looks tidy.

Soft next step

When AxeOS shows accepts and Bitmern Solo lists your worker with moving shares, Bitaxe setup is done. Add another board the same way: same host and easy-start port for that coin, new worker suffix, password x, and keep the Bitaxe on 2.4 GHz Wi‑Fi.

For other ASIC brands and the full port matrix, use Connect your ASIC to Bitmern Solo. For the flat 1% / keep 99% receipt model, use Bitmern Solo fees.

Start mining

Create an account, register your coin wallet, and point AxeOS at Bitmern Solo.

Start Mining → https://www.bitmernsolo.com/

---