Miner compatibility

Which miners actually support pearlhash

We published a list of five miners. We had tested none of them. On 10 August 2026 we tested four, and three of them do not support the algorithm at all — including the one in our own copy-paste command. This page is the correction, with the evidence.

If you copied our start command before 10 Aug 2026, it could not have worked.
SRBMiner-MULTI rejects --algorithm pearlhash before it opens a socket. That was our error, not yours.

Test results

PeakMiner 2.8.2 — works (NVIDIA)

Supports Pearl natively. The flag is --coin pearl, not --algorithm pearlhash; the pool goes in --url and the address in --user. Verified from the binary’s own --help, which documents “Coin / algorithm to mine, e.g. pearl or btx”. Not yet run against our stratum with a GPU attached — the machine we tested on has none, and PeakMiner exits before connecting when it finds no CUDA device. So: the miner speaks pearlhash; our endpoint has not yet been confirmed end-to-end with it.

SRBMiner-MULTI 3.5.1 — does NOT support pearlhash

Verified two independent ways on the latest release: its own list-algorithms returns zero matches for “pearl”, and strings on the binary returns zero. The algorithm is not in the build.

BzMiner 25.0.1b2 — does NOT support pearlhash

Latest Linux release downloaded and unpacked; strings on the binary returns zero occurrences of “pearl”.

Kryptex krig-miner 1.1.3 — real Pearl miner; our TLS endpoint is now live

A genuine PRL miner for AMD (ROCm) and NVIDIA (CUDA). It accepts stratum+ssl:// only — TLS is mandatory, so until 10 Aug 2026 every AMD owner was locked out of this pool. Fixed: stratum+ssl://stratum.linkrra.com:5568 is live.

Worth saying how nearly we shipped it broken. The port opened, the service ran, the firewall was right — and the certificate covered only pool.linkrra.com, so any client doing normal hostname verification (which is the entire point of a TLS-only miner) would have failed the handshake. Every check we had passed, because none of them verified the hostname from outside the box. The certificate now covers both names, and check-stratum-endpoint.py verifies DNS, public-CA trust, hostname match, subscribe, authorize and a pushed job before any endpoint gets published again.

Still honest about the remaining gap: we have confirmed the endpoint is usable by a standards-compliant client. We have not yet run krig-miner itself against it with an AMD card attached — we do not have one.

ARCMiner, lpminer — no such pearlhash miner found

We could not locate any released software under either name that supports pearlhash. Both were listed on this site without evidence. They have been removed. If one exists and we missed it, tell us and we will test it and publish the result either way.

Verified start command

peakminer --coin pearl \
  --url stratum+tcp://stratum.linkrra.com:5567 \
  --user <your-prl-address>.<worker> \
  --password x

Why we are publishing our own mistake

A pool asks you to point hardware you pay for at infrastructure you cannot see. The only thing that makes that reasonable is a habit of saying what has actually been measured and what has not. We would rather lose the miner who wanted five compatible clients than keep the one who finds out the hard way. Every claim above is re-runnable; ask and we will send you the commands.

Connect a miner →