Wrong Coin Endpoint on Bitmern Solo (Host/Port Mismatch)

Wrong Coin Endpoint on Bitmern Solo (Host/Port Mismatch)

The miner is hashing. Firmware looks “connected.” Yet the matching coin tab stays empty, another coin tab shows a ghost worker, or shares never land where you expect — because the host/port points at coin A while the username wallet belongs to coin B (or you are watching the wrong coin tab).

If your Bitaxe or home ASIC is pointed at a Bitmern Solo host/port for one coin while the username wallet (or the dashboard tab you watch) belongs to another, run an ordered mismatch checklist: lock the per-coin host, use BTC easy-start btc.bitmernsolo.com:3132 (never treat :3102 as the Bitaxe / home default), set username to WALLET.worker with a wallet that matches that coin, password x, open the matching coin tab, then prove first accepts. This post does not invent a full host table beyond the known per-coin pattern, and Current Effort is not a find guarantee.

This is the wrong-coin-endpoint lane. Switching coins on purpose: switch coins on Bitmern Solo. Wallet shape rejected: invalid wallet rejects. Host/port/scheme typos: stratum URL mistakes. Tab vs worker attribution: coin tabs explained. Field wiring: connect ASIC.

Bitmern Solo is solo infrastructure: flat 1% fee on finds only, you keep 99%. Fee context stays light here — the job is lining host, port, wallet, and tab to the same coin.

Endpoint mismatch ≠ switch-coins ≠ invalid wallet ≠ URL typos ≠ coin tabs

Five patterns get mixed up:

1. Wrong coin endpoint — stratum host/port for coin A; username wallet (or watched tab) for coin B. That is this post.
2. Intentional coin switch — you meant to move the board to another coin and need the full switch path. Use switch coins.
3. Invalid wallet rejects — wallet prefix does not match a valid registered receive address for the coin you are on. Use invalid wallet rejects.
4. Stratum URL mistakes — wrong scheme, typos, or port shape on an otherwise same-coin string. Use stratum URL mistakes.
5. Wrong coin tab — string is consistent; you are staring at the wrong tab. Use coin tabs explained.

Do not invent a Bitmern Solo “cross-coin error code” table, a guaranteed first-accept SLA, or a claim that Current Effort predicts a find. Product facts that matter: per-coin hosts (for BTC, btc.bitmernsolo.com), BTC easy-start :3132, username WALLET.worker with wallet matching that coin, password x.

What usually looks like “mining the wrong coin”

Common mismatch desks on Bitaxe-class and small ASIC setups:

1. LTC (or other) wallet on BTC host — username starts with an LTC-style receive prefix while host is btc.bitmernsolo.com:3132.
2. BTC wallet on a non-BTC host — BTC receive address on another coin’s per-coin host.
3. Correct host, wrong port family for that coin — leftover :3102 or a foreign pool port still in the primary slot while you assume Bitmern Solo BTC easy-start.
4. Failover slot still on another coin — primary looks clean; board flaps onto a secondary pointed at a different coin’s host.
5. Dashboard tab ≠ miner coin — string is BTC; you watch LTC (or the reverse) and conclude “no workers.”
6. Copied string from a friend on another coin — host/port pasted wholesale; wallet left as yours for a different coin.
7. Coin switched in firmware UI but stratum fields not re-saved — display label says one coin; stratum still points at another.

Separate these from a clean same-coin string that still fails wallet validation (invalid wallet rejects) or a typo on an otherwise matching coin (stratum URL mistakes).

Ordered mismatch checklist

Run top to bottom. Stop when the matching coin tab shows the worker under the expected label, fresh accepts move, and firmware is no longer pointed at a cross-coin host/wallet mix.

1. Name the coin you intend — then lock one host

Symptom: You are unsure which coin the board is supposed to mine right now.

Action: Pick one coin. For BTC easy-start, the host is:

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

Other coins use their matching per-coin hosts on the same Bitmern Solo pattern — do not invent extra hosts here. Never treat :3102 as the Bitaxe / home default.

2. Match the wallet prefix to that same coin

Symptom: Username wallet looks “valid” in the abstract but belongs to a different coin than the host.

Fix: Username must be WALLET.worker where WALLET is a registered receive address for the same coin as the host. Password stays x. If the prefix is wrong for that coin, leave this post and use invalid wallet rejects.

3. Confirm password is literally x

Symptom: Password holds a wallet unlock, exchange PIN, or blank while you chase “wrong coin.”

Fix:

x

No quotes. No spaces. Auth is not wallet security theater. Password detail: stratum password x if that lane is the real story.

4. Open the matching coin tab before you blame the endpoint

Symptom: You watch coin B while the board points at coin A and conclude “endpoint broken.”

Fix: Open the same coin the miner is pointed at. A BTC-pointed board will not populate an LTC worker card. Tab reading: coin tabs explained.

5. Clear cross-coin leftovers from failover slots

Symptom: Primary is BTC; secondary still has another coin’s host/port or a foreign pool string; board flaps and attribution looks random.

Fix: Put Bitmern Solo for your chosen coin on the primary (or only) pool slot. Clear or disable failover slots that still carry another coin’s endpoint. Save and apply.

6. Re-save and power-cycle after the string change

Symptom: You fixed host/wallet but firmware still shows the old connect line.

Fix: Save pool settings, reboot the board (or full power-cycle), and watch logs for a new connect to the intended per-coin host — not a stale line from the mismatch string.

7. Separate mismatch from intentional switch

Symptom: You meant to move the whole board to another coin, not just fix a typo.

Fix: Use the full path in switch coins on Bitmern Solo. This post is for accidental host/wallet/tab mismatch, not a planned migration.

8. Separate mismatch from URL typos on the same coin

Symptom: Host coin and wallet coin already match; scheme/port/typo is the only issue.

Fix: Use stratum URL mistakes.

9. Prove first accepts on the matching coin tab

Open the matching coin tab. Confirm:

• Worker row present under the expected WALLET.worker label
• Fresh accepts moving (not stuck empty)
• Hashrate reading believable while the board hashes
• Current Effort leaving a stuck empty reading when attribution works

Card reading stays in the dashboard guide. Current Effort is an ops signal — not a find guarantee.

10. Soft fee reminder only after work lands

Fee reminder only if you need it: flat 1% on finds; you keep 99%. A matched coin endpoint is an ops signal, not a fee.

When switch-coins, invalid wallet, URL mistakes, or tabs is the real story

If you are intentionally moving coins, use switch coins. If the wallet prefix is invalid for the coin you are on, use invalid wallet rejects. If host/port/scheme is wrong on an otherwise same-coin string, use stratum URL mistakes. If attribution is a tab-reading problem, use coin tabs explained. First-time fields: connect ASIC.

What this post will not invent

• No full invented multi-coin host spreadsheet beyond the known per-coin pattern (btc.bitmernsolo.com for BTC, matching hosts for other coins)
• No claim that :3102 is the home Bitaxe default (easy-start is :3132)
• No “first accept within N seconds” guarantee after a matched string
• No luck formulas, dollar EV, or find-time promises from Current Effort
• No competitor fee comparisons

Fee reminder: flat 1% on finds; you keep 99%. Matching host + wallet + tab is stratum hygiene, not a luck product.

Quick retest sequence after fixing a mismatch

After you align host, wallet, and tab to one coin, do not stare at a stale firmware line forever. Use a short retest loop:

1. Save the stratum string again (BTC easy-start still btc.bitmernsolo.com:3132, WALLET.worker for that coin, password x).
2. Reboot or power-cycle the board so it opens a new connect to the intended host.
3. Open the matching coin tab — not a neighbor tab.
4. Wait for the worker row + first accepts — not for a luck promise or a Current Effort “guarantee.”

If the wallet prefix is wrong for that coin, leave this post and use invalid wallet rejects. If you meant a full coin change, use switch coins.

Soft next step

Lock one coin’s per-coin host (BTC easy-start btc.bitmernsolo.com:3132), set WALLET.worker with a wallet for that same coin, password x, clear cross-coin failover leftovers, then confirm first accepts on the matching coin tab before you chase deeper share or hardware issues.

Start mining

Start Mining — after login, open the matching coin tab and confirm workers / shares / hashrate.

FAQ

Can I point a Bitaxe at BTC host with an LTC wallet?

No — that is the mismatch this post fixes. Host, wallet, and watched tab must be the same coin. Username is WALLET.worker with a wallet registered for that coin; password x.

What BTC port should a home Bitaxe use first?

:3132 on btc.bitmernsolo.com. Never treat :3102 as the Bitaxe / home default.

What username and password does Bitmern Solo expect?

Username WALLET.worker (wallet prefix must match the registered receive wallet for that coin). Password exactly x.

Does Current Effort mean I am about to find a block?

No. Current Effort is an ops / attribution signal on the dashboard — not a find guarantee. See the dashboard guide.

Where do intentional coin switches fit?

If you meant to move the board to another coin, use switch coins on Bitmern Solo — not only this mismatch checklist.

Where do invalid wallet rejects fit?

If host and tab already match the coin but the wallet prefix is wrong or unregistered, use invalid wallet rejects.

Where do I confirm the fix on Bitmern Solo?

Matching coin tab → worker row → fresh accepts → believable hashrate. Guide: dashboard workers / shares / effort.