Planning matrix
Area
What to confirm
Why it matters
S19 / S21 family
Exact model suffix, control board, current stock firmware date, and whether the target action is scan, pool edit, or Braiins OS install.
Newer stock firmware and board variants can change what a local tool can safely do.
S17 family
Board type, recovery route, and whether SD-card workflow is safer than a network batch workflow.
Older machines often need more recovery planning before firmware actions.
S9 family
Legacy workflow expectations, SD-card availability, and whether the unit is production-critical.
Legacy support does not mean every action should be automated.
Pool configuration
Pool URL, worker naming convention, password field, and whether a rollback pool profile exists.
Wrong pool changes can silently move revenue or break monitoring.
Cooling and tuning
Toolbox version, Braiins OS version, model support, and temperature policy.
Thermal changes need observation windows, not just successful command execution.
Preflight checks
- Record model, serial, rack, IP, board family, current firmware, and current pool settings.
- Download only from the release page and verify download before running the tool.
- Test discovery and read-only status checks before any write action.
- Use a small pilot group before rack-level or subnet-level operations.
- Keep a documented rollback path for firmware and pool configuration changes.
Related pages
Supported miners guide
General support boundaries and caveat language.
Open guideRollout checklist
Turn the matrix into a phased deployment plan.
Plan rolloutTroubleshooting
Use when scan, login, compatibility, or firmware steps fail.
Fix issues