One pool connection. Every BitAxe in your fleet working as one miner.
Open-source ESP32-S3 firmware — a cluster-aware fork of ESP-Miner — that turns multiple BitAxe-family solo miners into a coordinated master/slave swarm: zero duplicate work, one unified dashboard, remote tuning across the whole fleet.
v1.0.0 formerly released as ClusterAxe — firmware still reports/ships as clusteraxe-* for OTA compatibility, see note below.
01 What is ZombieOS?
Standalone BitAxe firmware (stock ESP-Miner) is great at mining — alone. ZombieOS adds the layer that's missing once you have more than one.
One master, up to 8 slaves
The master owns the single Stratum connection to your pool, splits work so no two devices ever hash the same range, and aggregates every slave's shares into one cluster total — up to 9 BitAxe units per cluster.
Wireless or wired
ESP-NOW wireless by default — sub-5ms latency, ~200m range, no cabling. Or BAP over RS-485 daisy-chain for ~1200m range and industrial-grade reliability, up to 16 devices.
Built on ESP-Miner, not from scratch
ZombieOS is a fork of the standard open-source BitAxe firmware — every single-device feature you already know still works. Clustering, the tuner, and the dashboard are layered on top.
02 Supported hardware
Pre-built binaries exist today for two boards. Never cross them — 601 and 801 use different voltage domains.
Gamma601
The standard single-chip BitAxe Gamma board. Runs as standalone, master, or slave.
GammaTurbo (GT801)
The dual-chip Gamma Turbo board. Same three roles — standalone, master, or slave.
Known issue: the GT801 master role currently misreports its own local hashrate as 0 H/s in the UI — cluster-wide totals and slave devices are unaffected, this is a display bug on the master's own tile only. Not yet root-caused.
03 What ZombieOS has that standalone firmware doesn't
Beyond clustering itself, running ZombieOS gets every device — even a single standalone unit — a better tuner and a sturdier UI than stock.
Cluster-exclusive
Zero duplicate work
Per-slave extranonce2 partitioning gives every device its own slice of the search space — no two units ever hash the same range.
Coinbase ring buffer
Each slave keeps 8 fresh, deduplicated coinbases in rotation instead of restarting the ASIC on every ~1s pool rebroadcast — meaningfully more real work per second.
Unified cluster dashboard
Per-slave accepted/rejected shares + reject %, nonce range, MAC address, last-seen/last-work timestamps, plus a master summary: power, J/TH efficiency, jobs sent.
Real remote control
Per-slave restart and identify, and config pushed over ESP-NOW even when a slave has no LAN IP at all — not a silent no-op like some wireless-only setups.
Board-aware safety
Each slave's undervolt/overheat thresholds are derived from its own reported voltage rail — a 12V GT801 master won't false-throttle a 5V Gamma601 slave.
Every device, including standalone
Board-aware tuner/benchmark
Power budget auto-scales to the detected ASIC count (real 50W/60W oc on the 2-chip GT801 vs 25W/30W on Gamma601), with live hashrate/temp/power/HW-error telemetry.
Overclock benchmarks that don't cook the chip
Polls temperature every 3s during a run and backs off before the firmware's own overheat cutoff — instead of finding out the hard way.
Settings survive power loss
Best-known-good tuner settings persist to NVS mid-run and across reboots — no 35-50 minute recalibration unless you explicitly ask for one.
Embedded web UI
The UI is compiled directly into the firmware binary — no separate www.bin to flash or lose track of.
Best-shares scoreboard + live WebSocket telemetry
Top-20 best shares, a Block Header card (nonce/diff/version/ntime of your last find), and a live "chance to find a block %" stat.
04 Downloads — ZombieOS v1.0.0
Pick the file for your exact board and role. Full flashing steps (including esptool offsets) are in FLASHING.md on GitHub.
Gamma601
GammaTurbo (GT801)
First time flashing from stock AxeOS? Rename your chosen file to esp-miner.bin and upload it in AxeOS → Firmware Update. There is no www.bin — the UI is built into the firmware itself.
zombieos-… names. The device itself already reports ZombieOS-v1.0.0 on its screen, in the web UI, and at /api/system/info.