How to Set Up BTC Tools on a Miner Network
Set up BTC Tools on a trusted local network: record the current state, scan the correct subnet, test a small group and verify results.
Workflow
BTC Tools setup checklist
A reliable setup starts before opening the application: verify the file, document the network, know the expected miners, and prepare a small test group with a rollback path.
2. Connect
Use a trusted workstation that can reach only the intended miner management network.
3. Discover
Confirm the imported range, scan, and compare results with the expected inventory.
4. Change and review
Apply prepared settings to a small selected batch and validate local and pool-side results.
Checklist
Before you continue
Complete the inventory and network checks before using credentials or configuration actions.
- Choose the correct Windows, Linux, or source route.
- Confirm authorized private IP ranges.
- Record the expected miner count and current settings.
- Scan without making changes first.
- Group miners by owner, rack, model, and firmware.
- Apply one prepared change to a small test group.
- Review exceptions before expanding the batch.
Operations
Setup stages and acceptance checks
Do not move to the next stage until the current result matches the plan.
| Area | What to check | BTC Tools workflow |
|---|---|---|
| Package | Correct platform, architecture, size, and file record | Stop on any mismatch. |
| Network | Workstation reaches only intended subnets | Exclude public and unrelated ranges. |
| Discovery | Found miners match inventory | Resolve missing and unexpected devices. |
| Credentials | Access works for the selected group | Do not mix unknown ownership or firmware. |
| Configuration | Prepared values applied to a test batch | Keep rollback values. |
| Validation | Local status and pool activity agree | Document timeouts and exceptions. |
Setup
Use a test batch as the gate
The first successful scan is not approval for a full-farm change. Select a small representative group, apply one change, and validate it before widening scope.
Diagnose discovery before changing miner settings
| Observed result | Next check | What it does not prove |
|---|---|---|
| No devices listed | Run ipconfig on the Windows workstation; compare its address, subnet mask and route with the authorized miner management range. | An empty scan does not prove the miner is offline. |
| Device listed, action rejected | Confirm the exact model/firmware and use credentials supplied by the administrator. Test an authenticated read first. | Discovery does not establish write permission or universal model support. |
| Settings appear saved, pool state unchanged | Read settings back from the miner and compare the pool worker status after its reporting interval. | A successful button click does not prove accepted shares or earnings. |
Example record: workstation OS; tool version; miner model/firmware; authorized range; expected device count; observed result; exact error. Keep passwords out of that record. Export the available results for comparison before and after a scheduled change.
Use the package selection page to distinguish a Windows archive from Linux packages and a source snapshot.
Documentation reviewed September 28, 2026. This is an independent operator guide; compatibility must be checked against the installed version. Source: project documentation.