BzMiner is a cryptocurrency miner and hardware monitor for Windows, Linux and macOS. It works with NVIDIA, AMD, Intel and Apple Silicon graphics processors, alongside CPU mining. The program is free to download, with no paid tier. Fee-bearing algorithms reserve portions of mining time for their developers.
Sending work to a pool
The user supplies an algorithm name, pool address and wallet, with optional worker identification and a pool password. BzMiner connects to the pool, processes its mining jobs and submits shares under that login. A configuration file accepts JSON settings or command-line options; explicit launch arguments override matching file settings.
Algorithm choices determine which processors participate. These examples differ in how they divide the work:
| Algorithm | Processing |
|---|---|
| XELIS | GPUs and CPU mine concurrently |
| Ergo | GPUs perform Autolykos mining |
| Verus | CPU performs VerusHash mining |
| Warthog | GPUs filter candidates; CPU checks matching nonces |
Dividing a rig’s processors
BzMiner selects graphics cards by device number or PCI address. Allow and deny lists include or exclude individual GPUs, while separate controls set CPU thread counts and processor affinity. GPU intensity controls how much work each launch performs.
One process can run several algorithms with separate pools, wallets and device assignments. For example, GPUs can mine Pearl while the CPU mines RandomX. Global device exclusions affect every algorithm; numbered controls affect only the corresponding algorithm. A separate NVIDIA route runs Pearl and Cuckaroo29 on the same graphics card, with a pool configuration for each.
Pool recovery and farm routing
BzMiner tries backup pools when the primary disconnects. Backups must use the same algorithm. It separately checks the failed primary, including protocol authorization, and returns when that connection works again. A SOCKS5 setting routes outbound pool connections through a proxy.
Its farm proxy distributes one pool’s jobs to other BzMiner rigs and forwards their shares through one upstream connection. The pool sees one worker, while the proxy shows individual rigs with their hashrates, power and share counts. The proxy can mine too, or only relay work. Both ends must use the same algorithm and BzMiner version.
Reading mining and sensor data
The BzMiner browser dashboard shows device hashrates, accepted and rejected shares, pool state and hardware readings. Clicking a metric opens its history chart. GPU views cover temperatures, clocks, fan speeds, power and PCIe activity when the hardware exposes those sensors.
Other views show CPU topology, memory-module timings and temperatures, and storage volumes. Monitor-only mode collects hardware readings without mining or requiring a pool and wallet. A Farm tab discovers local instances and totals their hashrates, power and shares. JSON endpoints expose these readings to other applications.
The dashboard accepts local connections by default and has no password. Console users can switch among a dashboard, scrolling log, sensor table and individual device pages. A hotkey pauses or resumes mining without closing BzMiner.
Controlling clocks and cooling
BzMiner applies tuning through configuration settings, console commands, hotkeys or the dashboard’s Tune panel. NVIDIA cards expose core and memory offsets, clock locks, power limits and fan controls. AMD cards expose fan controls only; Intel GPUs and CPUs offer no corresponding tuning controls.
Fan settings accept fixed speeds or temperature targets with permitted speed ranges. Per-card settings let different GPUs use different values. Optional safety thresholds pause an individual card after sustained excessive temperature or power. Recovery thresholds and timing determine when it resumes, while other cards continue mining. BzMiner restores its hardware changes when it exits normally.
Benchmarks without an external pool
BzMiner offers two local test modes. The basic mode creates work locally and exercises the algorithm without network connections. The benchmark mode starts an internal Stratum server and connects through the normal mining client.
That second mode includes authorization, job delivery, share submission and acceptance checks. It reports accepted, rejected and stale shares alongside mining rates. Users can change difficulty, job-refresh intervals, device selection and tuning settings. Neither mode needs a wallet or internet connection.
Serving a language model
BzMiner also loads language models from local folders or Hugging Face repository identifiers. It downloads absent models with resume support, then serves browser chat and an OpenAI-compatible API. Clients can request streaming replies, while settings select the execution device and context length.
The engine accepts compatible dense safetensors checkpoints from the Llama, Qwen and text-only Gemma families. It does not read GGUF, AWQ or CTranslate2 files, and it rejects mixture-of-experts architectures. When Pearl mining shares the card with inference, the default behavior pauses mining during each request and resumes between requests.
