Hierarchy: Organization → Sites → Agents → Scan Tasks → Workers

Hierarchy Levels

Organization
└── Sites
    └── Agents
        └── Scan Tasks
            └── Workers

Organization v1.0.0-alpha4

The top level of the operational hierarchy. It unifies physical sites and team members within a Business account. Member roles and site scoping permissions are configured at the organization level (see "Roles and Permissions"). In Personal accounts, the organization level is hidden: it consists of a single site and a single user.

Sites

A Site is a physical or logical entity within the organization: a mining farm, a data center, an individual building, or a container. All other functional 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 and operating expenses
• Maximum power capacity (Capacity) — for tracking infrastructure load
• Group operation settings (batch command pacing and delays)

Typical scenario: A company operates multiple mining facilities across different regions — each facility corresponds to a dedicated site in Pulse.

Agents

An Agent is a lightweight local application installed on a computer, server, or directly on mining hardware within the same local network as the miners. The agent serves as the communication bridge between on-site machines and the HashCore cloud.

What an agent does:

• Scans the local network within configured IP ranges
• Discovers ASIC devices and retrieves real-time telemetry
• Streams metrics to HashCore cloud infrastructure in real-time
• Executes operator commands (reboot, pool reconfiguration, firmware updates, etc.)

Agent operating modes:

• Full Control — telemetry monitoring and command execution (default)
• Monitoring Only — read-only telemetry streaming, command execution disabled

Multiple agents can run within a single site — for example, across segmented subnets or separate network zones.

Scan Tasks

A Scan Task defines where and how an agent searches for hardware: which IP ranges to scan and which credentials to use for authentication. Each agent can run multiple scan tasks concurrently.

What is configured in a Scan Task:

• Network ranges — target IP subnets and ranges. Supports import from TXT, CSV, JSON, and CIDR aggregation
• Unlock Configs — authentication credentials for devices with non-standard credentials (HashCore, Bitmain)
• Status — tasks can be enabled or disabled without deletion

Typical scenario: One task scans 192.168.1.0/24, while another scans 10.0.0.0/24. Each task can define tailored unlock credentials.

Workers — Devices

Workers are ASIC miners discovered by the agent during network scans. Devices are never added manually — they appear automatically as soon as the agent detects them on the local network.

What is available at the device level:

• Real-time telemetry: Hashrate, power draw, temperatures, fan RPM
• Connectivity Status and operational Miner Status
• Comprehensive details: network configuration, serial numbers, hashboard health, pool statistics
• Event Log — an immutable chronological timeline of all commands and status transitions
• Operations: reboot, pool updates, firmware installation, diagnostic bundles, and more

Summary Scheme