How to use Awesome Miner for large scale mining? (Management)

Setting Up Centralized Mining Control

1. Install Awesome Miner on a dedicated Windows server with stable uptime and sufficient RAM to handle hundreds of miners simultaneously.

2. Configure the software to connect to mining pools using API keys that support real-time statistics and remote configuration updates.

3. Deploy the Awesome Miner Remote Agent on each physical mining rig, ensuring all agents report back through encrypted HTTPS channels.

4. Assign unique identifiers and location tags to every miner to enable granular filtering and group-based management across geographically dispersed facilities.

5. Integrate SNMP or IPMI-enabled hardware monitoring to correlate hashrate drops with thermal throttling or power supply anomalies.

Automating Profitability Switching

1. Enable the built-in profitability calculator using live coin price feeds from CoinGecko and network difficulty data pulled directly from blockchain explorers.

2. Define custom profit thresholds per algorithm—such as Ethash, KawPoW, or Autolykos—to trigger automatic pool switching without manual intervention.

3. Set up fallback rules so that if a primary pool becomes unreachable for more than 90 seconds, the system routes hashpower to a preconfigured secondary pool instantly.

4. Log all switch events with timestamps, profitability delta, and pool response latency to identify recurring instability patterns in specific mining regions.

5. Disable auto-switching during scheduled firmware upgrades to prevent unintended reconfiguration while devices are in maintenance mode.

Monitoring and Alert Infrastructure

1. Configure email and Telegram webhook alerts for critical conditions including zero hashrate, fan failure, temperature above 85°C, or repeated watchdog resets.

2. Build custom dashboards showing real-time metrics: average GPU utilization per rack, total kWh consumed per hour, and pool-reported rejected share rate.

3. Use the integrated script engine to run PowerShell commands that restart mining services or reboot rigs when memory leaks exceed predefined thresholds.

4. Archive historical performance logs in compressed ZIP format daily and retain them for exactly 90 days to comply with internal audit requirements.

5. Tag alert severity levels explicitly—Critical, Warning, Info—so on-call engineers can triage based on escalation policies defined in PagerDuty integrations.

Firmware and Driver Lifecycle Management

1. Maintain version-controlled repositories for GPU drivers and ASIC firmware binaries, verified via SHA-256 checksums before deployment.

2. Schedule non-disruptive rolling updates during low-hashrate windows—typically between 02:00–04:00 UTC—when electricity tariffs are lowest.

3. Apply firmware patches only after validation on isolated test rigs running identical hardware configurations and overclock profiles.

4. Roll back failed driver updates automatically using Windows System Restore points triggered by post-installation stability checks.

5. Enforce mandatory firmware signing checks on Bitmain and MicroBT devices to block unauthorized or tampered binaries from loading.

Frequently Asked Questions

Q: Can Awesome Miner manage both GPU and ASIC devices simultaneously?Yes. It supports over 40 mining software variants and communicates natively with Antminer, Whatsminer, and Innosilicon devices via HTTP API or SSH protocols.

Q: Is it possible to restrict certain users from modifying overclock settings?Yes. Role-based access control allows administrators to disable overclock editing for junior operators while permitting read-only dashboard access.

Q: Does Awesome Miner store wallet credentials locally on the server?No. Wallet addresses and private keys are never stored or transmitted by Awesome Miner. Payout destinations are configured exclusively at the pool level.

Q: How does Awesome Miner handle time synchronization across thousands of rigs?It relies on the Windows Time Service on the central server and forces NTP sync on remote agents during agent startup and every six hours thereafter.