Goldshell – NiceHash / Unsupported Pool Algo

Identify your Goldshell model's native algorithm and confirm it has an active NiceHash spot market. KD-series → Kadena (yes). LT-series and Mini-DOGE → Scrypt (yes). ST-BOX → ETCHash, listed on NiceHash as `daggerhashimoto` (yes). HS-BOX/HS5 → Handshake (no NiceHash market — stop here, mine direct). CK-BOX/CK5/CK6 → Eaglesong (no NiceHash market — mine direct on F2Pool's CKB pool). KA-BOX/KA-BOX Pro/AL-BOX II → Kadena (yes).

Get your NiceHash BTC mining address. Log into nicehash.com → Mining → Wallet, copy the BTC mining address (the one labelled `Mining Address`, not the deposit address — they are different). NiceHash authenticates stratum logins by mining address only. Save it to a text file you'll paste from. Validate the address is a real BTC address by pasting into mempool.space — a valid address returns address history (or empty history for a fresh address); a malformed address returns 404.

Open the Goldshell Web UI. Find the miner's IP via `find.goldshell.com` from a browser on the same LAN, or check your router's DHCP table for a hostname starting with `goldshell-`. Default login is `admin` / `123456789` (change immediately if you have not). Navigate Settings → Pool. Ensure you are on Pool 1 (highest priority).

Configure Pool 1 with NiceHash details. Pool URL: `kadena.auto.nicehash.com` (or `scrypt.auto.nicehash.com`, `daggerhashimoto.auto.nicehash.com` — match your algo). Port: `9200` for TLS or `3200` for plain TCP. Worker: paste your NiceHash BTC address, append `.MODELNAME` (e.g. `33xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.KD6-01`). Password: `x`. Click Save. Some Goldshell firmware versions strip `stratum+tcp://` prefixes; others reject them. Use bare hostname in the URL field.

Reboot the miner with a full power cycle (10 seconds off, then on). Goldshell BOX-series firmware caches old pool state in RAM and a soft restart does not always clear it. Within 60 seconds of power-on the dashboard should show Pool: Connected, accepted shares ticking up, LEDs solid green. If LEDs go red+blue, the pool config did not take — re-check the URL field for typos and reboot again.

Test the NiceHash stratum endpoint independently from a laptop on the same network. Linux/macOS: `nc -v kadena.auto.nicehash.com 9200`. Windows PowerShell: `Test-NetConnection kadena.auto.nicehash.com -Port 9200`. The connection should succeed within 2 seconds. If it times out, your network blocks outbound 9200 — try 3200 (plain TCP) or 443 (NiceHash also offers some algos on 443). Some ISPs filter mining-pool ports aggressively.

Pin to a specific NiceHash region. The `auto` hostname routes via anycast to the nearest cluster — usually fine, occasionally wrong. If reject rates are above 5%, manually pin: `kadena.usa.nicehash.com`, `kadena.eu.nicehash.com`, etc. Reduces stale shares from anycast misroutes and gives you a stable endpoint for monitoring latency. Run `ping <regional-host>` and pick the one with the lowest RTT.

Verify NiceHash sees your worker. Log into nicehash.com → Mining → Rigs. Your Goldshell should appear within 5 minutes of connection, named after the worker suffix you set in step 4. If the rig appears as `Unknown` or with no worker suffix, your username field is missing the `.WORKERNAME` part after the BTC address — fix it in Goldshell Pool settings and reboot.

Run a 24-hour profitability sanity check. NiceHash Mining → Profitability calculator: plug in your Goldshell model's hashrate and power draw at your kWh rate. Compare against direct mining (Dxpool/F2Pool for KDA, Litecoinpool for merge-mined LTC+DOGE on Scrypt, F2Pool for ETCHash on ST-BOX) converted to BTC at spot. NiceHash wins on convenience and BTC-only payout. Direct mining usually wins on absolute payout, especially for Scrypt where merge-mining DOGE adds significant value NiceHash does not capture.

Update Goldshell firmware over Ethernet — NEVER WiFi. Goldshell's #1 source of bricked miners is the WiFi-firmware-update path: any packet loss during the transfer corrupts the image and leaves the device in `red+green LED stuck` state requiring SD-card recovery. Hardwire the miner to your switch, download the latest firmware from `goldshell.com/upgrade-firmware/` for your exact model, upload via web UI, wait the full 5-10 minutes without touching anything. Each firmware release tends to expand the supported-pool allow-list and fix stratum-extension quirks.

Deploy a stratum proxy on your LAN to bypass Goldshell's pool allow-list. Install `stratum-mining-proxy` (slush0) or a similar open-source proxy on a Raspberry Pi. Configure it to listen on `0.0.0.0:3333` and forward to `kadena.auto.nicehash.com:9200`. Point the Goldshell at `<pi-ip>:3333` — Goldshell sees a `normal` pool on the local network, the proxy translates and forwards to NiceHash. Solves the allow-list issue, gives you packet-level logs, and lets you swap upstream pools without touching the Goldshell UI.

For ST-BOX on NiceHash ETC: enable EthProxy stratum mode if your firmware exposes the toggle. ST-BOX speaks stratum-eth (EthProxy variant) on `daggerhashimoto.auto.nicehash.com`. Some firmware versions need explicit `mining.subscribe` parameters to negotiate EthProxy correctly — check the firmware release notes. If shares submit but reject rate is >15%, swap to a NiceHash regional endpoint or run through a stratum proxy that normalizes the protocol exchange.

Configure failover pools. Goldshell supports Pool 1 / Pool 2 / Pool 3 with priority-based fallback. Set Pool 1 = NiceHash, Pool 2 = direct-coin pool (Dxpool/Litecoinpool/F2Pool with the native coin address), Pool 3 = a second NiceHash regional endpoint. If NiceHash drops or your account locks, the miner keeps earning. Goldshell falls back automatically when Pool 1 fails three reconnect attempts.

Lock down the Goldshell against the documented pool-hijack botware. Internet-exposed Goldshells with default `admin/123456789` credentials get scanned and silently re-pointed at attacker-controlled stratum URLs. After moving to NiceHash: change the admin password, disable port forwarding to the miner, place it on an isolated VLAN with outbound-only internet, monitor the Pool config field weekly for unauthorized changes. Sovereignty starts at the firewall.

Stop DIY and escalate. If algo has a confirmed NiceHash market, BTC address validates on mempool.space, `nc` reaches the stratum endpoint, latest firmware is installed over Ethernet, and a stratum proxy on a Raspberry Pi also fails to bridge auth — open a D-Central support ticket at https://d-central.tech/contact/ with logs from the proxy and screenshots of the Goldshell Pool settings. Escalate to bench repair only if diagnosis uncovers a hashboard or control-board fault (LT5/KD6/CK6 commonly mask hardware issues as `pool connection` symptoms).