Skip to main content
Hashwarp 2.0 runs your 1.x command lines and configuration as they are. A few things work differently; this page lists them.

​
One download for every GPU

Hashwarp 1.x had separate CUDA and OpenCL builds. Hashwarp 2.0 has one build per system, which mines on NVIDIA GPUs with CUDA and on AMD and other GPUs with OpenCL, and needs no CUDA toolkit: only the GPU driver (NVIDIA 525 or newer). On Windows, NVIDIA GPUs no longer need the OpenCL runtime to be registered, and the archive no longer has fix-opencl-icd.vbs. If an AMD GPU isn’t found, see Troubleshooting.

​
Options

Every 1.x option still works. Most have a new, clearer name, which hashwarp --help shows; the old names are listed by hashwarp --help-all: A configuration file can replace the long command lines: --save-config hashwarp.json writes one from your options. See Configuration.

​
The output

The output is new: each line has its time, level and source, hashrates are written MH/s and difficulties GH, and a line is printed per share. See Output & Logs. Scripts that read 1.x’s output should read --log-format json or the API instead.

​
The API

  • The API listens only where --api-bind says, and on 127.0.0.1 with the 1.x option --api-port.
  • It is read only unless --api-allow-control is given; with 1.x’s --api-port, it is read only. Control on an address other than 127.0.0.1 requires --api-token.
  • The JSON-RPC methods of 1.x (miner_getstat1 …) still work, on the same port as the new JSON API, dashboard and Prometheus metrics.

​
New in 2.0

The full list is in the release notes.