OneZeroMiner

OneZeroMiner is a closed-source command-line GPU miner for NVIDIA cards, with AMD support for some algorithms. Its users are miners chasing newer coins such as Dynex, Xelis, Qubitcoin and PearlHash-based projects, which the big general-purpose miners cover late or not at all. If you searched for “onezerominer”, this page sums up what the current build supports, what it costs in dev fee and how to get it running.

The project’s domain onezerominer.com now redirects to its GitHub repository, which holds the README, the option list and the releases for Windows, Linux and mining operating systems such as Hive OS and mmpOS.

OneZeroMiner at a glance

What it does

• Mines six algorithms on NVIDIA GPUs and XelisHashV3 on AMD GPUs as well.
• Dual mining: the README lists a XelisHash plus qhash pair on NVIDIA, with per-GPU dual intensity settings.
• Per-GPU tuning from the command line: absolute core and memory clocks, clock offsets, fan speed and power limit, with separate values for the second algorithm when dual mining.
• Dynex-specific tuning parameters (–nt and –nr) and a Mallob endpoint option; a second kernel for qhash aimed at CMP cards.
• ZIL support with before and after scripts and a built-in test pool for checking overclock settings.
• Xelis solo mining mode, SSL pools, SOCKS5 proxy and DNS-over-HTTPS.
• Local HTTP API (127.0.0.1:3001 by default) and log-file output for monitoring.

How miners use it

Mine XelisHashV3 to a pool

1. Unpack the archive for your OS.
2. Run the miner with algorithm, pool, wallet and worker. In OneZeroMiner, -w is the wallet and –worker is the rig name.

onezerominer -a xelishashv3 -o pool.example.com:3333 -w YOUR_WALLET_ADDRESS --worker rig01

For an encrypted connection, prefix the pool with ssl:// or stratum+ssl://. Add –disable-amd or –disable-nvidia on mixed rigs if you want only one vendor to mine.

Tune NVIDIA cards from the miner

1. Pick the device order with -d (comma-separated indices).
2. Give per-GPU lists for clocks and power; an asterisk skips a card.

onezerominer -a qhash -o pool.example.com:3333 -w YOUR_WALLET_ADDRESS --worker rig01 --cclk 1500,* --mclk 5000,* --pl 150,*

The numbers are placeholders. Find stable values for each card yourself and change one setting at a time.

Run it in Hive OS or mmpOS

1. In the flight sheet, choose the custom miner option.
2. Use the onezerominer-x.x.x.tar.gz package from the release, as the README specifies for Hive OS and mmpOS.
3. Put the algorithm and any extra flags in the custom configuration, then check the miner log after the first start.

Install and first run

Windows: extract the win64 ZIP into its own folder. The README requires the latest Microsoft Visual C++ Redistributable, and NVIDIA cards need driver 528.33 or newer, because the binary is built with CUDA 12.8. Write your command into a .bat file so the settings survive a restart.

Linux: use the linux tar.gz build. NVIDIA cards need a driver that supports CUDA 12.8; AMD cards need ROCm 5.6 or newer, and on AMD only XelisHashV3 is supported.

The miner sends usage analytics by default; add –disable-telemetry if you do not want that. As with any miner, antivirus software may label OneZeroMiner as potentially unwanted, because mining code is often misused in malware. Download only from the official GitHub releases and confirm the file matches the release page before making a folder exception. Mine only on hardware you own or have permission to use. Clock and power changes can crash a rig; note your stock settings first.

Limitations

• Closed source from a pseudonymous team, with a developer fee of 1% to 3% depending on the algorithm (0% on ZIL).
• Narrow focus: six algorithms, and the list changes as coins appear and fade. Classic coins such as KawPow or Autolykos are not supported.
• AMD support covers only XelisHashV3.
• PearlHash support is new: as of 1.7.5 it covers RTX 20, 30 and 40 series, with newer cards promised for a later release.
• There is no graphical interface; you work on the command line or through a mining OS.
• Telemetry is on unless you switch it off.
• Small-coin mining is volatile: rewards depend on electricity cost, network difficulty and a coin price that can move sharply.

OneZeroMiner vs alternatives

Rigel is the broader NVIDIA miner, with 16 algorithms, dual and triple mining and a terminal UI. It overlaps with OneZeroMiner on XelisHashV3 and ZIL, while OneZeroMiner covers Dynex, Qubitcoin and PearlHash, which Rigel does not list. GMiner supports NVIDIA and AMD on older algorithms but has not been updated since early 2024. To run several of these miners across many rigs, manage them from a mining OS such as Hive OS.

FAQ

Where do I get the OneZeroMiner download?

OneZeroMiner is published on its official GitHub releases page, and onezerominer.com redirects there. Each release has a Windows ZIP, a Linux tar.gz and a package for mining operating systems.

Does OneZeroMiner work on Windows?

Yes. A 64-bit Windows build ships with every release. It needs the Visual C++ Redistributable and a recent NVIDIA driver.

Which algorithms does OneZeroMiner support?

Currently dynex, xelishashv3, cryptix_ox8, qhash, pearlhash and zil. Only xelishashv3 runs on AMD.

What is the OneZeroMiner dev fee?

The README lists 1% for pearlhash, 2% for dynex, xelishashv3 and cryptix_ox8, 3% for qhash and 0% for zil.

Is OneZeroMiner safe?

It is closed source from an anonymous team, like most GPU miners. Use only the official release files, check them against the release page and avoid running it on a PC that holds sensitive data.

OneZeroMiner vs Rigel: which is better?

Neither one is better across the board. Pick by algorithm: OneZeroMiner for Dynex, Qubitcoin or PearlHash, Rigel for a wider range of NVIDIA algorithms and dual mining.

Is mining with OneZeroMiner profitable?

That depends on your electricity price, GPU efficiency and the price of the coin you mine, which for young coins can swing a lot. Check current numbers for your own setup first.

Last checked against official sources: 1 October 2026 (developer website: github.com). Versions and licence terms change — confirm on the developer's site before deploying in production.