Hierarchy: Sites → Agents → Scan Tasks → Workers
HashCore Pulse is organized into a four-level hierarchy. Understanding this structure helps to properly configure the platform and efficiently manage hardware of any scale.
Hierarchy Levels
Sites
└── Agents
└── Scan Tasks
└── Workers
Sites
A Site is the top level of the hierarchy. It represents a physical or logical entity: a mining farm, a data center, a separate building, or a rack. All other entities — agents, devices, metrics — are tied to a specific site.
What is stored at the site level:
- Name and geographical location
- Electricity tariff — used to calculate net income
- Maximum power (Capacity) — for displaying site utilization
- Group operation settings (batch command sending)
Typical scenario: A single company manages several farms in different cities — each farm is a separate site in Pulse.
Agents
An Agent is a local application installed on a computer or server within the same network as the miners. The Agent acts as a link between devices on the site and the HashCore cloud.
What an agent does:
- Scans the local network within specified IP ranges
- Discovers ASIC devices and retrieves metrics from them
- Transmits data to the HashCore cloud in real-time
- Executes user commands (reboot, Pool change, firmware installation, etc.)
Agent operating modes:
- Full Control — metric collection and command execution (default)
- Monitoring Only — metric collection only, commands are not executed
Multiple agents can be connected to a single site — for example, if devices are located in different subnets.
Scan Tasks
A Scan Task defines what exactly the agent scans: which IP ranges to check and how to authenticate with devices. Each agent can have multiple scan tasks.
What is configured in a Scan Task:
- Network ranges — a list of IP ranges for scanning. Supports import from TXT, CSV, JSON, and range aggregation
- Unlock Configs — credentials for devices with non-standard passwords (HashCore, Bitmain)
- Status — a task can be enabled or disabled without deletion
Typical scenario: One task scans the 192.168.1.0/24 subnet, another scans 10.0.0.0/24. Each task can have its own authentication settings.
Workers — Devices
Workers are ASIC miners discovered by the agent during the scanning process. Devices are not added manually — they appear automatically once the agent finds them on the network.
What is available at the device level:
- Real-time metrics: Hashrate, consumption, temperature, fan RPM
- Connectivity status and Miner Status
- Detailed information: network parameters, serial numbers, board status, Pools
- Event Log — a chronological feed of all operations and changes
- Operations: reboot, Pool change, firmware installation, diagnostics, etc.
Summary Scheme
| Level | Entity | Who creates |
|---|---|---|
| 1 | Site | User manually |
| 2 | Agent | User manually |
| 3 | Scan Task | User manually |
| 4 | Worker | Agent automatically |
First Monitoring
Once the agent is running and devices are discovered, HashCore Pulse begins collecting and displaying real-time data. This section explains what you will see and what to pay attention to first.
Device Statuses
HashCore Pulse uses a two-tier status system for each device. The first tier reflects connectivity with the device, while the second indicates what is happening inside the miner. Together, they provide a complete overview of your farm's status without needing to access each device. `v0.7.0`