Deployment sequence
Preflight
Record package version, download result, OS, operator, miner list, pool settings, and compatibility notes.
Pilot
Run read-only discovery first, then test the target write action on one or a few non-critical miners.
Rack wave
Apply to one rack or subnet only after the pilot has stable telemetry and pool connection.
Scale
Continue in batches sized for the team’s monitoring capacity, not just network speed.
Audit fields to keep
Download record
Package URL, version, download date, workstation OS, and operator.
Compatibility record
Model, board, current firmware, intended action, known caveats, and rollback route.
Batch record
Batch size, miner IDs, start time, end time, failures, and manual interventions.
Observation record
Pool connection, hashrate, temperature, fan behavior, rejected shares, and alerts.
Rollback gates
- Do not start a batch if the rollback package or pool profile is unknown.
- Pause rollout if one pilot miner loses pool connection or disappears from monitoring.
- Pause rollout if temperature or fan behavior changes outside the expected range.
- Pause rollout if operators cannot identify whether a failure is network, firmware, credentials, or tool usage.