How to mine
How to mine Monero, Zephyr and Salvium (RandomX)
CPU only. Huge pages, thread counts, and the memory it needs, on every platform.
- Algorithm
- RandomX, rx/0 (
-a randomx, alsoxmr,zeph,sal) - Mines on
- The CPU only
- Dev fee
- 1%
- Wallet
- The chain’s address: a Monero
4...address for XMR - Memory
- 2080 MB plus 2 MB per thread; huge pages help
- Launcher
start_randomxin the archive
RandomX was designed so that a GPU has no advantage over a CPU, and no GPU implementation of it is worth the power it draws, so this is a CPU-only algorithm everywhere. Monero is the chain it was written for; Zephyr and Salvium run the same stock rx/0 and mine the same way with a different pool and wallet.
Before you start
- A wallet on the chain you mine. A Monero address for XMR (95 characters, usually starting with
4); a Zephyr or Salvium address for those. - A pool. Monero pools that returned a job when this build shipped, TLS first:
stratum+ssl://gulf.moneroocean.stream:20128·stratum+tcp://gulf.moneroocean.stream:10128(MoneroOcean)stratum+ssl://pool.supportxmr.com:9000·stratum+tcp://pool.supportxmr.com:3333(SupportXMR)stratum+tcp://monero.herominers.com:1111(HeroMiners)stratum+tcp://pool.hashvault.pro:3333(HashVault)
- A CPU with AES instructions. Anything from the last decade. Without them RandomX runs roughly four times slower, and bzminer says so at startup.
- Memory. 2080 MB for the dataset plus 2 MB per mining thread. If that does not fit, the miner drops to a much slower low-memory mode and tells you.
The command
./bzminer \
-a randomx \
-p stratum+ssl://gulf.moneroocean.stream:20128 \
-w 4YOUR_MONERO_WALLET \
--worker rig1-a randomx— the algorithm.rx/0,xmrandmoneromean the same thing;zeph,zephyr,salandsalviumalso select it, and exist so a config that names the coin works.-p— the pool. A second-pis a backup.-w— the address, and only the address. bzminer joins the worker name on with a dot; a placeholder that already carries.workerends up with two suffixes, and MoneroOcean accepts that silently, so the mistake is easy to miss.--worker rig1— the rig’s name. Avoid+in it; MoneroOcean reads a plus sign in the login as its own difficulty separator.
Zephyr, for example, is the same line with that chain’s pool and address:
./bzminer -a zeph -p stratum+ssl://YOUR_ZEPHYR_POOL:PORT -w ZEPHYR_ADDRESS --worker rig1Step by step, on your platform
Pick your platform. The steps are the same shape everywhere: get the archive, put your wallet in the launcher, run it, open the dashboard. Only the details change.
Huge pages are worth about ten percent. On Windows the account running bzminer needs the Lock pages in memory right (Local Security Policy → Local Policies → User Rights Assignment), and a reboot after granting it. The startup line says whether it got them. CPU register tweaks are a further optional speed-up and use the PawnIO driver from install-pawnio.bat in the archive.
-
Download and unzip
Get
bzminer_v100.82_windows.zipfrom the release page and unzip it anywhere you like — a folder on the desktop is fine. There is no installer and nothing is written outside that folder except the log. The SHA-256 of the archive is published beside it if you want to check the download. -
Put your wallet in the launcher
Right-click
start_randomx.bat, choose Edit, and replace the placeholder wallet with your own. The pool is already filled in; other pools are listed as commented-out lines in the same file. Save it. -
Run it
Double-click the launcher. The console dashboard opens in a window. Or, from a command prompt in that folder, the same thing by hand:
bzminer.exe -a randomx -p stratum+ssl://gulf.moneroocean.stream:20128 -w 4YOUR_MONERO_WALLET --worker rig1Windows Terminal is the better console for it: the old
conhostwindow cannot scroll the log pane with the mouse wheel and select text at the same time. Everything still works in the old console; it is just less convenient. -
Open the dashboard
Browse to
http://127.0.0.1:4014/on the same machine. Nothing to install and nothing to sign in to.
Overclocking on Windows needs no special privileges for the power limit and the fan, and no
administrator prompt to mine. CPU register tweaks that speed up some CPU algorithms are optional
and use the PawnIO driver; install-pawnio.bat is in the archive for that, and mining
carries on without it.
Reserve huge pages first. RandomX wants 2080 MB for its dataset plus 2 MB per mining thread, and huge pages make that about ten percent faster:
sudo sysctl -w vm.nr_hugepages=1280The startup line says which it got. Two more Linux-only gains need root: CPU register tweaks (MSR), which want the msr module and access to /dev/cpu/*/msr, and cache partitioning, on by default, which reserves a private slice of the last-level cache for each mining thread on CPUs that support it (AMD Zen 2 and newer, Intel with RDT). RandomX’s 2 MiB scratchpads add up to about the L3 on a typical rig, so left alone they evict one another; fencing them off measured a few percent on a Threadripper. --cache-qos 0 turns it off.
-
Download and unpack
wget https://github.com/bzminer/bzminer/releases/download/v100.82/bzminer_v100.82_linux.tar.gz tar -xzf bzminer_v100.82_linux.tar.gz cd bzminer_v100.82_linuxA single static binary; no packages to install, and no CUDA toolkit or OpenCL SDK. The GPU driver is the only thing it needs from the system.
-
Put your wallet in the launcher
Open
start_randomx.shin any editor and replace the placeholder wallet. Other pools are in the same file as commented-out lines. -
Run it
./start_randomx.shOr the same command written out, which is all the launcher does:
./bzminer \ -a randomx \ -p stratum+ssl://gulf.moneroocean.stream:20128 \ -w 4YOUR_MONERO_WALLET \ --worker rig1If you redirect the output to a file or run it under a service manager, bzminer notices there is no terminal and switches to the plain scrolling
logscreen on its own, so the file is readable rather than full of cursor codes. -
Open the dashboard
http://127.0.0.1:4014/on the rig itself. To see it from another machine on your network, add--set http_address=0.0.0.0to the command — there is no password on it, so only do that on a network you trust.
Overclocking on Linux is privileged. Every clock, power and fan change is a driver write
that needs root, so run the miner with sudo when you use the --oc-*
flags. Without root the run still mines; each refused knob is named in the log with the reason.
CPU only, as everywhere. Apple Silicon has the AES instructions RandomX wants, so an M-series chip is a respectable RandomX miner.
-
Download, unpack, clear the quarantine flag
tar -xzf bzminer_v100.82_macos.tar.gz cd bzminer_v100.82_macos xattr -dr com.apple.quarantine .The build is not signed with an Apple Developer ID, so macOS refuses to open it until the quarantine flag is cleared. That last line does it once, for the whole folder. The archive is Apple Silicon only; it does not run on Intel Macs.
-
Put your wallet in the launcher
Open
start_randomx.shin TextEdit or any editor and replace the placeholder wallet. -
Run it
./start_randomx.shOr written out:
./bzminer \ -a randomx \ -p stratum+ssl://gulf.moneroocean.stream:20128 \ -w 4YOUR_MONERO_WALLET \ --worker rig1 -
Open the dashboard
http://127.0.0.1:4014/in Safari or any browser on the Mac.
On a Mac the GPU is reached through Metal, and only algorithms with a Metal kernel use it: Ergo, KawPow, Ethash, Pearl, Warthog and CryptoNight. XELIS, RandomX and Verus mine on the CPU there. There is no overclocking on macOS.
Hive rigs are usually GPU boxes. RandomX uses only the CPU, so this is what to run beside a GPU coin — see mining two algorithms at once. For Zephyr or Salvium, put zeph or sal in the algorithm box and that chain’s pool and wallet in the flight sheet.
The clean way is Hive’s custom miner mechanism, which installs the current bzminer straight from the release page and lets you type any algorithm name. The Hive OS and mmpOS guide has the detail and the alternative of updating Hive’s own bzminer entry in place.
-
Make a flight sheet
Coin, wallet and pool as usual. For the miner pick Custom, then open Setup Miner Config.
-
Fill in the custom miner form
Miner name bzminer_customInstallation URL https://github.com/bzminer/bzminer/releases/download/v100.82/bzminer_custom-v100.82.tar.gzHash algorithm randomxWallet and worker template %WAL%— just the wallet. Hive passes the rig name separately and bzminer joins the two itself, so a template with a worker in it would name the worker twice.Pool URL stratum+ssl://gulf.moneroocean.stream:20128— a barehost:portmeans plain stratum; writestratum+ssl://host:portin full for TLSPass xExtra config arguments Any bzminer flag, on one line — overclocks, --devices,--cpu_threads. -
Apply it to the rig
Hive downloads the package on first start. Hashrate, temperatures and shares appear on the Hive dashboard because bzminer serves Hive’s stats format itself on port 4014, so leave the web server on its default port.
mmpOS ships a bzminer miner profile. What it does not ship is the current version, so the profile
gets a one-time download script, and any algorithm its own list does not know is reached with
--force_algo.
-
Create a miner profile
Miner bzminer, the coin or algorithm, your pool and wallet. The rig name becomes the worker name.
-
Install the current version
In the profile, under Advanced, paste this into “Initiate command prior to miner launch”. It downloads v100.82 once and exits immediately on every later launch, so it costs nothing per restart. To move to a later release, change the version on the first line.
export version="v100.82" if [ -f "/tmp/bzminer_${version}_linux.tar.gz" ]; then exit 0 else cd /tmp; wget https://github.com/bzminer/bzminer/releases/download/${version}/bzminer_${version}_linux.tar.gz; tar -xvf bzminer_${version}_linux.tar.gz; sudo cp -adpR bzminer_${version}_linux/bzminer /opt/mmp/miners/bzminer/ fi -
Name the algorithm if the list lacks it
If
randomxis not among the algorithms mmpOS offers for bzminer, pick any and add--force_algo randomxto the profile’s extra arguments. It overrides whatever the OS wrote into the pool block, which is exactly what it is for. -
Assign the profile to the rig
Stats come from bzminer’s own web port, so keep the web server enabled on 4014.
What you should see
The startup lines tell you the three things that decide RandomX speed: whether the full dataset
was allocated, whether it got huge pages, and how many threads are mining. Then the hashrate
settles within a minute. The CPU row in the device table shows t16-style
configuration in its cfg column: the number of threads actually mining.
Tuning
Thread count matters more here than on any other algorithm. Each thread wants a 2 MB
scratchpad resident in cache, so past roughly L3 size ÷ 2 MB the threads
compete and the rig gets slower, not faster. Start from the auto value, then try one or two
steps in each direction with the t / T keys while watching the hashrate:
./bzminer -a randomx -p stratum+ssl://gulf.moneroocean.stream:20128 -w 4YOUR_MONERO_WALLET \
--cpu_threads 12
# or name the processors outright, leaving the rest for everything else
./bzminer -a randomx ... --cpu_affinity 0-11By default bzminer holds one or two threads back so the machine stays responsive; a dedicated rig can have them all. Huge pages are the other lever (see your platform’s tab above). There is no clock or voltage control for the CPU in bzminer.
On a machine with GPUs, RandomX is what the CPU can do while the cards mine something else. One process, two algorithms:
./bzminer -a kawpow,randomx \
--p1 stratum+tcp://gulf.moneroocean.stream:10128 --w1 4YOUR_MONERO_WALLET --pass1 "rig1~kawpow" \
--p2 stratum+ssl://gulf.moneroocean.stream:20128 --w2 4YOUR_MONERO_WALLET
KawPow cannot use the CPU, so nothing needs saying about who gets it. Pair RandomX with an
algorithm that can — XELIS, Pearl or CryptoNight — and the CPU is shared between
the two by default. To give RandomX all of it, keep the other algorithm off the CPU with its own
number: --cpu1 0. Not --cpu 0, which is rig-wide and stops RandomX too. The
devices and multi-algo guide explains the numbered flags.
Problems
- It is slow and the startup line says no huge pages. Set them up as described in your platform’s tab above; they are worth about ten percent.
- It is slow and the log mentions light mode. The 2 GB dataset did not fit. Close whatever is holding memory; the fallback runs from a 256 MB cache and is about twenty times slower.
- MoneroOcean refuses the login. There is a
/or+in the worker name, or the wallet is not a 95-character Monero address. Pressuto see what was sent. - A message about MSR tweaks. Those tweaks are an optional speed-up. Mining carries on without them; they need PawnIO on Windows or the
msrmodule on Linux.
More in the troubleshooting guide.