Network access
Confirm that the workstation can reach the miners on the management LAN or VLAN.
Updated June 16, 2026 - BTC Tools operations guide
How to configure Antminer workflows with BTC Tools
Plan Antminer-style setup with BTC Tools: network access, pool URLs, worker names, backup pools, and review steps.
BTC Tools
Configure Antminer Workflows with BTC Tools
Antminer-style setup should be handled as an operational workflow: prepare pool details, confirm the target group, apply changes to a small batch, and review miner status afterward.
Workflow
Before configuration
Use this page as a practical planning reference for local ASIC miner operations. The exact behavior available in BTC Tools can depend on miner model, firmware, network access, and the action being performed.
Pool details
Prepare primary and backup pool URLs, worker names, and password fields before editing.
Batch scope
Start with a small rack, subnet, or miner group before expanding the change.
Review path
Check local reachability and pool-side worker activity after configuration.
Checklist
Before configuration
Keep the scope narrow, document device groups, and separate local miner status from pool-side account data.
- Target IP range or subnet.
- Admin access for miners you control.
- Primary and backup pool URLs.
- Worker naming convention.
- Expected rack, room, or device group.
- Pool account format for worker names.
- Current settings record before the change.
- Small test group that matches the firmware group.
Operations
Configuration fields
These tables are written for miners and technicians who need repeatable local workflows rather than broad crypto marketing copy.
| Area | What to check | BTC Tools workflow |
|---|---|---|
| Pool URL | Mining pool endpoint supplied by the pool. | Use the pool format expected by your account. |
| Worker name | Miner identifier visible in the pool dashboard. | Map workers to rack, room, or serial records. |
| Password field | Pool-specific value; often simple but depends on the pool. | Use the value required by the pool account. |
| Backup pool | Fallback endpoint if the primary pool is unavailable. | Keep backup settings consistent across a batch. |
| IP range | Local subnet or management VLAN target. | Avoid scanning unrelated office or public networks. |
| Device group | Rack, room, switch, model, or firmware group. | Apply settings only to the intended group. |
| Review window | Time after applying changes. | Confirm pool-side worker activity and local reachability. |
| Exception list | Miners excluded from the batch. | Avoid changing devices under repair or under separate ownership. |
Setup
Plan, scan, change, and review
For every BTC Tools workflow, start from the intended IP range and device group, then apply changes in small controlled batches and review results before expanding the scope.
