Before you calculate
Use this calculator after you already know the miner model, control board family, current firmware state, and the package you plan to run. The result is a planning estimate, not approval to push a firmware or pool change across a production fleet.
Keep pilot miners representative: include the oldest board type, the newest board type, and at least one miner from any rack or subnet that often behaves differently during scans.
Batch wave planner
How to use the result
- If the pilot fails, stop. Do not count the remaining waves as planned work.
- If a batch produces mixed results, shrink the next wave and review compatibility notes.
- Observation time should include pool connection, hashrate, temperature, and alert checks.
- Use the rollout checklist to record package version, operator, target list, and rollback path.
Next step after the estimate
Turn the wave count into a written rollout record. The record should name the operator, target miners, expected action, package version, start time, observation window, rollback path, and the condition that stops the rollout. For firmware-related work, keep the first successful wave under observation before starting the next one.