HashCore Toolkit uses a local-first architecture that prioritizes performance, security, and ease of deployment. Understand the system design behind efficient ASIC fleet management.
This page explains how HashCore discovers devices, communicates with miners, stores data, and scales to manage thousands of devices efficiently.
Local-First Architecture
Runs on your network without cloud dependencies
HashCore Toolkit operates as a local application that runs on a single machine within your mining network. This machine acts as the management server, communicating directly with ASIC miners over the local network.
Unlike cloud-based management platforms, HashCore does not require data to leave your facility. All monitoring data, configuration settings, and operational history remain under your control. This approach improves security, reduces latency, and ensures management capabilities continue functioning even if internet connectivity is lost.
The local-first design helps keep management traffic inside your environment. Remote access and external exposure should be planned around your own network and security controls.
Device Discovery Process
Automatic detection of ASIC miners on the network
HashCore automatically discovers ASIC miners by scanning specified IP ranges and guided local network discovery workflows supported by the devices you operate. When a miner is detected, HashCore identifies the model, firmware version, and current configuration.
Discovery Methods
1.
IP Range Scanning: Scan specific subnet ranges (e.g., 192.168.1.0/24) to find miners
2.
Network Broadcast: Use guided network scanning and discovery workflows to detect miners automatically
3.
Manual Addition: Add specific IP addresses for miners with static assignments
4.
Import from CSV: Bulk import device lists with IP and credential information
Once discovered, devices are added to the management dashboard where they can be organized into groups, labeled by location or purpose, and monitored continuously. Discovery runs periodically to detect new devices or changes in the network.
Communication with Miners
How HashCore interacts with ASIC devices
HashCore Toolkit communicates with supported miners over the local network to collect status, run diagnostics, and apply supported actions from one interface.
Supported Communication Methods
•
Supported status interfaces: Read hashrate, temperature, and diagnostic data from supported miner environments
•
Local web management endpoints: Apply supported configuration changes where vendor interfaces allow it
•
Maintenance workflows: Use supported firmware-specific flows for diagnostics and update tasks
HashCore keeps device status current through repeated monitoring cycles while balancing visibility and network overhead.
For bulk operations affecting hundreds of devices simultaneously, HashCore implements intelligent batching and rate limiting to prevent network congestion. Operations are queued and executed in parallel threads up to a configurable concurrency limit.
Data Storage and Management
How operational data is stored and accessed
HashCore stores operational data in a local database on the management server. This includes device inventory, configuration history, performance metrics, and audit logs.
Stored Information
•Device inventory with hardware details and network information
•Historical performance data (hashrate, temperature, power consumption)
•Configuration templates and deployment history
•User accounts, permissions, and audit logs
•Alert rules and notification preferences
Time-series data like hashrate and temperature is retained with configurable retention policies. Aggregated summaries preserve long-term trends while managing storage requirements. Detailed logs can be exported for external analysis or compliance requirements.
Backup and recovery planning should follow the operational standards you use for the host running Toolkit and its local data.
Scalability and Performance
HashCore Toolkit is designed to manage up to 50,000 devices from a single instance. This capacity assumes a properly sized management server with adequate CPU, memory, and network connectivity.
For operations exceeding 50,000 devices or requiring geographic distribution, multiple HashCore instances can be deployed with centralized oversight through HashCore Pulse. This architecture supports larger multi-site operations without forcing every device into one local instance.
Recommended Server Specifications
Up to 1,000 Devices
• 4 CPU cores
• 8 GB RAM
• 50 GB storage
• 1 Gbps network
Up to 50,000 Devices
• Server-class CPU resources
• 32+ GB RAM
• 500 GB storage
• High-throughput local network
See the installation guide for detailed hardware requirements and deployment recommendations based on your fleet size.
Ready to deploy HashCore Toolkit in your environment?