Skip to main content
Nonce Agent scans configured IP ranges for miners, reports discovered devices to Nonce, and continues collecting data after the scan completes.

​
Scan Workflow

  1. You start a scan from the Nonce UI.
  2. The Agent retrieves the task from the server and begins scanning.
  3. The Agent probes each address in the configured IP range and identifies miners.
  4. For each discovered miner, the Agent retrieves device details and reports them immediately.
  5. Nonce processes the reported data and updates the miner records in the UI.
  6. After the scan, the Agent continues scheduled data collection to keep miner records current.

​
Scan Behavior

​
Manual scan

  • The Agent reports each discovered miner without waiting for the entire IP range to finish.
  • Miner records may appear in Nonce before the scan task completes.
  • The Agent adds discovered miners to its monitoring list for scheduled data collection.

​
Automatic scan

  • The Agent rescans saved IP ranges on a schedule.
  • Scheduled scans can discover newly connected miners without another manual scan.

​
How Long Until Miner Data Appears?

Elapsed time varies with the IP range size, network quality, miner response time, and configured Agent intervals. With the default intervals, typical timing is:
  • Agent installation confirmation: Within a few seconds after you run the installation command and confirm the installation
  • Manual scan start: Within approximately 5 to 10 seconds
  • First miner record: Often within tens of seconds after the manual scan starts
  • Scheduled miner data collection: Every 5 minutes
  • Automatic IP range scan: Every 60 minutes
A scan task can complete before the latest miner data appears in the UI.

​
What Affects Scan Duration?

  • IP range size: scanning /24 is much faster than scanning several large ranges at once
  • Miner response speed: slow or overloaded miners take longer to identify
  • Network quality: routing issues, packet loss, or firewall rules can slow detection
  • Miner credentials: incorrect web passwords can prevent metadata collection for some miner models
  • Retries: retrying failed data requests improves the success rate but increases the total scan time