Run a miner worker
Choose the MDK miner worker guide for your hardware.
Overview
MDK drives each miner brand through its own worker. These guides are task-focused and independent — you only need the one for the hardware you operate.
If ORK, worker, manager, or thing are unfamiliar, read terminology first.
Pick your hardware
The authoritative model list for every worker is the generated supported-hardware catalogue. For example, you may:
Prerequisites
Every guide assumes:
- Node.js >=24 (LTS)
- npm 10.x or newer
- Commands are run from the repo root
- Outbound network access for ORK discovery
For the mock/development path:
- No physical miner is required
- The runnable example for your model starts the bundled mock device and registers it
Each runnable example starts an ORK whose control plane is peer-to-peer over a Hyperswarm DHT. Without outbound network access, startup will stall while the ORK tries to reach DHT bootstrap nodes. See how workers connect for the ORK/DHT mechanics.
For the deployment path:
- A Node.js service or script in your deployment that runs the MDK worker and registers devices
- A supported miner reachable from the machine or container running the worker
- Access to the miner's native API and credentials, if that API requires them
- The worker's
USAGE.mdfor the exactregisterThingoptions
Next steps
- Browse supported hardware
- New to the moving parts? Read terminology (ORK, worker, manager, thing, mock)
- If an example does not start or a mock port is busy, use troubleshooting
- Drive the registered device from the CLI or dashboard — Get started