1. Scan
Scan the expected IP range and compare results with your rack, switch, or DHCP records.
How to Manage ASIC Miners with BTC Tools
A controlled BTC Tools workflow for discovering ASIC miners, reviewing status, selecting devices and validating batch changes.
Workflow
Mistakes to avoid
A clean ASIC management workflow starts with discovery and ends with review. The goal is to change only the devices you intend to change.
2. Group
Select a small group by rack, subnet, room, or maintenance window before applying any batch action.
3. Configure
Prepare pool URLs, worker naming, and backup pools before updating selected miners.
4. Review
Check reachability and pool-side worker activity after changes are applied.
Checklist
Confirm the working inventory before a change
Use the checklist to record the current state, intended devices and rollback values before selecting a batch.
- Changing a full farm before testing a small group.
- Using worker names that do not map back to physical devices.
- Mixing DHCP leases and static IP plans without records.
- Ignoring model or firmware differences.
- Treating pool-side hashrate and local miner status as the same data source.
- Running a maintenance pass without recording the starting pool values.
- Updating mixed firmware groups as if every device behaves the same.
- Skipping a post-change review in the pool dashboard.
Operations
Step-by-step workflow
The table separates each step from its acceptance check so an operator can stop when the observed result differs from the plan.
| Area | What to check | BTC Tools workflow |
|---|---|---|
| Prepare | Collect IP range, credentials, pool URLs, and naming plan. | Keep the maintenance scope clear. |
| Scan | Find miners on the local network. | Confirm expected and unexpected devices. |
| Reconcile | Compare scan results with rack, switch, or DHCP records. | Catch stale labels before applying changes. |
| Select | Choose a limited group. | Reduce accidental fleet-wide changes. |
| Apply | Update settings for selected miners. | Watch for timeouts and firmware-specific behavior. |
| Review | Check status and pool activity. | Document results for the next maintenance pass. |
| Roll forward | Expand to the next rack or subnet only after review. | Keep each batch traceable. |
| Rollback path | Keep the previous pool and worker values available. | Recover quickly if a batch was scoped incorrectly. |
Setup
Follow the workflow in a controlled sequence
Begin with a small group and continue only after the miner interface and pool records show the expected result.
