From KD-Box
to XBT-Box.

Check compatibility, install over SSH, then manage your miner from its local browser console.

1. Check your hardware

Use a stable power supply and reliable Ethernet connection. Save your existing pool/network settings and keep the appropriate stock firmware/recovery resources before making changes.

2. Make sure SSH is available

The installer needs root SSH before it can begin. The older original KD-Box Goldshell SSH-enabled legacy firmware is the SSH prerequisite referenced for this conversion. Goldshell’s official GitHub hosts the original KD-Box firmware.

Goldshell KD-Box legacy SSH-enabled firmware on GitHub ↗ · Firmware download section

1. Confirm the label and current web interface identify the original KD-Box.
2. If SSH already works and the installer’s compatibility check passes, you do not need to flash solely for its label.
3. If SSH is unavailable, obtain the exact original KD-Box legacy SSH-enabled firmware .cpb from Goldshell. Use the stock Goldshell firmware-update interface only if it accepts that model/version. Keep power on and allow the update/reboot to finish.
4. Find the miner’s current IP again and verify SSH. If the stock interface refuses a downgrade or signature, stop; request the correct model recovery procedure instead of forcing another model’s firmware.

legacy SSH-enabled firmware does not make every controller compatible. The XBT-Box installer’s runtime checks still apply. Goldshell firmware and XBT-Box are separate downloads: never upload the XBT-Box installer into Goldshell’s firmware field.

ssh root@MINER_IP

Replace MINER_IP with your actual LAN address. Use the miner’s SSH password, which can differ from its web password. Check the SSH fingerprint on a trusted LAN before proceeding.

3. Install from Windows

1. Download XBT-Box Installer. You do not need Python or a separate OpenSSH installation for the graphical installer.
2. Run the Windows x64 installer. It is an unsigned executable; verify that you obtained it from ACMECrypto and compare its SHA-256 with the downloads page.
3. Enter the miner IPv4 address manually and check the prefilled SSH password against your device. It does not change the miner’s root password. The installer remembers it using Windows DPAPI account protection.
4. Optional: select the correct local adapter and choose Scan subnet, then select your miner. Nothing scans automatically on launch. Find Goldshell opens Goldshell’s discovery page. A discovery match alone does not prove model compatibility.
5. Leave the verified reboot option selected for normal installation. Click Install. The app verifies the model/runtime and uploaded package, installs, checks the console, and reboots only after success.
6. Keep the miner powered. Open console becomes available as soon as the new UI is verified, while restart/reboot checks may still be running. Read the phase message and allow several minutes for pool connectivity, chip telemetry and the saved profile to settle. After reconnection, click Open console or open http://MINER-IP:8080.

First-seen SSH host keys are accepted and saved by the installer. An unexpected change to a previously saved key is refused. Verify the device independently before changing its trust record. The installer saves the SSH password encrypted with Windows DPAPI for your current Windows account; it is not saved as plaintext or passed on the command line.

The console uses port 8080. Stock Goldshell’s port 80 service remains unchanged. Do not forward either management port or SSH to the public Internet.

4. First login and first shares

1. Log in to the fresh console with admin / 123456789. Go to System → Administrator password and change it. An upgrade preserves your existing console password.
2. Open Miner → Pool settings. Fresh installs contain a supplied pool/worker profile and autostart is enabled. Replace the worker with your own wallet/worker; do not assume the prefilled address pays you.
3. Set your pool’s exact Stratum URL, worker and password. Add fallback pools if desired. Save draft does not change active mining; use Save & Apply pools to activate.
4. Check Home for a healthy miner, fresh hashrate and increasing accepted shares. Confirm work is credited to your worker on the pool’s own status page.
5. Watch fans and temperatures while the device settles. The reference default is 715 GH/s at 220 W; results vary.

Existing custom pools, tuning, thermal settings and console passwords are preserved on upgrade. Installation explicitly enables mining autostart, including a previously idle setup; existing safety locks remain enforced.

5. Daily controls and features

Home: monitor the miner

See current/average hashrate, accepted/rejected shares, hardware errors, chip average and chip maximum, both fan RPM readings, board status and up to one hour of history. Observed average high/low values reset with a new miner process or console restart; they are not a separate minimum-chip sensor.

Miner: pools and tuning

Use up to three pools in failover order. The the current release default clock profile is 750 MHz. Supported trial settings span 500–850 MHz in 10 MHz increments and 50–100% shared fan PWM. Voltage is displayed read-only; this build does not implement a working hardware voltage adjustment.

Make one change at a time, then watch pool shares, hardware errors and temperature. Hot tuning stops mining, keeps fans at full speed and cools before a guarded restart. Missing stopped-miner telemetry triggers a cooling wait; startup still needs fresh temperature checks. A fan fault or safety timeout leaves mining stopped.

Temperature protection

Defaults are Safe 76°C / Max 82°C, with reboot on Max enabled. Warnings begin within 2°C of Max. The independent watchdog continues with the browser closed. A temperature trip retains a safety lock; a reboot does not simply erase it. Correct cooling/power/fan problems before acknowledging a lock. Acknowledgement leaves mining stopped and disables autostart.

Start, stop and autostart

Start and Restart enable mining autostart. Stop mining leaves both mining engines idle with fans at 100% and stays effective across normal reboots. Start mining again only when ready. Pool/network delays are retried during enabled startup.

Estimated power

The console’s power reading is modeled, not measured onboard. Default references are 220 W mining and 10 W idle. Use a wall meter under Miner → Power estimation to calibrate. The default 220 W reference corresponds to about 5.28 kWh per day of continuous operation; it is not a profit estimate.

Network settings

Under System, choose DHCP or static IPv4 and DNS. Automatic DHCP DNS uses lease-provided servers, falling back to 1.1.1.1 and 8.8.8.8 when absent; static automatic DNS uses that fallback pair. Manual DNS remains under your control. Applying can disconnect the console and mining. Reconnect at the new address and choose Keep settings within 120 seconds; otherwise it restores the previous configuration. Do not apply network changes from Goldshell and Miner OS at the same time.

Locate miner

Under System → Locate miner, blink the supported system/status LED for 15 seconds to identify the unit. Mining and fan settings stay unchanged; the previous LED state is restored. If no unique supported LED interface exists, the app reports that limitation.

Diagnostics and support

Developer details offers read-only RPC and log views. Download a redacted diagnostic bundle, inspect it yourself, and send only the relevant redacted error to support. Local alerts are included; automatic SMTP and SNMP delivery are not available in this release.

Developer fee

A fixed, disclosed 2% of eligible mining time supports Miner OS development. The System page shows collection status. This is separate from any fee charged by your selected pool.

Complete feature reference

This inventory covers the features included in the current release. See the protection table below for limits and stop conditions.

Overclocking and underclocking

The default XBT profile is 750 MHz, with a reference performance of 715 GH/s at 220 W. “Overclock” here means above that default XBT profile; the inspected stock KD-Box profile was 850 MHz. A higher selectable clock is not a promise of higher accepted hashrate or safe operation on every unit.

1. Open Miner and confirm healthy fans, fresh telemetry and stable pool shares.
2. Choose a clock and fan setting, then use Save & Restart tuning. Change one setting at a time so you can compare results.
3. If temperature is above Safe or telemetry is missing, the app stops mining and holds full fans for cooling before restarting. With no post-stop samples, it waits at least 30 seconds; the restarted miner still needs fresh Safe-temperature checks.
4. Startup checks both fans, lowers an observed clock above 500 MHz to 500 MHz, verifies it, waits for a fresh chip average at or below Safe, then restores and verifies the saved clock.
5. Wait through the settling check and compare pool-accepted rate, temperature and hardware errors. If stability worsens, return to the default or a lower profile.

No per-change clock step limit is imposed while the miner is at or below Safe; the 10 MHz setting increments and 500–850 MHz bounds still apply. Tuning settings do not establish voltage control. Power estimates may stop being valid after fan or voltage-profile changes; recalibrate with a wall meter.

Safety mechanisms and their limits

These are software protections that depend on a functioning controller, sensors and fans. They do not replace sound cooling, a suitable power supply or hardware thermal protection. Treat a tripped safety lock as a fault to investigate, not a prompt to raise the limit.

6. Update or return to stock control

Run the newer installer against the same miner to upgrade. Preserve your settings and review the result before leaving it mining. Unknown or incompatible private runtimes are refused rather than overwritten.

To stop the conversion and resume stock services, use System → Mining services → Return to stock control and confirm. This disables converted-miner autostart; stock services may resume KDA mining. It does not uninstall all overlay files, flash firmware, or restore a previous firmware version.

Troubleshooting

Still stuck? Contact support →