DCENT_Toolbox — Open Source Miner Management

DCENT_Toolbox is a local tool, not a compatibility guarantee. Every operation must resolve to an exact miner, control board, incumbent firmware, command, evidence level and recovery route.

Safe starting point

# Install from a source checkout until the PyPI package is published.
git clone https://github.com/DCentralTech/DCENT_Toolbox.git
cd DCENT_Toolbox
python -m pip install -e .
dcent discover
dcent audit <MINER_IP>
dcent diagnose <MINER_IP>

Confirm the current CLI help and repository documentation for the installed version. Discovery or audit is read-only evidence; it does not establish flashing support.

Capability and evidence matrix

Operation	General status	Required gate
Discovery and identification	Designed across multiple adapters	Verify the model/control-board result against physical hardware.
Diagnostics and evidence export	Read-oriented capability	Record the Toolbox version, adapter, command and raw output.
Configuration	Firmware– and command-specific	Preview the exact diff and keep a rollback path.
Backup/recovery assistance	Platform-specific orchestration	Prove the recovered image and restore route on the actual unit.
Firmware installation	Not universal	A named model + control-board + incumbent-firmware route must be validated. A generic install command is not permission to flash.

DCENT_OS relationship

Toolbox can parse and verify DCENT_OS package metadata and is intended to orchestrate guarded operations. Today, the S9 XIL artifact still lacks a published witnessed current-artifact install/boot/soak/recovery capstone, and the S19j Pro XIL artifact lacks a validated first-install route from vendor stock. Therefore this page does not call Toolbox “the install path” for those artifacts.

Evidence before mutation

1. Identify the exact unit and control board.
2. Capture the incumbent firmware/version and hardware health.
3. Run a dry plan and inspect every persistent write.
4. Back up and prove recovery.
5. Open the exact firmware/model release record.
6. Stop if the route is lab-gated, unproven or absent.

Source and reporting

Read the GPL-3.0 source repository. Report the Toolbox version, platform adapter, exact command, miner/control board, incumbent firmware and raw output. Never generalize one successful adapter/command combination to an entire platform family.

FAQ

Does Toolbox support every miner?

No. It contains multiple adapters and operations, each with its own evidence. “Detected” does not mean “safe to configure,” and “package parsed” does not mean “safe to install.”

Can Toolbox install DCENT_OS now?

Only a future exact route promoted by the canonical evidence ledger should be described as validated. Current S9 XIL and S19j Pro XIL artifacts remain guarded.

DCENT_Toolbox documentation

Six task-focused pages. Read them in order the first time: install, then a read-only pass, then check whether a route to your exact hardware actually exists before anything mutating.

• Install & first command — Python 3.9+ and a source checkout on Windows, macOS or Linux — then the read-only dcent doctor <ip>.
• Command reference — The ~75 top-level dcent commands grouped by discovery, read-only diagnostics, config, install and recovery — each tagged read-only or mutating.
• Supported miners, firmwares & boards — 4 vendor backends, 6 firmwares and 7 control-board families from the S9 to the S21, with honest confidence levels.
• Discover, audit & diagnose — The read-only pass: neighbour-first LAN discovery, then build a miner evidence profile before anything mutating.
• Install DCENT_OS with Toolbox — The honest routes: only the Antminer S9 has a public network-write path today; S17/S19/S21 stay lab-gated.
• FAQ — 0% dev fee, no cloud, GPL-3.0 — which miners are covered, and which install routes really exist.