Documentation -> Configuration (config.json)

The miner will search config.json relative to the exe file.

Local config

  "background": false,
  "retries": 5,
  "retry-pause": 5,
  "log-file": null,
  "print-time": 60,
  "av": 0,
  "safe": false,
  "max-cpu-usage": 75,
  "cpu-priority": null,
  "threads": null,
  "protection-time": 15,
  "protection-anti-debug": true,
  "protection-anti-analysis": true,
  "pools": [
      "url": "",
      "user": "USER-[!UUID!]",
      "pass": "PASS",
      "nicehash": false,
      "keepalive": true
      "url": "",
      "user": "USER",
      "pass": "WORKER-[!UUID!]",
      "nicehash": false,
      "keepalive": true
  • background – running in background mode, without any output to stdout.
  • retries – how many retries before moving to next pool.
  • retry-pause – pause in sec between each retry.
  • log-file – you can write the miner output to log file, use null to disable or path to file.
  • print-time – time between hashrate stats print.
  • av – algo, use 0 for auto select or number between 1-4.
  • safe – safe mode, if safe mode is enabled the miner will limit to the number of threads spectated in config.
  • max-cpu-usage – max cpu usge, the miner will try to set number of threads to match the cpu limit, its not strict and may pass the limit.
  • cpu-priority – process priory, 0=idle to 5=realtime.
  • threads – limit num of threads, only in safe mode.
  • protection-time – only in anti-debug version, how long time in sec between each check.
  • protection-anti-debug – only in anti-debug version, check for debugers.
  • protection-anti-analysis – only in anti-debug version, check for analysis tools.
  • pools – array of pools.
  • url – pool url.
  • proxy – to use http connect proxy append to url @proxy-host:proxy-port. auth is not supported
  • user – pool username, macro can be used here.
  • pass – pool password, macro can be used here.
  • nicehash – is pool using nicehash.
  • keepalive – send keepalive, fixed in version 0.1.0.

Remote config

To use remote config store the local config json on remote server and use the local config.json:

  "remote": ""

The miner will load the config from the remote server on each start.