Bitcoin Forum
October 16, 2026, 07:45:25 AM *
News: Latest Bitcoin Core release: 31.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: LazMiner – GPU miner for 18 algorithms (CUDA / OpenCL / Vulkan) + RandomX, 1%  (Read 81 times)
LazMiner (OP)
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
October 04, 2026, 03:24:49 PM
Last edit: October 15, 2026, 05:25:08 AM by LazMiner
 #1

LazMiner 0.2.52 – GPU miner for 18 algorithms (CUDA / OpenCL / Vulkan) + CPU RandomX, 1% dev fee

What is LazMiner?
LazMiner is a GPU miner for Windows and Linux (x64). It started as a side quest to LazDazh, our rig management project, and is tested and supported by sxemini. I only started coding a few months ago, so this is a young project, built by measuring every kernel against the card instead of guessing. Every algorithm has a CPU reference and a built-in self-test (--self-test), and the CPU re-checks every solution before it is sent to the pool.

It ships as one file: the GPU runtime travels inside the executable. No toolkit, no installer, no redistributable.

Please read this first
This is a new miner, so expect bugs. Please report them, and please post your test results (card, algorithm, pool, hashrate, power) so we can keep optimizing. Every report helps, and it is the fastest way for us to improve.
I know it is hard to trust a new miner, especially one without a GitHub page. I try to be as transparent as possible, which is why we always post VirusTotal results for every download (linked below). If you have questions about anything the miner does, just ask here or on Discord.

Supported GPUs
- AMD: Polaris, RDNA1 to RDNA4 (OpenCL)
- NVIDIA: Pascal to Blackwell (CUDA)
- Intel: Should work with OpenCL, but not tested yet
Everything in these ranges is supported, but not every card is tested and optimized. Our test and tuning cards so far: Pascal, Turing, Ampere, Ada, Blackwell, RDNA1, RDNA2 and RDNA4.

Operating systems and drivers
Built and tested on Ubuntu (Linux x64) and Windows 11 (x64). Other Linux distributions and other Windows versions are not tested, so they may or may not work. Tested with the NVIDIA 580 and 595 driver and AMD RDNA 3 and for with ROCm 7.2.4 (Linux), RDNA1 and RDNA2 teste with ROCm 6.2.4.

Algorithms
GPU (18): KawPoW (Ravencoin, Neurai), Autolykos2 (Ergo), FishHash (Iron Fish), SHA3-256t (Bitcoin III), PearlHash (Pearl), Cuckaroo29 (Tari/Grin), XelisHash v3, Octopus (Conflux), Verthash, Decred (BLAKE3), Poseidon2b / NOID (Parano1d), Quantus (QPoW), hoohash-pepew (PEPEPOW), ProgPoW 0.9.4, ProgPoW-Z (Zano), TensorCash (proof of inference), Compute Substrate (CSD, SHA-256d)
CPU: RandomX (rx/0) and RandomX v2 (rx/2), LazMiner's own engine on the official RandomX library, XelishashV3

Backends per algorithm
AlgorithmCUDAOpenCLVulkan
KawPoWyesyeslimited
Autolykos2yesyesyes
FishHashyesyesyes
SHA3-256tyesyesyes
PearlHashyesyesyes
Cuckaroo29yesyes-
XelisHash v3yesyes-
Octopusyesyes (AMD)-
Verthashyesyesyes
Decred (BLAKE3)yesyesyes
Poseidon2b / NOIDyesyeslimited
Quantusyesyes-
hoohash-pepewyesyesyes
ProgPoW 0.9.4yesyes-
ProgPoW-Zyesyes-
TensorCashyesyes (layer stages)-
Compute Substrate (CSD)yesyes-
Default: CUDA on NVIDIA, OpenCL on AMD. Vulkan is still experimental and not supported everywhere (it is meant for AMD cards without ROCm; some algorithms have no Vulkan kernel or only a limited one). Override per card with --gpu-backend 0:cuda,1:vulkan.

TensorCash
TensorCash is proof of inference: a share is one window of 256 tokens of the chain's language model (Qwen3-8B, Q8, model file needed, --tsc-model). The model's layers are split between the selected cards, so several small cards, even NVIDIA and AMD mixed, mine as one row. In this first version the last card of a row has to be an NVIDIA card. Tested live at a pool on Linux; the Windows build runs the same code but has not mined on a Windows rig yet.

Dual mining
A second algorithm can share the same cards, each with its own pool. Measured live (sum of both lanes vs. each alone, 1.00 = no gain), best examples: Verthash + Hoohash 1.75 (RTX 5070), FishHash + Decred 1.70 (RTX 3060), Verthash + SHA3-256t 1.55 (RX 6600 XT), Autolykos2 + Decred 1.34 (RX 6600 XT), FishHash + SHA3-256t about 1.3 on every card. Pairs that do not pay are not in the defaults. The 1% dev fee applies to the second lane as well.
Code:
lazminer -a fishhash -o stratum+tcp://POOL:PORT -u WALLET.rig1 --dual-algo sha3-256t --dual-pool stratum+tcp://POOL2:PORT --dual-user WALLET2

PearlHash on AMD – compared with SRBMiner 3.7.5
Please note: we do not want to put any other miner down. We respect the work SRBMiner has put in over the last years. This comparison is only meant to show where LazMiner stands. Same card, same settings, live at the pool.
CardLazMinerSRBMiner 3.7.5
RX 9060 XT (RDNA4)60.7 TH/s55.5 TH/s
RX 6600 XT (RDNA2)12.85 TH/s10.77 TH/s
BC-160 (RDNA1)13.0 TH/s3.97 TH/s
Your results will vary with clocks, voltage and drivers, so please post yours.

Developer fee: 1%
1% of wall-clock time (36 seconds per hour), on a separate connection, on all algorithms except ProgPoW 0.9.4 and ProgPoW-Z. In dual mining the 1% applies to the second lane as well. Your own accepted/rejected counters do not change during a dev slice.

Parameters (--help prints the same list; every option marked <n|map> also works per device, e.g. --intensity 0:24,1:22)
OptionWhat it does
Mining
-a, --algo <name>Algorithm: kawpow, autolykos2, pearlhash, cuckaroo29, sha3-256t, fishhash, xelishash, octopus, verthash, decred, hoohash-pepew, progpow, progpowz, noid, quantus, tensorcash, sha256d-csd, randomx, randomx-v2
-o, --pool <url>Pool, stratum+tcp://host:port. Repeat for failover
-u, --user <wallet[.rig]>Wallet or login for the pool before it
-p, --pass <password>Pool password, default x
-w, --worker <name>Rig name appended to the login
--tlsUse TLS for the pool before it
--verthash-data <file>Verthash data file (1.2 GiB); default: beside the binary, then the cache
--gen-verthash-data [f]Build that data file and exit
Dual mining
--dual-algo <name>A second algorithm on the same cards
--dual-pool <url>Its pool (repeat for failover)
--dual-user <wallet>Wallet or login for that pool
--dual-pass <password>Its password, default x
--dual-worker <name>Rig name for the dual pool
--dual-intensity <n|map>Launch size of the second algorithm
--dual-share <percent>Limit the second algorithm's share of the card's time (default: both run together)
Algorithm options
--pearl-shape <MxN>PearlHash matrix shape (default 1024x524288, halved on small cards)
--pearl-ecoPearlHash efficiency mode (AMD OpenCL, Pascal, GTX 16): fewer watts, peak rate can be lower
--quantus-ecoQuantus efficiency mode on NVIDIA Ada: fewer watts, slightly lower rate
--csd-ecoCompute Substrate efficiency mode on NVIDIA Turing and newer: more hashes per watt, 2-4 % lower rate
--tsc-model <file>TensorCash model file (Qwen3-8B-Q8_0-full-v2.gguf, 8.7 GB)
--tsc-slots <n>TensorCash windows per batch, multiple of 8 up to 128 (default: what fits)
--tsc-split <a,b,..>TensorCash layer ends per card, e.g. 24,36 (default: by speed and memory)
--cpu-threads <n>RandomX worker threads, 0 = automatic
--cpu-affinity <ids>RandomX: logical CPU IDs to use, e.g. 0,2,4,6
--cpu-no-huge-pagesRandomX: do not use huge pages
--cpu-no-msrRandomX on AMD Zen (Linux, root): do not write the prefetcher setting
Devices
-d, --devices <list>Cards to use, e.g. 0,1,3 or 0-3, in PCI bus order (default: all)
-l, --list-devicesPrint every detected device and exit
-b, --backend <name>cuda, opencl or vulkan (default: best per vendor)
--gpu-backend <map>Backend per card, e.g. 0:cuda,1:vulkan
-i, --intensity <n|map>18..28, log2 of the nonces per launch
--worksize <n|map>Threads per block / work group
--gridsize <n|map>Blocks per launch
--allow-integratedDo not skip integrated GPUs
--cuda-nvrtc <what>Which bundled CUDA compiler to use (normally chosen for you)
Clocks (NVIDIA / AMD, driver support required)
--core-offset <n|map>Core clock offset in MHz
--mem-offset <n|map>Memory clock offset in MHz
--lock-clock <MHz|map>Pin the core clock; 0 releases the lock
--lock-memory <MHz|map>Pin the memory clock where supported; 0 restores
--keep-clocksLeave the settings applied when the miner exits
Monitoring API
--api-port <n>TCP port, default 4028 (TeamRedMiner/cgminer schema)
--api-bind <ip[:port]>Listen address, default 127.0.0.1
--api-allow <list>Extra allowed client addresses
--api-rwAllow control commands (quit, restart, gpuenable)
--no-apiDisable the API server
--no-api-httpAnswer raw socket clients only, not HTTP GET
Network
--retry-pause <sec>Delay between reconnect attempts, default 10
--retries <n>Give up after n failures, 0 = never
--timeout <sec>Reconnect after this much pool silence, default 180
Behaviour
--report-interval <s>Hashrate report period, default 30
--hashrate-avg <s>Averaging window for the headline hashrate
--temp-limit <C>Pause a GPU above this temperature
--temp-resume <C>Resume below this temperature
--no-cpu-verifySkip the CPU recheck of every solution
--verify-fullKawPoW: full CPU re-derivation for every share
--verify-first <n>KawPoW: full re-derivation for the first n shares per GPU, default 3
--nonce-start <n>Fixed starting nonce instead of a random one
--benchmark [algo]Run offline, no pool needed
--benchmark-seconds <n>Benchmark duration, default 30
--self-test [algo]Check the GPU kernels against the CPU reference and exit
Logging and misc
--log-level <level>trace, debug, info, warn, error, off
--log-file <path>Mirror the log to a file
-v, --verbose / -q, --quietDebug level / warnings only
--no-colorDisable ANSI colours
-c, --config <file.json>Read options from a JSON file
-h, --help / -V, --versionHelp / version and exit
Examples:
Code:
lazminer -a quantus -o stratum+tcp://POOL:PORT -u WALLET.rig1
lazminer -a pearlhash -o stratum+tcp://POOL:PORT -u WALLET.rig1 -d 0,1
lazminer -a randomx -o stratum+tcp://POOL:PORT -u WALLET.rig1
lazminer --self-test -a quantus

Planned
- More algorithms
- More dual-mining options
- Further performance improvements
- Better Vulkan support
- Intel GPU support
- More AMD overclocking support
- HiveOS support

Downloads
Our GitHub account was flagged as "spam" and suspended several times and is currently suspended. We are working with GitHub support to get it restored. Until then, all downloads are hosted on our own web space:
- Windows x64: https://lazlabz.de/Lazminer/lazminer-0.2.52-windows-x64.zip
  VirusTotal: https://www.virustotal.com/gui/file/1c4871840e682d0e7466f82d175435f2423d11c1d292ea800c0d2cf19c85ecf3
- Linux x64: https://lazlabz.de/Lazminer/lazminer-0.2.52-linux-x64.zip
  VirusTotal: https://www.virustotal.com/gui/file/55c330e3f384a085aac612abccb08f5156ee87fa37e7490d3921c2801074a61b

- HiveOS Package:  https://lazlabz.de/Lazminer/lazminer-0.2.52.tar.gz
  Virustotal: https://www.virustotal.com/gui/file/81e296bceb6ca25953154c7a1175dc0addcd264bb610fd9bec50127e91e2a3c8
a third download, lazminer-0.2.52.tar.gz, to enter in HiveOS as a custom miner (Miner name lazminer, Installation URL pointing at the archive); algorithm, pool, wallet and extra arguments come from the flight sheet. The same binary as in the Linux package; as a tar.gz it also suits Debian/Ubuntu without HiveOS


Support / contact
LazMiner is tested and supported by sxemini.
- Website: https://lazlabz.de
- Discord: https://discord.gg/au8Mu8bwkp
- X: https://x.com/LazLabz
- Telegram support: coming soon
LazMiner (OP)
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
October 13, 2026, 09:20:27 AM
 #2

LazMiner 0.2.51 – what changed since 0.2.50

Downloads and VirusTotal links are in the main thread (current build: 0.2.51). All figures are measured live at a pool, against the previous version on the same card and settings. Where a gain came in several steps, the steps are listed as measured, not added up.

New
- TensorCash (-a tensorcash): proof of inference on NVIDIA Pascal and newer and on AMD RDNA. Several small cards mine as one row. Live: Blackwell 5.6-5.8 windows/s at 70 W; a mixed row of five older cards (Pascal, Turing, RDNA4) 3.6 windows/s in 0.2.51 and 4.4 in 0.2.51a (a is an internal build, +22% in the next release); six cards including RDNA1 5.9 windows/s at about 500 W. First version: an AMD card cannot be the last card of a row yet; tested on Linux, not yet on a Windows rig. Still experimental first release
- CPU mining: RandomX (rx/0) and RandomX v2 (rx/2), plain TCP pools only (no TLS), 1% fee.
- Compute Substrate (CSD, SHA-256d) on NVIDIA and AMD, with --csd-eco for the efficiency mode.
- AMD clock control: core and memory offsets and locks. No voltage, fan or power control yet; physical validation is still pending.
- Display: a card that falls back from CUDA to OpenCL is shown in red.

Faster, per architecture
- Quantus, NVIDIA: Pascal +3.6%; Turing +2.5-2.7% at less power; Ada +1.9% at 2.5% less power; Blackwell +1.6%, then +0.3%
- Quantus, AMD: RDNA1 +2.9%; RDNA2 +4.0%, then +2.5%, then +0.5%; RDNA4 +9.1%, then +0.3%, then +1.2%
- PearlHash, AMD: RDNA1 +2.6% at 8% less power; RDNA2 +2.5% at 9% less power (the miner picks the faster of two modes at start-up; --pearl-eco forces the efficiency mode); RDNA4: a new kernel that is about 10% faster
- PearlHash, NVIDIA: Ampere +1.7%; Blackwell about 10% lower power at practically the same hashrate

Notes
- Gains are measured on the configurations we have; yours will differ. Please post results and bug reports.
- 0.2.51a is marked internal: it ran on our rigs but is not a full release yet.
LazMiner (OP)
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
October 15, 2026, 05:24:19 AM
 #3

LazMiner 0.2.52 – what changed since 0.2.51

Downloads and VirusTotal links are in the main thread (current build: 0.2.52). All figures are measured live at a pool, against the previous version on the same card and settings. Where a gain came in several steps, the steps are listed as measured, not added up.

New
- XelisHash v3 on the CPU (-a xelishash --backend cpu): LazMiner's own CPU engine, same display, API and 1% fee as the GPU algorithms. Live at a pool: 3.60 kH/s on a Ryzen 5 2600X, 1.16 kH/s on a Core i3-7350K with three threads.
- HiveOS package: a third download next to the Windows and Linux zips, a custom-miner tar.gz for HiveOS (flight-sheet config, stats, API on its own port). It was tested offline with mock data only so far and not on a real HiveOS rig yet, so feedback is very welcome.

Faster, per architecture
- TensorCash, mixed rows of NVIDIA Pascal/Turing and AMD RDNA cards: a new kernel for small batches. A row of five cards 3.6 -> 4.4 windows/s (+22%); a row of six cards including RDNA1 5.9 windows/s at about 500 W, where the same set ran at 3.0 windows/s with a third of the shares stale in 0.2.51. This was the internal build 0.2.51a and is now in a release.
- Quantus, AMD GCN4: +16% hashrate at +13% hashes per watt
- Compute Substrate (CSD), AMD: new OpenCL kernel, G[Suspicious link removed]A2 +1.9%

Notes
- Gains are measured on the configurations we have; yours will differ. Please post results and bug reports.
- CPU XelisHash: the rate depends strongly on the CPU's cache and memory speed, so numbers will vary between machines.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!