Guide · Hive OS

Mine on a Hive OS rig

3 steps · about 10 minutes

  1. Know what you are working around

    Hive OS ships SRBMiner as a built-in miner, so the obvious move is to pick it in a flight sheet and type pearlhash in the algorithm field. That will not work, and it fails in the way that wastes the most time: healthy hashrate on screen, every share rejected.

    The built-in package tops out at SRBMiner 0.6.7. Pearlhash needs 3.5.9 or newer, and the kernels worth having landed in 3.7.3–3.8.3. The version Hive installs for you is years short of it — there is no flight-sheet setting that fixes that.

    So the algorithm field is not the problem. The binary is. Both routes below exist to get a current binary onto the rig.

  2. Simplest: run a current build over SSH

    A Hive OS rig is Ubuntu underneath and you have root on it. If you only want one rig on Pearl, this is the shortest honest path — it is exactly the NVIDIA guide, run on the rig.

    curl -fsSL -O https://github.com/doktor83/SRBMiner-Multi/releases/download/3.8.3/SRBMiner-Multi-3-8-3-Linux.tar.gz
tar xzf SRBMiner-Multi-3-8-3-Linux.tar.gz
cd SRBMiner-Multi-3-8-3
./SRBMiner-MULTI --algorithm pearlhash \
  --pool stratum.linkrra.com:5567 \
  --wallet prl1your-address-here --worker rig1

    Stop the Hive flight sheet first, or the two miners will fight over the same GPUs.

    The trade-off, stated plainly: Hive's watchdog, autofan and hashrate charts do not see a miner they did not start. You get mining; you lose the dashboard. For one rig that is usually a fair trade, for twenty it is not.

  3. Fleet-scale: a custom-miner flight sheet

    Hive's Custom Miner feature exists for exactly this — a miner, or a miner version, that is not baked into the image. You package a current SRBMiner build to Hive's custom-miner layout, host the tarball somewhere your rigs can reach, and point a flight sheet at it. Hive then treats it as a first-class miner: watchdog, stats and all.

    The fields, and what goes in each for this pool. Miner name has to match the name of your package.

    Miner name:                 srbminer
Installation URL:           <your packaged tarball URL>
Hash algorithm:             pearlhash
Pool URL:                   stratum.linkrra.com:5567
Wallet and worker template: prl1your-address-here.%WORKER_NAME%
Pass:                       x
Extra config arguments:     --algorithm pearlhash
    We have not run this on a Hive rig ourselves. The field list is from Hive's own custom-miner documentation and the pool values are the ones we verify daily, but the packaging step is yours and we have no receipt for it. If you get it working we would genuinely like to hear what the tarball had to contain.
Notes

Why we can be specific about the version ceiling: Hive's miner integrations are public. The hive/miners/srbminer directory in the Hive OS repository contains version folders from 0.3.1 to 0.6.7 and nothing above — that is the full set of builds the platform will install for you. The same integration reads the algorithm from a free-text field and exposes the miner API on port 21550, so the plumbing is fine; only the binary is old.

mmpOS: deliberately absent. We could not find documentation confirming a pearlhash-capable SRBMiner build on mmpOS, and we are not going to describe a flight sheet we have neither tested nor sourced. If you run mmpOS and have it working, tell us and this page gets a fourth step.

Pool details are the same whichever route you take: stratum.linkrra.com:5567, or stratum+ssl://stratum.linkrra.com:5568 for TLS. No extra fee over the upstream pool's own, currently 0%. PPLNS, 1 PRL minimum.

Custom-miner field list from Hiveon: adding a custom miner, read 2026-11-03. Built-in SRBMiner version range from the minershive/hiveos-linux miner directory, read 2026-11-03. Pearlhash minimum version is our own test record on the compatibility page.