How to mine

How to mine Pearl

A zk proof-of-work: every share is a STARK proof. Why the hashrate looks small, and how to mine solo.

Algorithm
Pearl zk proof-of-work (-a pearl, or -a pearlhash)
Mines on
NVIDIA, AMD, Intel and Apple GPUs, and the CPU
Dev fee
1%
Wallet
Starts with prl1
Solo mining
Yes, against your own node’s RPC
Launcher
start_pearl in the archive

Pearl is a zero-knowledge proof-of-work: every share is a STARK proof. That makes each share enormously heavier than a hash on any other algorithm here — a proof is about 140 KB on the wire — and it changes how the numbers read. The hashrate looks tiny next to KawPow or Ergo, and that is by design rather than a fault: a small number is what a heavy proof per share looks like. Judge Pearl by accepted shares, which is what the pool pays for.

Before you start

  • A Pearl wallet address, starting with prl1.
  • A pool. Three that have been mined from this build:
    • stratum+tcp://us.pearl.herominers.com:1200 (HeroMiners)
    • stratum+tcp://prl-us.kryptex.network:7048 (Kryptex — takes a Kryptex account name or a wallet; bzminer knows Kryptex wants wallet/worker rather than wallet.worker and sends the right one)
    • stratum+tcp://pearl-cpu-eu1.luckypool.io:3370 (LuckyPool, EU)
  • Any GPU, any CPU. The GPU does the search and the CPU proves the results; both take part on every rig.

The command

./bzminer \
  -a pearl \
  -p stratum+tcp://us.pearl.herominers.com:1200 \
  -w prl1YOUR_WALLET \
  --worker rig1
  • -a pearl — the algorithm. -a pearlhash is the same thing: several mining operating systems spell it that way in their own lists, so bzminer answers to both.
  • -p — the pool, or your own node for solo mining (below).
  • -w — your prl1 address.
  • --worker rig1 — the rig’s name on the pool.

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_pearl.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 pearl -p stratum+tcp://us.pearl.herominers.com:1200 -w prl1YOUR_WALLET --worker rig1

    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_pearl.sh in any editor and replace the placeholder wallet. Other pools are in the same file as commented-out lines.

  3. Run it

    ./start_pearl.sh

    Or the same command written out, which is all the launcher does:

    ./bzminer \
      -a pearl \
      -p stratum+tcp://us.pearl.herominers.com:1200 \
      -w prl1YOUR_WALLET \
      --worker rig1

    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.

Note

Pearl uses the Apple Silicon GPU through Metal and the CPU. Both halves are on the one chip, so an M-series Mac is a complete Pearl rig on its own.

  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_pearl.sh in TextEdit or any editor and replace the placeholder wallet.

  3. Run it

    ./start_pearl.sh

    Or written out:

    ./bzminer \
      -a pearl \
      -p stratum+tcp://us.pearl.herominers.com:1200 \
      -w prl1YOUR_WALLET \
      --worker rig1
  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.

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 algorithmpearl
    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 URLus.pearl.herominers.com:1200 — a bare host:port means plain stratum; write stratum+ssl://host:port in full for TLS
    Passx
    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.

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 pearl is not among the algorithms mmpOS offers for bzminer, pick any and add --force_algo pearl 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.

What you should see

The GPU finds candidates and the CPU turns them into proofs, so the CPU is busy on a Pearl rig even though the search runs on the card. The share count climbs slowly and steadily; the tbs column (measured time between shares) is a better read on a Pearl rig than the hashrate.

If you look at the raw pool traffic with --log-level network, each share is a very long line. --log-wire-max trims the proof out of the log so the frames either side of it are readable.

Tuning

Pearl is compute-bound, the opposite of most GPU algorithms here. The core clock is what pays, and the prover is heavy enough that starving the card on power hurts more than it saves:

./bzminer -a pearl -p stratum+tcp://us.pearl.herominers.com:1200 -w prl1YOUR_WALLET \
  --oc-core-clock-offset 150 --oc-fan-speed "t:65[30-85]"

Leave the power limit at stock until you have a baseline, then trim it while watching shares over an hour. The CPU side is sized by --cpu_threads, which caps the prover’s threads as well; on a machine you also use, leave it on auto.

Pearl also mines on the CPU in its own right, so on a rig that runs RandomX beside it the two share the processor. To hand the whole CPU to RandomX, keep Pearl off it with --cpu1 0 (Pearl being algorithm 1) rather than --cpu 0, which is rig-wide and would stop RandomX too. The devices guide spells the rig out.

To measure a card honestly, the built-in benchmark server at a fixed difficulty is the tool. Pearl on a big GPU wants a high one so the local server is not flooded:

./bzminer --benchmark 25000000000000 -a pearl

Solo mining

Point -p at your node’s RPC URL instead of a pool and bzminer mines blocks for you directly. Nothing else changes. Solo rewards arrive as whole blocks, so a single rig can go a long time between them; the pool option is the steady one.

Problems

  • The hashrate looks tiny. That is how Pearl works: each share is a full proof, so the number is small by design and does not mean the rig is underperforming. Judge it by accepted shares and the tbs column.
  • Shares are rejected. Press u and check the wallet is a prl1 address with nothing added. On Kryptex, an account name is also accepted.
  • The CPU is fully busy. That is the prover doing its job. Cap it with --cpu_threads or the T key if the machine needs to stay usable.

More in the troubleshooting guide.