How to mine

Profit switching

MoneroOcean solo switching, experimental measured dual selection, independent device lists and reusable OC profiles.

What it is
An auto-switching pool that takes several algorithms and pays everything in XMR
Pool
gulf.moneroocean.stream, port 10128 plain or 20128 TLS
Wallet
A Monero address, whatever you mine
Password
Plain worker name for switching; worker~algorithm for fixed mining
Main example
Pearl, CryptoNight-GPU and C29 on GPUs; RandomX on CPU

Use -a mo (or moneroocean) to let MoneroOcean choose the most profitable algorithm from those you offer. BzMiner measures the supported algorithms, advertises their rates, and follows the pool's jobs. Payouts use your Monero wallet. By default each connection gets one algorithm at a time. Add --mo-dual for experimental measured solo/dual selection on GPUs.

For setup help and tuning discussion, join the bzminer Discord.

Automatic solo/dual selection: --mo-dual

--mo-dual freshly benchmarks solo algorithms, ranks them by current MoneroOcean payout factors after algorithm fees, then measures the pair of the top two concurrently. It selects a measured pair only when its expected payout beats the best solo by the configured gain threshold. Otherwise it mines solo.

./bzminer -a mo -p stratum+tcp://gulf.moneroocean.stream:10128 -w 4YOUR_MONERO_WALLET --pass rig1-gpu --devices1 gpu --mo-algos1 pearl,cn/gpu,c29 --mo-dual

Equivalent complete config.txt:

{
  "mo": {"dual_top":2,"dual_seconds":30,"dual_gain_percent":3,"min_time_seconds":120},
  "pools": [
    {"algo":"mo","url":"stratum+tcp://gulf.moneroocean.stream:10128","wallet":"4YOUR_MONERO_WALLET","pass":"rig1-gpu","devices":"gpu","mo_algos":"pearl,cn/gpu,c29"}
  ]
}
  • Shortlist: bare --mo-dual means the top two, producing one pair. --mo-dual 3 tests three unordered pairs among the top three. The allowed shortlist is 2–6 (mo.dual_top); zero disables it.
  • Devices: GPU connections only, with the same physical-device roster for both algorithms in a tested pair. CPU connections keep pool-controlled solo switching. Use one mo connection per card for independent decisions.
  • Fresh measurements: every startup measures solos and each pair between solo controls: A, B, A+B, A, B. Solo rates are never added to invent a paired rate. Controls drifting more than 3% reject that pair. Saved pair reports do not replace fresh calibration.
  • Time: mo.dual_seconds defaults to a 30-second measured window after warmup: 20 seconds ordinarily, 90 for C29, 120 for OpenCL. Loading kernels and first work add time. Expect many minutes; six candidates permit fifteen pairs and can take hours. Fan curves and configured sustained safety limits apply during calibration.
  • Clocks: CN/GPU starts after its companion produces work. The non-CN companion owns the shared card’s OC and fan profile; other pairs use deterministic algorithm-name order. A physical GPU has one clock configuration.
  • Switching: mo.dual_gain_percent defaults to 3%, and mo.min_time_seconds defaults to a 120-second residence time. A selected pair uses two independent pinned pool sessions. The controller re-evaluates measured modes as public pool pricing changes.
  • Fallback: pricing refreshes every 60 seconds; quotes older than 300 seconds disable pairs. Missing startup prices fall back to pool-controlled solo switching. Failed sessions trigger another mode or park hashing while retrying. External OC or intensity changes disable pairs until fresh startup calibration.
  • Report: mo-dual-perf.json records concurrent rates, solo controls and the clock owner. Change its path with mo.dual_report.
Note

Experimental and off by default. These are relative payout estimates before electricity costs, not guaranteed profit. Physical GPU correctness and profitability qualification remain pending. Include only algorithms supported by your cards and available VRAM.

Separate GPU and CPU mining

GPU-only switching between Pearl, CryptoNight-GPU and C29:

./bzminer -a mo -p stratum+tcp://gulf.moneroocean.stream:10128 -w 4YOUR_MONERO_WALLET --pass rig1-gpu --devices1 gpu --mo-algos1 pearl,cn/gpu,c29

CPU-only RandomX through the switching protocol:

./bzminer -a mo -p stratum+tcp://gulf.moneroocean.stream:10128 -w 4YOUR_MONERO_WALLET --pass rig1-cpu --devices1 cpu --mo-algos1 randomx

With only randomx offered, the CPU stays on RandomX. To mine GPU and CPU work together, use separate connections with separate device selectors and lists:

./bzminer -a mo,mo --p1 stratum+tcp://gulf.moneroocean.stream:10128 --w1 4YOUR_MONERO_WALLET --pass1 rig1-gpu --devices1 gpu --mo-algos1 pearl,cn/gpu,c29 --p2 stratum+tcp://gulf.moneroocean.stream:10128 --w2 4YOUR_MONERO_WALLET --pass2 rig1-cpu --devices2 cpu --mo-algos2 randomx

Use plain worker passwords for switching. Do not add a ~algorithm pin: that is for fixed mining and is stripped in mo mode. These commands are single lines; use bzminer.exe on Windows and ./bzminer on Linux/macOS.

Different algorithms on different GPUs

Give each independently switching GPU or group its own mo connection. GPU 0 below offers pearl,cn/gpu,c29, GPU 1 offers only pearl,cn/gpu, and the CPU offers randomx. Their pool choices are independent. Cards sharing one connection have their rates summed and follow the same choice. Use disjoint devices; overlapping switching assignments are rejected.

Only offer algorithms supported by the selected GPUs, installed plugins and available VRAM. An algorithm list does not add hardware support. In particular, include C29 only on cards with enough available VRAM. Replace the sample PCI IDs with those shown in your miner's device table.

Save this as config.txt and run bzminer --config config.txt. The NVIDIA OC values illustrate the configuration; use settings tested on your cards.

{
  "pools": [
    {"algo":"mo","url":"stratum+tcp://gulf.moneroocean.stream:10128","wallet":"4YOUR_MONERO_WALLET_HERE","worker":"","pass":"rig1-gpu0","devices":"0000:23:00","mo_algos":"pearl,cn/gpu,c29"},
    {"algo":"mo","url":"stratum+tcp://gulf.moneroocean.stream:10128","wallet":"4YOUR_MONERO_WALLET_HERE","worker":"","pass":"rig1-gpu1","devices":"0000:25:00","mo_algos":"pearl,cn/gpu"},
    {"algo":"mo","url":"stratum+tcp://gulf.moneroocean.stream:10128","wallet":"4YOUR_MONERO_WALLET_HERE","worker":"","pass":"rig1-cpu","devices":"cpu","mo_algos":"randomx"}
  ],
  "oc_profiles": {
    "gpu0": {
      "oc": {"power_limit":"150"},
      "oc_algos": {
        "pearl":  {"lock_core_clock":"1200","lock_memory_clock":"810"},
        "cn/gpu": {"lock_core_clock":"1050"},
        "c29":    {"lock_core_clock":"1200"}
      }
    },
    "gpu1": {
      "oc": {"power_limit":"140"},
      "oc_algos": {
        "pearl":  {"lock_core_clock":"1350","lock_memory_clock":"810"},
        "cn/gpu": {"lock_core_clock":"1100"}
      }
    }
  },
  "devices": [
    {"pci":"0000:23:00","oc_profile":"gpu0"},
    {"pci":"0000:25:00","oc_profile":"gpu1"}
  ]
}

The equivalent command loads a file named independent-oc-profiles.txt containing just the oc_profiles object from the config above:

./bzminer --config independent-oc-profiles.txt -a mo,mo,mo --p1 stratum+tcp://gulf.moneroocean.stream:10128 --w1 4YOUR_MONERO_WALLET_HERE --pass1 rig1-gpu0 --devices1 0000:23:00 --mo-algos1 pearl,cn/gpu,c29 --p2 stratum+tcp://gulf.moneroocean.stream:10128 --w2 4YOUR_MONERO_WALLET_HERE --pass2 rig1-gpu1 --devices2 0000:25:00 --mo-algos2 pearl,cn/gpu --p3 stratum+tcp://gulf.moneroocean.stream:10128 --w3 4YOUR_MONERO_WALLET_HERE --pass3 rig1-cpu --devices3 cpu --mo-algos3 randomx --oc-profile 0000:23:00=gpu0 --oc-profile 0000:25:00=gpu1

For one GPU, remove the second GPU pool and its device entry. For GPU-only mining, remove the CPU pool. For CPU-only config, retain just the CPU pool and omit oc_profiles and devices.

Reusable OC profiles

Define named presets in oc_profiles. A profile's oc provides base settings; its oc_algos overrides those fields for the active algorithm. Select a default with --oc-profile NAME or top-level oc_profile, and per-card choices with --oc-profile PCI=NAME or devices[].oc_profile. Names use letters, digits and underscores; unknown names are errors.

Settings apply in this order: global oc, global algorithm settings, default profile base and algorithm settings, card profile base and algorithm settings, then explicit per-card OC fields. Later specified fields win. Power limits are watts; clocks and offsets are MHz. Supported controls depend on the GPU, driver and permissions. CPU connections leave GPU controls alone.

In the example, GPU 0 uses 150 W, core 1200 MHz and memory 810 MHz for Pearl. On cn/gpu, it uses 150 W and core 1050 MHz; the old Pearl memory lock is cleared with the default automatic reset policy. A switch resets and applies OC only to its own GPUs. GPU 1 retains its independent profile. Profiles also apply during calibration, so the advertised rate reflects that algorithm's OC.

To preserve external overclocks, use --oc-reset false or "oc":{"reset":false} in config.txt. Explicit OC values you configure still apply. In a selected dual mode, the clock owner’s profile applies to the shared card.

For default solo switching, rates are cached in mo-perf.json by PCI ID and OC settings. Missing or OC-mismatched rates are measured on startup. Changing a profile remeasures affected card/algorithm entries. --mo-benchmark-seconds 0 offers only matching cached rates; it skips measurement. --mo-min-time 120 asks the pool to wait 120 seconds between choices. Manual --benchmark and --bench cannot combine with switching.

To define a profile from the CLI, use --set oc_profiles.eco.oc.power_limit=150 and --set oc_profiles.eco.oc_algos.pearl.lock_memory_clock=810, then select it with --oc-profile eco. You can change between saved profiles by selecting a different name instead of repeating every OC field.

Use the same profiles without switching

Profiles work with fixed algorithms too. This command loads the same profile library and keeps GPU 0 on Pearl:

./bzminer --config independent-oc-profiles.txt -a pearl -p stratum+tcp://gulf.moneroocean.stream:10128 -w 4YOUR_MONERO_WALLET_HERE --pass rig1-gpu0~pearl --devices1 0000:23:00 --oc-profile 0000:23:00=gpu0

For config.txt, keep oc_profiles and devices, change that GPU pool's algo to pearl, remove its mo_algos and set pass to rig1-gpu0~pearl. A fixed CPU pool uses algo: "randomx", devices: "cpu", password rig1-cpu~rx/0, and no mo_algos. Fixed and switching pools can run together on separate devices.

Fixed-algorithm password pins

The remaining examples and platform tabs use fixed algorithms. Their passwords use worker~algorithm to request matching work from MoneroOcean. For example, --pass rig1~kawpow pins KawPow, while --pass rig1~cn/gpu pins CryptoNight-GPU. Keep these pins out of switching connections.

The wallet, the ports, the worker name

  • The wallet is a Monero address for everything — 95 characters, usually starting with 4. Not an Ergo address for Autolykos, not an ETC address for etchash. MoneroOcean validates it and refuses anything else.
  • Ports. stratum+tcp://gulf.moneroocean.stream:10128 is plain; stratum+ssl://gulf.moneroocean.stream:20128 is TLS. The TLS port serves a self-signed certificate, so leave --ssl-verify off; the login is still encrypted.
  • The worker name goes on with --worker and bzminer sends wallet.worker. Avoid + and / in it: MoneroOcean reads a plus sign as its own difficulty separator and refuses a slash as part of the address. Letters, digits and dashes are safe.

More fixed-algorithm examples

Mine-aPinRuns onVerified
RandomX (Monero’s own)randomx~rx/0CPUEvery Monero pool listed in the RandomX guide
KawPow (any KawPow coin)kawpow~kawpowGPURTX 4090: 57.4 MH/s, 9 of 9 shares accepted
Autolykos2 (Ergo’s algorithm)ergo~autolykos2GPURTX 4090: 238 MH/s, 10 of 10 accepted
etchash (Ethereum Classic’s)etchash~etchashGPUProbed and served; unpinned it was handed KawPow
CryptoNight-GPU (Conceal, Ryo)cn or cn/gpu~cn/gpu (required)GPU and CPURTX 6000 Ada: 6.32 kH/s, 11 of 11 accepted

RandomX, on the CPU

./bzminer -a randomx -p stratum+ssl://gulf.moneroocean.stream:20128 \
  -w 4YOUR_MONERO_WALLET --worker rig1 --pass "rig1~rx/0"

RandomX is Monero’s algorithm, and bzminer’s login already names rx/0, so this one works without the pin; it is there for consistency and costs nothing. The RandomX guide covers huge pages and thread counts.

KawPow, on the GPUs

./bzminer -a kawpow -p stratum+tcp://gulf.moneroocean.stream:10128 \
  -w 4YOUR_MONERO_WALLET --pass "rig1~kawpow"

MoneroOcean picks which KawPow coin, so the name is the plain kawpow rather than a coin. Expect a DAG rebuild when the pool changes chain. See the KawPow guide.

Autolykos2, on the GPUs

./bzminer -a ergo -p stratum+tcp://gulf.moneroocean.stream:10128 \
  -w 4YOUR_MONERO_WALLET --pass "rig1~autolykos2"

The 2 GB table still has to fit in VRAM. See the Ergo guide.

etchash, on the GPUs

./bzminer -a etchash -p stratum+tcp://gulf.moneroocean.stream:10128 \
  -w 4YOUR_MONERO_WALLET --pass "rig1~etchash"

See the Ethash guide for DAG sizes.

CryptoNight-GPU, on GPUs and CPU

./bzminer -a cn -p stratum+ssl://gulf.moneroocean.stream:20128 \
  -w 4YOUR_MONERO_WALLET --pass "rig1~cn/gpu"

The pin is mandatory here; without it the login is refused. See the CryptoNight guide.

GPUs on one, CPU on the other, one wallet

A fixed-algorithm whole-rig setup. Every pool flag takes the algorithm’s number:

./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 --pass2 "rig1~rx/0"

Both show up under the same wallet on MoneroOcean’s stats page, as two workers.

Step 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.

  1. Download and unzip

    Get bzminer_v100.82_windows.zip from 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.

  2. 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.

  3. 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 rig1 --pass "rig1~rx/0"

    Windows Terminal is the better console for it: the old conhost window 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.

  4. 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.

  1. 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_linux

    A 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.

  2. Put your wallet in the launcher

    Open start_randomx.sh in any editor and replace the placeholder wallet. Other pools are in the same file as commented-out lines.

  3. Run it

    ./start_randomx.sh

    Or 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 rig1 \
      --pass "rig1~rx/0"

    If 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 log screen on its own, so the file is readable rather than full of cursor codes.

  4. 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.0 to 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.

  1. 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.

  2. Put your wallet in the launcher

    Open start_randomx.sh in TextEdit or any editor and replace the placeholder wallet.

  3. Run it

    ./start_randomx.sh

    Or written out:

    ./bzminer \
      -a randomx \
      -p stratum+ssl://gulf.moneroocean.stream:20128 \
      -w 4YOUR_MONERO_WALLET \
      --worker rig1 \
      --pass "rig1~rx/0"
  4. 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.

Note

The example is RandomX on the CPU. For a GPU algorithm, put kawpow, ergo, etchash or cn in the algorithm box and the matching pin (rig1~kawpow, rig1~autolykos2, rig1~etchash, rig1~cn/gpu) in the Pass field. The wallet is always a Monero address.

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.

  1. Make a flight sheet

    Coin, wallet and pool as usual. For the miner pick Custom, then open Setup Miner Config.

  2. Fill in the custom miner form

    Miner namebzminer_custom
    Installation URLhttps://github.com/bzminer/bzminer/releases/download/v100.82/bzminer_custom-v100.82.tar.gz
    Hash algorithmrandomx
    Wallet 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 URLstratum+ssl://gulf.moneroocean.stream:20128 — a bare host:port means plain stratum; write stratum+ssl://host:port in full for TLS
    Passrig1~rx/0
    Extra config argumentsAny bzminer flag, on one line — overclocks, --devices, --cpu_threads.
  3. 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.

Note

Whatever the algorithm, the wallet is a Monero address and the pool password carries the ~algorithm pin. If mmpOS does not offer the algorithm, --force_algo names it.

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.

  1. Create a miner profile

    Miner bzminer, the coin or algorithm, your pool and wallet. The rig name becomes the worker name.

  2. 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
  3. Name the algorithm if the list lacks it

    If randomx is not among the algorithms mmpOS offers for bzminer, pick any and add --force_algo randomx to the profile’s extra arguments. It overrides whatever the OS wrote into the pool block, which is exactly what it is for.

  4. Assign the profile to the rig

    Stats come from bzminer’s own web port, so keep the web server enabled on 4014.

A note on the dev fee

Several of bzminer’s dev fees are also collected at MoneroOcean, for the same reason you might mine there: one destination that takes the family and cannot be stranded by a single chain’s pool going down. A fee slice on KawPow therefore mines MoneroOcean’s current KawPow coin rather than yours, which costs a few seconds of DAG rebuild each way. The dev fee guide has the whole picture.

Problems

  • No work yet. Check connection logs and calibration progress. For a fixed-algorithm connection, verify its password pin; a switching connection uses a plain worker password. The pool may also be waiting for work from a chain.
  • “Invalid payment address provided.” The wallet is not a Monero address, or the worker name contains /.
  • Connected without accepted shares. Check the selected algorithm, available memory, pool difficulty and rejection messages. Check the password pin for fixed mining, or the offered algorithms and cached rates for switching.
  • The TLS port fails with a certificate error. --ssl-verify is on. MoneroOcean’s certificate is self-signed; turn it off for this pool.