Skip to content

We're upgrading our operations to serve you better. Orders ship as usual from Laval, QC. Questions? Contact us

Bitcoin accepted at checkout  |  Ships from Laval, QC, Canada  |  Expert support since 2016

SOLO_ADDR_MISMATCH Critical

Solo Wallet Address Mismatch — Block Reward Lost

Solo-pool block reward paid to a Bitcoin address you cannot spend from. Address-authenticated solo pools (CKPool, Public Pool, Ocean, `solo.d-central.tech`) build candidate-block coinbase outputs that pay directly to the on-chain address in the Stratum User field. If the address is wrong-network (testnet/signet pasted into mainnet), format-mismatched against pool policy (segwit/Taproot to CKPool's legacy-only handler), generated from a seed you've lost, or owned by an inaccessible exchange account, the post-2024-halving 3.125 BTC + fees reward is unrecoverable the moment the block confirms.

Critical — Immediate action required

Affected Models: Every solo miner pointed at an address-authenticated pool: Bitaxe (Supra, Ultra, Gamma, GT, Hex, Max), NerdMiner, NerdAxe, NerdQAxe, NerdQAxe++, NerdNOS, PiAxe, StealthMiner, NerdOctaxe; full ASICs (Antminer, Whatsminer, Avalon) running solo to ckpool/Public Pool/Ocean/`solo.d-central.tech`.

Symptoms

  • Stratum User field contains an address you cannot currently sign for from any wallet (lost seed, dead device, abandoned wallet app, closed exchange account)
  • Address starts with `m...`, `n...`, `2...`, `tb1q...`, `tb1p...`, or `bcrt1...` — testnet/signet/regtest prefix pasted into a mainnet pool
  • Address copied from a paper wallet generated years ago with no record of the seed phrase
  • Address from an old hardware wallet (Trezor One, Ledger Nano S original, KeepKey) where the seed backup is misplaced or unreadable
  • Address belongs to an exchange account that has since been closed, frozen, or KYC-locked
  • Address contains a single-character typo that happened to land on a different valid checksum (rare but documented; Base58Check 32-bit checksum, bech32 30-bit checksum)
  • You have never sent a tiny test deposit to the address to verify your wallet can sign for it
  • You have no record of which wallet, device, or seed produced the address
  • Configured against CKPool (`solo.ckpool.org`) but pasted a `bc1q...` segwit or `bc1p...` Taproot — CKPool requires legacy `1...` P2PKH
  • Configured against Ocean (`mine.ocean.xyz`) but pasted a non-Taproot address — Ocean's TIDES/DATUM payouts mandate Taproot `bc1p...`
  • AxeOS / pool dashboard shows your worker username diverging from the address you actually configured (silent rewrite, MITM on the web UI, or pool-side bug)
  • Post-block-found: AxeOS log shows `mining.notify` immediately followed by your hashed share matching block target, but mempool.space shows the coinbase paid to an address you don't own

Step-by-Step Fix

1

Pre-flight: pick the right pool for your address format. CKPool requires legacy `1...` P2PKH. Ocean mandates Taproot `bc1p...` for TIDES/DATUM payouts. Public Pool and `solo.d-central.tech` accept all four valid mainnet formats. Decide which pool first, then generate an address in a format that pool accepts — don't let a wallet's default format dictate your pool choice.

2

Generate the address in a self-custody wallet whose seed you control and have backed up offline. Sparrow Wallet (sparrowwallet.com), Electrum (electrum.org), Coldcard (coldcard.com) + Sparrow, or Jade (blockstream.com/jade) + Sparrow are the proven setups. Write the seed words on paper, store in a fireproof location, and verify the seed restores cleanly to a second device before connecting the wallet to any miner.

3

Validate the candidate address on two independent block explorers. Paste into mempool.space — it should load an address page (zero balance is fine for an unused address). Cross-check on blockstream.info. Both loading address pages = real, valid mainnet on-chain address. Either explorer 404ing or kicking you to a testnet suggestion = malformed string or wrong-network prefix; do not proceed, regenerate.

4

Send a `2,000 sats` test deposit (~$1 USD) from any wallet you currently control to the candidate address. Wait for one confirmation on mempool.space. Now open the wallet you BELIEVE owns the address — confirm the 2,000 sats appears in its balance. If they appear, your seed is intact and you can sign for spends from that address. If they don't, your wallet has lost the address or the seed is corrupted; stop and resolve before mining another share.

5

Save the verified miner config to a plaintext file on your workstation: Stratum URL, port, the verified address, originating wallet name, and where the seed is stored offline. If you ever reflash, factory-reset, or swap miners, copy-paste from this file — never retype. Eliminates Unicode-paste surprises and accidental field clears after firmware updates.

6

Hardening: use a hardware wallet for the receiving address. Coldcard Mk4 (~$220 CAD), Blockstream Jade (~$120), Trezor Safe 3 (~$160), or DIY SeedSigner (~$60-90 in parts). The address is generated on a device whose private keys never touch your computer. If your laptop is compromised, the receive address is still safe. If a block is found, the sats appear at an address only the hardware wallet can sign for. Highest-ROI custody decision in Bitcoin, conditional on actually winning a block.

7

Generate a unique receive address per miner so you can audit which device's potential block reward goes to which output. Address derivation is deterministic from the seed — every address resolves back to the same backed-up phrase, no redundancy lost. Sparrow exposes a clean address-list view; Electrum has it via Receive → Used / Unused. Helps with bookkeeping and post-block forensics if anything ever goes wrong.

8

Run the seed-restore drill annually. Once a year (calendar-tie it to smoke-detector battery changes), take the seed backup off the shelf, type the words into a fresh device — air-gapped if possible (SeedSigner or Krux signers are ideal) — confirm the master fingerprint and first 5 receive addresses match your records. Wipe and re-store the device. Detects backup degradation (faded ink, missing words, transcription errors) before it costs you a block.

9

Disable the miner's WAN access except to the pool itself. A compromised AxeOS / NerdMiner / NerdAxe web UI exposed to the internet is an attack vector for silent Stratum-User swaps to an attacker's address. Firewall the miner to LAN-only or VPN-only at your router, and verify the Stratum User field hasn't changed every time you touch the miner — especially after firmware updates, since some updates have factory-reset behaviors that wipe user-supplied addresses.

10

Do not mine to exchange addresses (Coinbase, Kraken, Binance, Bitbuy, NDAX, Shakepay). They are valid on-chain addresses but you don't hold the keys. Account closures, KYC re-verification holds, AML flags on mining-source deposits, jurisdictional withdrawal restrictions, and outright exchange insolvency (Mt Gox / FTX / Celsius / Voyager / BlockFi) have all locked mining payouts in the wild. Self-custody (Sparrow + hardware wallet) is the only configuration that respects solo mining's sovereignty premise.

11

Post-mismatch recovery (low success rate; do them anyway). If the block was found in the last hour, contact the pool admin immediately. CKPool: Con (`@ckolivas`) on Libera IRC `#ckpool`. Public Pool: `benjamin-wilson` on GitHub. Ocean: ocean.xyz/contact. Provide block height, configured Stratum User address, intended address, proof of seed/wallet ownership of the intended address. Most admins won't unwind a confirmed coinbase, but if the block hasn't propagated a re-template is technically possible. Cost is one polite message; expected success is near-zero but not strictly zero.

12

If the wrong address belongs to an exchange you can no longer access, contact the exchange's compliance team with the block height, txid, and proof-of-mining. Some exchanges have a manual-review path for unexpected mining deposits to closed accounts. Most don't. Document the disposition in writing. For some users a tax-loss filing in your jurisdiction is the only practical outcome; consult an accountant familiar with crypto-mining tax treatment.

13

If the seed is lost, exhaust every recovery path before declaring the loss permanent. Search photo libraries (you may have photographed the seed at backup time and forgotten), email drafts, encrypted notes apps, password managers, old cloud backups, hard drives from previous laptops. Run partial-seed brute force via `btcrecover` (github.com/btcrecover/btcrecover) if you remember some words or the BIP-39 passphrase pattern. Not every lost seed is permanently lost — some are merely misfiled. Spend the days; the asymmetry against the stake is unforgiving.

14

Document the loss for the community. If you've lost a block reward to an address mismatch, write up the case (anonymized if you want) and post it where the next pleb miner will see it: r/Bitaxe, r/BitcoinMining, the Bitaxe Discord, the D-Central blog. Lessons paid in BTC should be paid forward — every pleb who reads your post is one fewer who has to learn it the same way. D-Central's editorial position: we'll publish anonymized post-mortems on the blog if you want a wider audience.

15

Tier 4 — D-Central pre-flight review (free with any D-Central-purchased miner). Book a 15-minute slot at d-central.tech/contact/. We verify (a) address format matches your chosen pool's policy (CKPool legacy / Ocean Taproot / Public Pool flexible / D-Central segwit-friendly), (b) wallet seed restores cleanly on a fresh device, (c) mempool.space and blockstream.info both resolve the address, (d) firewall posture is locked down enough that an attacker can't silently swap the Stratum User. Free is the right price for the asymmetry against a 3.125 BTC + fees disaster.

16

Tier 4 — post-disaster forensics. If the block has already been found and the address was wrong, open a D-Central support ticket at d-central.tech/contact/ with block height, transaction id, configured Stratum User address, intended address, pool name, AxeOS firmware version, and any pool-dashboard screenshots. We can't recover the BTC — nobody can after coinbase confirmation. We CAN help you (a) confirm whether the pool admin has any recovery path, (b) document the loss for tax purposes, (c) advise on jurisdictional remedies if the loss involves an exchange, (d) harden your next configuration. We've seen every variation; we save you weeks of re-discovering each cul-de-sac.

When to Seek Professional Repair

If the steps above do not resolve the issue, or if you are not comfortable performing these repairs yourself, professional service is recommended. Attempting advanced repairs without proper equipment can cause further damage.

Related Error Codes

Still Having Issues?

Our team of Bitcoin Mining Hackers has been repairing ASIC miners since 2016. We have seen it all and fixed it all. Get a professional diagnosis.