Bitcoin mining software: how to manage an ASIC mining farm with BTC Tools, sub-accounts, and batch updates

Managing an ASIC mining farm requires moving beyond individual miner web interfaces to batch operations, centralized monitoring, pool-side dashboards, and structured sub-account management. BTC Tools can scan an IP address range and batch-configure supported Antminer and Avalon ASICs on a local network. Awesome Miner is well suited for Windows-based, multi-vendor mining fleets. Foreman.mn is designed for larger cloud-managed mining operations. Pool sub-accounts separate workers by location, model, or client, using worker names like farm1.s21pro-001.
Network management and monitoring software for ASIC miners enables real-time performance tracking and optimization to improve mining efficiency. A single ASIC can be managed manually. Five ASICs already need structure. Fifty ASICs need a workflow. At that point, mining becomes an operations problem: IP addresses, firmware versions, worker names, pool settings, high temperature warnings, fan speed, rejected shares, payouts, uptime, bandwidth, latency, and network stability.
This guide explains how retail and mid-size miners can manage a growing ASIC fleet using BTC Tools, Awesome Miner, Foreman.mn, pool dashboards, sub-accounts, worker names, Antminer API access, and custom integrations.
Key takeaways
ASIC farm management becomes harder after five machines because manual web-interface checks do not scale.
BTC Tools can scan Antminer miners, sort devices, perform batch setup, reload equipment, batch set pools and worker names, reboot miners, and update firmware. It lists support for Antminer S17, T17, S9, S7, T9 and Avalon A8, A7, A6.
Awesome Miner supports more than 200 ASIC miner models, including Bitmain Antminer, Canaan Avalon, Goldshell, Innosilicon, Obelisk, and Whatsminer.
Foreman.mn is a cloud-based mining management system for larger mining operations, hosting providers, and industrial sites.
A pool dashboard should serve as the primary management interface because it reflects pool-side performance, including worker status, hashrate stability, accepted shares, reject patterns where available, and payout visibility.
A practical worker name format is subaccount.miner-postfix, for example farm1.s21pro-001.
Real-time monitoring should track hashrate, temperature, fan speed, share submissions, uptime, alert thresholds, and network health indicators. Real-time monitoring features in ASIC management tools provide a summary of key metrics like temperature and fan speed, enabling quick responses to issues.
Batch configuration, firmware updates, and remote rebooting are essential for scaling.
Energy efficiency is critical for Bitcoin mining in 2026, and software supporting undervolting can help reduce electricity costs.
Automation and alerting are necessary for uptime and profitability.
Mining pools generally require ASICs to connect through mining software or firmware, allowing participants to combine computational power and share rewards.
Why management tools become essential after 5 ASICs
Managing a single ASIC is straightforward. You open the miner’s web interface, enter the Stratum endpoint configuration, add the worker name, and check whether hashrate appears in the pool dashboard.
Once a mining operation exceeds five ASICs, operational challenges begin to accumulate.
| Problem | What happens |
| Different IP addresses | Machines become harder to find on the local network |
| Different models | Antminer S19, S21, Whatsminer M60, and Avalon units behave differently |
| Different firmware versions | Updates and settings become inconsistent |
| Random worker names | It becomes hard to match pool workers to physical machines |
| No sub-accounts | Locations, clients, and models get mixed together |
| No alert thresholds | Problems are noticed too late |
| Local-only checks | The miner may look fine locally but underperform pool-side |
A growing fleet may include Antminer S19, S19 Pro, S21, S21 Pro, Whatsminer M30, M50, and M60, as well as Avalon A1566 units. Each machine has its own expected hashrate, power behavior, temperature profile, firmware access, and monitoring limits.
The goal is to establish a simple operational framework for the mining farm:
- Scan the network
- Identify machines
- Group workers logically
- Configure pool settings in batches
- Monitor pool-side performance
- Set alert thresholds
- Test updates before rolling them out
- Document what changed
A mining management system enables managers to track and manage assets in real time, which improves overall company performance and supports better decision-making.
Bitcoin mining software and farm management
Bitcoin mining software connects ASICs to a mining pool, receives work assignments from the network through the pool, and directs the hardware to perform SHA-256 hashing operations. Modern bitcoin mining software streamlines the process of connecting ASICs to pools and helps optimize operational efficiency by automating configuration, monitoring, and troubleshooting tasks throughout the mining operation lifecycle.
Mining pools require miners to connect their hardware through mining software or firmware. This lets individual miners combine computational power and receive payouts according to the pool’s payout model.
As a mining operation grows, software becomes the central control layer.
| Type | Examples | Suitable for |
| Built-in ASIC firmware | Stock Antminer, Whatsminer, Avalon firmware | Basic connection and machine control |
| Batch operation tools | BTC Tools | Local scanning, pool config, reboot, firmware updates |
| GUI management tools | Awesome Miner, EasyMiner-style tools | Visual control and monitoring |
| Command-line tools | CGMiner, BFGMiner | Advanced users |
| Cloud mining management systems | Foreman.mn | Larger sites and hosted fleets |
| Pool dashboards | EMCD Pool dashboard | Pool-side worker monitoring and payout visibility |
CGMiner and BFGMiner are open-source and customizable tools usually favored by advanced users. GUI-based tools are easier for beginners. Batch tools reduce repetitive work. Cloud platforms help larger teams manage mining operations across sites.
The pool dashboard remains central because it shows whether the miner is submitting work to the pool and whether that work is counted.
BTC Tools: scan, configure, and batch-update your fleet
BTC Tools is a practical solution for retail and mid-sized mining operations that require batch management on a local network.
It can scan supported Antminer and Avalon ASICs by IP address range, configure pool settings, update worker names, reboot selected miners, monitor core data, and apply firmware updates to supported devices. The software enables users to specify which port or ports to monitor, the type of data to collect, sampling time, and histogram size, allowing for effective tracking of ASIC performance metrics.
| Brand | Supported models to check first |
| Bitmain Antminer | S7, S9, S17, T17, T9 |
| Canaan Avalon | A6, A7, A8 |
| BTC Tools feature | Why it matters |
| ————————————- | ——————————————————– |
| IP scanner | Finds miners across a local network |
| Batch pool config | Updates pool URL, worker name, and password |
| Batch worker name setup | Keeps naming consistent |
| Batch reboot | Restarts selected miners after changes |
| Batch firmware update | Updates supported ASICs without opening each interface |
| Configuration file handling | Helps keep repeated settings structured |
| Temperature, fan, and hashrate view | Gives fast local visibility before pool-side checks |
BTC Tools functions as a batch management layer rather than the definitive source of operational performance data. After using it, the operator should still check the pool dashboard to confirm accepted work reaches the pool.
For newer machines like Antminer S19, S19 Pro, S21, S21 Pro, Whatsminer M30, M50, M60, or Avalon A1566, check exact compatibility before relying on BTC Tools for batch updates.
How to build a clean miner inventory
A growing mining operation requires a well-maintained inventory system. Some management tools can automatically import miners or pull basic information such as IP address, model, hashrate, temperature, fan speed, firmware version, working mode, or status.
| Data point | Why it matters |
| Miner model | Helps compare expected performance |
| IP address | Helps locate and access the machine |
| Network segment | Shows where the miner sits |
| Worker name | Links the machine to the pool dashboard |
| Firmware version | Helps plan updates |
| Working mode | Shows standard, low-power, or custom settings |
| Temperature | Helps identify cooling problems |
| Fan speed | Helps detect fan or airflow issues |
| Pool configuration | Confirms the correct Stratum endpoint |
| Status | Shows whether the miner is functioning normally |
An undocumented miner is effectively unmanaged.
Awesome Miner, Foreman.mn, and mining management systems
Awesome Miner is a Windows-based platform for managing and monitoring mixed mining fleets. It supports more than 200 ASIC miner models across brands such as Bitmain Antminer, Canaan Avalon, Goldshell, Innosilicon, Obelisk, and Whatsminer.
One of its primary advantages is rules-based automation. Operators can create rules that detect mining issues and trigger actions, such as alerts or scheduled ASIC reboots.
Foreman.mn is built for larger mining operations that need cloud-based visibility, remote access, and site-level coordination. It is more relevant for industrial miners, hosting providers, data centers, and mining companies managing hundreds or thousands of ASICs.
A mining management system, or MMS, is a computer-based system used to plan, control, monitor, and manage equipment, people, and operational workflows. In the mining industry, digital systems like MMS have transformed operations by delivering measurable value through improved efficiency and better resource utilization. In ASIC mining, the term is usually applied more narrowly: software that helps operators monitor miners, manage tasks, track performance, and respond to problems.
MMS tools typically include modules for safety monitoring, production scheduling, dispatch control, performance management, asset tracking, analytics, and resource planning. Real-time data collection and analytics on key performance indicators (KPIs) are essential features for better decision-making and resource allocation, helping operators decide which machines need repair, which sites are unstable, and where power or cooling issues are affecting output.
Pool dashboard: your primary management surface
A pool dashboard should serve as the primary management interface for a mining operation.
It does not replace BTC Tools, Awesome Miner, Foreman.mn, firmware dashboards, or local web interfaces. It reflects actual pool-side performance.
| Pool dashboard metric | Why it matters |
| Worker status | Shows whether each ASIC is online or offline |
| Real-time hashrate | Shows current pool-side performance |
| Average hashrate | Shows stability over time |
| Reject patterns, where available | Helps detect connection or configuration issues |
| Share submission | Shows whether work reaches the pool |
| Payout visibility | Shows how accepted work contributes to payout calculation |
| Sub-account view | Helps separate locations, models, or clients |
| Statistics | Helps review performance across time periods |
This is where EMCD Pool fits naturally.
EMCD Pool provides pool-side monitoring, mining account management, transparent payout tracking, and detailed visibility into worker performance. The base fee is 1.5%, with personalized rates available for larger miners based on hashrate.
EMCD Pool should not be positioned as an ASIC control platform. It does not replace BTC Tools, Awesome Miner, or Foreman.mn. It sits above them as the pool-side performance layer, helping miners see whether workers are connected, stable, and contributing accepted work.
EMCD also brings practical mining advantages: easy connection, transparent payout tracking, 24/7 monitoring, merge mining where supported, dedicated live support from real experts, and flexible plans for larger miners.
Tools comparison
| Tool | OS | Supported ASICs | Batch ops | Suitable for |
| BTC Tools | Windows | Antminer S7, S9, S17, T17, T9 and Avalon A6, A7, A8 | IP scan, batch pool config, worker naming, reboot, firmware update for supported models | Retail and mid-size miners with supported local ASICs |
| Awesome Miner | Windows | 200+ ASIC miner models, including Antminer, Avalon, Whatsminer, Goldshell, Innosilicon, and others | Rules-based automation, alerts, selected reboot and management actions depending on model | Mixed-vendor fleets and Windows-based operators |
| Foreman.mn | Cloud-based | Broad ASIC fleet support for larger operations | Remote monitoring, automation, asset tracking, infrastructure visibility | Industrial miners, hosting providers, data centers |
| Pool dashboard | Web-based | Any compatible ASIC configured to connect to the pool | Not for firmware batch updates, but strong for worker monitoring, sub-accounts, hashrate, share status, and payout visibility | Primary pool-side monitoring across ASICs and locations |
Sub-accounts: how to structure a multi-location farm
Sub-accounts separate workers by location, model, client, or hosted group within one pool account.
A simple structure looks like this:
Main pool account
│
├── farm1
│ ├── farm1.s21pro-001
│ ├── farm1.s21pro-002
│ └── farm1.s19pro-003
│
├── farm2
│ ├── farm2.m60-001
│ ├── farm2.m60-002
│ └── farm2.m50-003
│
└── hosted
├── hosted.clientA-s19-001
├── hosted.clientA-s19-002
└── hosted.clientB-a1566-001
| Structure | Example | Suitable use |
| Location | farm1, farm2, warehouse1 | Different rooms, sites, or facilities |
| ASIC model | s21pro, m60, a1566 | Comparing performance by machine type |
| Client | hosted-clientA | Mining hotels and hosting providers |
| Strategy | standard, undervolt, test | Firmware and power-mode testing |
| Business unit | own-fleet, partner-fleet | Internal reporting and payout organization |
Some pool setups also allow separate payout addresses for sub-accounts. This can help with hosted miners, partner arrangements, and accounting. Operators should check the exact pool settings before promising this structure to clients.
Worker names that actually help
A worker name serves as the miner's identifier within the pool dashboard.
Use this format:
subaccount.miner-postfix
Examples:
farm1.s21pro-001
farm1.s21pro-002
farm1.s19pro-003
farm2.m60-001
farm2.m50-002
hosted.clientA-s19-001
hosted.clientB-a1566-001
test.s21-undervolt-001
A strong worker name should show the sub-account, model, unit number, and optional mode. Avoid names like miner1, antminer, newminer, btc123, or test. These naming conventions may appear harmless initially. Then the farm grows, one miner overheats, another drops hashrate, and someone has to guess which box is which. That is not effective troubleshooting, it is guesswork.
ASIC monitoring: what to track and when to alert
Effective ASIC monitoring extends far beyond tracking hashrate alone. Real-time monitoring should include temperature, fan speed, hashrate, worker status, share submissions, uptime, reject patterns where available, and network health indicators.
| Metric | What it tells you |
| Hashrate | Whether the miner performs near its expected level |
| Temperature | Whether the ASIC is overheating |
| High temperature events | Whether cooling is failing or intake air is too warm |
| Fan speed | Whether cooling is healthy |
| Worker status | Whether the miner is online |
| Share submission | Whether work reaches the pool |
| Reject patterns | Whether submitted shares face issues |
| Uptime | Whether the miner is stable |
| Bandwidth and latency | Whether the network may affect share submission |
To configure ASIC monitoring properly, operators should define the data type, device scope, sampling time, alert threshold, history window, and response action.
A similar logic exists in broader infrastructure monitoring. NVIDIA’s Cumulus Linux, for example, can collect network ASIC telemetry by defining data types, ports, sampling time, and histogram settings. Bitcoin miner monitoring is different, but the principle is similar: collect the right telemetry, set thresholds, and respond before small issues become downtime.
Energy efficiency, undervolting, and power management
Energy efficiency is critical for Bitcoin mining in 2026. Electricity is often the largest operating expense, making undervolting, voltage optimization, and power management features increasingly important.
Undervolting can reduce electricity use by lowering voltage and power draw. The goal is to reduce cost without a major loss of accepted hashrate.
A miner can look efficient locally but perform worse pool-side. If power drops by 12% but accepted hashrate drops by 18%, the setting may not be helping. Operators should compare firmware changes against pool dashboard data, not only local miner screens.
Antminer API, SSH access, and advanced controls
Advanced operators may use Antminer APIs, SSH access, JSON-RPC, or other endpoints to collect miner data and automate fleet management tasks. For example, using the second one of the available Antminer API commands, you can retrieve and parse JSON data such as miner status, pool information, and rejected shares, often by sending RESTful calls or Python scripts to manipulate API commands and extract specific fields from the JSON response.
| Advanced access type | Use case |
| Antminer API | Pull miner status or performance data where supported |
| JSON-RPC | Communicate with compatible mining software |
| SSH access | Perform deeper configuration or diagnostic tasks |
| API endpoint | Connect mining data to custom dashboards |
| Telemetry export | Send performance data to BI tools or reports |
| Alert routing | Push warnings to Telegram, Slack, email, or incident systems |
| Custom code | Build internal scripts for collecting data or sending alerts |
Advanced access should not be the first layer of management. If worker names are random and sub-accounts are messy, API automation will only make the mess move faster.
Profit switching and merge mining
Profit switching allows mining software to redirect resources toward the most favorable coin or pool based on conditions such as coin price, network difficulty, payout model, and fees.
For Bitcoin-focused ASICs, hardware is designed for SHA-256 mining. The practical options depend on supported coins, pool setup, firmware, payout rules, liquidity, and switching costs. Frequent switching can introduce downtime, configuration errors, and reduced pool-side performance.
EMCD Pool supports merge mining, which lets miners mine multiple coins simultaneously where supported. This is a cleaner angle than overpromising profit switching. It gives miners more utility from the same work while staying within pool-supported workflows.
Safety, network control, and facility planning
ASIC farm management involves much more than software alone. It also includes safety, network control, cooling, power stability, and basic facility planning.
| Area | What to control |
| Power | Circuit load, breaker capacity, cabling, power distribution |
| Cooling | Intake temperature, exhaust flow, high temperature alerts |
| Network | Router, switches, IP address range, network segments, latency |
| Safety | Fire risk, cable routing, airflow, emergency access |
| Access | Who can change firmware, pool settings, and configuration files |
| Documentation | Device list, worker names, ports, firmware versions, changes |
| Monitoring | Pool dashboard, local ASIC monitoring, alerts, statistics |
This planning layer helps the mining setup operate efficiently. Without these controls, software tools can do little more than report problems after they occur.
Pre-setup operations checklist
- List every ASIC by model, serial number, IP address, location, firmware version, and expected hashrate.
- Map the local network, including IP address range, routers, switches, network segments, ports, and access rules.
- Decide the sub-account structure before connecting more workers: by location, model, client, hosted group, or test group.
- Create a worker naming convention using subaccount.miner-postfix, such as farm1.s21pro-001.
- Confirm Stratum endpoint configuration for each sub-account and document the pool URL, worker format, and password convention.
- Scan the local network with BTC Tools or another IP scanner to identify all miners and remove unknown or duplicate entries.
- Test batch pool configuration on one or two selected miners before applying settings to the full fleet.
- Set baseline ASIC monitoring thresholds for hashrate, temperature, fan speed, worker offline status, share submission, and uptime.
- Check pool-side monitoring after every major change, including firmware updates, pool setting changes, undervolting, or power-mode adjustments.
- Keep an operations log for firmware versions, reboots, configuration changes, alert events, repairs, statistics, and recurring issues.
FAQ
What is BTC Tools?
BTC Tools is a miner management utility used to scan and manage supported ASICs on a local network. It can help with IP range scanning, batch pool setup, worker naming, rebooting, and firmware updates for supported models. It is commonly checked first for Antminer S7, S9, S17, T17, T9 and Avalon A6, A7, A8 units.
How do I update firmware on multiple Antminers at once?
Use a batch tool that supports the exact Antminer model and firmware version. Scan the IP address range, select a small test group, upload the correct firmware, apply the update, and confirm stability before updating the full fleet. After the update, check local miner status and pool-side hashrate, share submission, reject patterns where available, and payout visibility.
What is a worker name in mining?
A worker name is the identifier of a miner inside the pool dashboard. It helps the pool and operator track which ASIC is submitting shares. A scalable format is subaccount.miner-postfix, for example farm1.s21pro-001. This makes it easier to identify location, model, and physical unit.
How do mining sub-accounts work?
Mining sub-accounts sit under one main pool account and separate workers by location, model, client, or operating purpose. For example, one account can include farm1, farm2, and hosted, with different workers inside each group. This helps with monitoring, troubleshooting, reporting, and payout organization.
Which tool is suitable for managing 5-50 ASICs?
For 5-50 ASICs, a practical setup usually combines BTC Tools for supported local batch operations, Awesome Miner for Windows-based multi-vendor management, and a pool dashboard for primary performance monitoring. Larger hosted or industrial operations may also need Foreman.mn for cloud-based fleet management.
Does ASIC monitoring replace pool monitoring?
No. ASIC monitoring shows device-level data such as temperature, fan speed, local hashrate, uptime, and functioning status. Pool monitoring shows whether the ASIC is connected, submitting work, and contributing to pool-side performance. A growing farm needs both.
Conclusion
ASIC farm management becomes significantly more complex after five machines. At that stage, relying on individual web interfaces is no longer a scalable workflow. It is a sign that the operation needs structure.
BTC Tools can help with local batch operations for supported Antminer and Avalon models. Awesome Miner fits Windows-based multi-vendor fleets. Foreman.mn is built for larger cloud-managed mining operations. But the pool dashboard remains the primary management surface because it shows the pool-side result: which workers are online, which workers are stable, how much hashrate reaches the pool, and whether the setup is producing accepted work.
EMCD Pool is positioned in that operational layer. It gives miners pool-side monitoring, mining account management, transparent payout tracking, 24/7 monitoring, merge mining where supported, and dedicated live support from real experts. The base fee is 1.5%, with personalized rates available for larger miners based on hashrate.
For a growing mining operation, success depends less on opening more browser tabs and more on building repeatable processes. It is building a cleaner system: structured sub-accounts, readable worker names, batch operations where they make sense, and pool-side monitoring that shows whether every ASIC is actually doing its job. After any configuration change or monitoring adjustment, pool-side performance should be verified to confirm that the operation is consistently producing accepted work.










