Top mineração suave

Changelog

pearlhash: Added support for Blackwell and Hopper (50xx series, H100/H200/H800, B200) Significant performance improvement for the previously supported generations.

Added --kernel for pearlhash. This is comma separated list of kernel numbers( 1 or 2). Supported on a few selected cards mostly Ampere and Ada cards. In most cases the default kernel 1 should be better but kernel 2 is worth trying too!

Fixed HiveOS and mmpOS hashrate stats for Quantus coin

Release v100.41 of bzminer

All feedback is welcome ;)

• 1660 pearl, quantus, c29, cn
• pearl improvements to 20 series nvidia
• quantus improvements on amd
• minor pearl improvements to all amd's
• fixed oc's on windows for nvidia
• fixed oc ui in webui for amd and intel
• webui now shows a warning for oc's that are unavailable due to permissions or something else

Mines Tari, Conceal, Ryo, Ergo, Ethereum Classic, EthereumPoW, Ravencoin, Neurai, Neoxa, Meowcoin, Clore, nexa, Pearl, Quantus, Monero, Zephyr, Salvium, VERUS, Warthog and XELIS, and ships sha256d as the open-source SDK example.

Downloads

Verify before running:

# Linux / macOS
sha256sum -c <<< "<hash>  <file>"

# Windows (PowerShell)
Get-FileHash .\<file> -Algorithm SHA256

A checksum only proves the file is the one that was published — always download from the official release page.

Getting started

1. Unpack the archive for your platform.
2. Open a start_<algo> script and replace the placeholder wallet with your own.
3. Run it, then open http://127.0.0.1:4014/ for the dashboard.

readme.txt inside each archive has the full quick start, the common options, and the hardware-safety settings. config.txt is a commented copy of every setting, generated from the shipped binary, so it always matches the build you have.

config.txt may be JSON or a command line. The shipped file is JSON — every setting inside one { } object. bzminer equally accepts the same file written as the options you would have typed, which is what a mining OS generates and the easier form to write by hand:

# one option per line, or a flag and its value on one line
-a pearl
-p stratum+tcp://pool:1234
-w YOUR_WALLET
--worker "My Rig"

Quote a value containing a space, and start a comment with #. An option you type on the command line beats the file's copy of it, so the file is a default you can override without editing it.

Docker

There is an image, and it carries the GPU userspace as well as the miner - no ROCm install, no driver packages, nothing on the host but a kernel driver:

docker pull bzminer/bzminer:v100.41
docker run --rm -it --gpus all bzminer/bzminer -a pearl -o stratum+tcp://pool:port -w YOUR_WALLET

The identical image is on GitHub as ghcr.io/bzminer/bzminer:v100.41 if you would rather not pull from Docker Hub.

Or keep your config, log and plugins on the host and run it as a service:

docker run -d --name bzminer --restart unless-stopped --gpus all \
    -v /opt/bzminer:/data -p 127.0.0.1:4014:4014 \
    bzminer/bzminer --set http_address=0.0.0.0

With no arguments it runs /data/config.txt; anything you pass goes straight to bzminer, so every command line on this page works unchanged. http_address has to be 0.0.0.0 for the dashboard, because the default 127.0.0.1 binds the container's loopback, which no published port can reach.

GPU flags differ per vendor. NVIDIA is --gpus all (with nvidia-container-toolkit on the host). AMD and Intel are --device /dev/kfd --device /dev/dri --group-add video --group-add render and --device /dev/dri. Overclocking, MSR tuning and huge pages additionally need --privileged; mining does not.

Update with a pull, not the miner's self-update - and the old tag stays published, so a rollback is just naming it:

docker pull bzminer/bzminer && docker restart bzminer

The binary inside the image is byte-identical to the one in bzminer_v100.41_linux.tar.gz above. Full documentation: docker run --rm bzminer/bzminer cat /opt/bzminer/docs/DOCKER.md.

Updating on a mining OS

Both fetch this exact version, so they can be pasted as-is - the version below is already the one on this page.

MMPOS

Put this in miner profile → advanced → "Initiate command prior to miner launch". It downloads once; on every later launch the if sees the archive already in /tmp and exits immediately, so it costs nothing per restart.

export version="v100.41"
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

Hive OS custom miner

The Linux release now includes bzminer_custom-v100.41.tar.gz, a complete Hive OS custom miner: the full bzminer binary, flight-sheet config adapter, log launcher, and native /hive_status reporting.

1. Click Copy on the Flight Sheet JSON below.
2. Open the Hive OS farm page that lists all workers.
3. Open the Flight Sheets tab.
4. Click Import from Clipboard.
5. Create/save the flight sheet and add your PEARL wallet.
6. Apply the flight sheet to the workers.

The sample mines Pearl on HeroMiners. Change url, pool_urls, algo, and coin for another pool or algorithm. The package maps those fields, %WAL%, the Hive worker name, and pass directly to bzminer. Put optional bzminer CLI arguments in user_config.

Flight Sheet JSON

{
  "name": "PEARL_BZMINER_CUSTOM",
  "isFavorite": false,
  "items": [
    {
      "coin": "PEARL",
      "pool_ssl": false,
      "pool_urls": [
        "us.pearl.herominers.com:1200"
      ],
      "dpool_ssl": false,
      "miner": "custom",
      "miner_alt": "bzminer_custom",
      "miner_config": {
        "url": "us.pearl.herominers.com:1200",
        "algo": "pearl",
        "pass": "x",
        "miner": "bzminer_custom",
        "template": "%WAL%",
        "install_url": "https://github.com/bzminer/bzminer/releases/download/v100.41/bzminer_custom-v100.41.tar.gz",
        "user_config": ""
      },
      "pool_geo": []
    }
  ]
}

Hive OS built-in miner (manual binary replacement)

Run it over SSH or in the Hive web shell.

You do not need to know which bzminer version is installed. Hive keeps one folder per version under /hive/miners/bzminer/, and the flight sheet decides which one runs - so this replaces the binary in every bzminer folder it finds and whichever one your flight sheet points at gets the new build. That is the whole reason it does not name a version directory.

version=v100.41
cd /tmp && wget -q https://github.com/bzminer/bzminer/releases/download/${version}/bzminer_${version}_linux.tar.gz && tar -xf bzminer_${version}_linux.tar.gz || { echo "download failed"; exit 1; }
miner stop
n=0; for d in /hive/miners/bzminer/*/; do [ -d "$d" ] && cp -f "bzminer_${version}_linux/bzminer" "$d" && n=$((n+1)); done
[ "$n" -gt 0 ] && echo "updated $n bzminer folder(s)" || echo "no /hive/miners/bzminer/<version>/ found - install bzminer from the flight sheet first"
miner start

It prints how many folders it updated. 0 means bzminer has never been installed from a flight sheet on that rig, so there is nothing to replace yet.

Reporting problems

Please include: your OS, GPU model(s) and driver version, the algorithm and pool, and the first ~40 lines of the log (it prints the build, the devices it found, and what each backend reported). --list-metrics output helps for sensor issues.

Added 3rd-party mining pools support:

• Kryptex Pool: 0% devfee
• 3rd-party pools: 3% devfee

Linux ARM64 miner for NVIDIA:

• DGX Spark (GB10)
• GH200
• GB200
• GB300

(Ubuntu 24.04 or newer with a CUDA 13 driver is required.)

ForgeMiner v1.8.4

Share difficulty, best share and blocks found on every coin, Quantus off the CPU, and more accepted shares.

What's new

• New — every share's difficulty, the session's best share and blocks found, on every coin. Each accepted share shows its own difficulty, the dashboard keeps the best share of the session, and a share that is also a block is flagged and counted. Best share and blocks sit in the totals row; accepted / stale / rejected is back to three numbers.
• Quantus (--algorithm quantus) no longer keeps a CPU core busy for every GPU — CPU load drops from about one core per card to almost zero, which matters on rigs with small CPUs.
• Quantus hashrate is slightly higher on almost every GPU.
• More accepted shares: a share found just after the pool switched jobs is now still sent while the pool accepts it, instead of being thrown away. Biggest gain on Xelis, where jobs change every few seconds; smaller on Quantus, Cryptix, KawPow (RVN / QUAI / XNA) and qhash.
• HiveOS custom miner — upgrade with the versioned URL: https://github.com/0xHashRaptor/ForgeMiner/releases/download/v1.8.4/ForgeMiner-1.8.4.tar.gz. HiveOS reinstalls a custom miner only when its installation URL changes, so rigs on the old .../releases/latest/download/ForgeMiner.tar.gz link stay on the version they first installed.
• The RTX 50-series (Blackwell) requires NVIDIA driver 580 or newer (unchanged).
• Everything else is unchanged from 1.8.3.

Checksums (sha256)

c61474c1edad5052b717f5a46a1900ea4056871b042f9da97351647ac356de1b  ForgeMiner-1.8.4-windows.zip
491296d32a76eae56497830e885c1c671d20f9b43a44d14c3f1c3776eeeca192  ForgeMiner-1.8.4-linux.tar.gz
a878789682981753727623c2af61af99329bf816c94fd7ce562bc838dae74f7f  ForgeMiner-1.8.4.tar.gz

c61474c1edad5052b717f5a46a1900ea4056871b042f9da97351647ac356de1b  ForgeMiner-1.8.4-windows.zip
491296d32a76eae56497830e885c1c671d20f9b43a44d14c3f1c3776eeeca192  ForgeMiner-1.8.4-linux.tar.gz
a878789682981753727623c2af61af99329bf816c94fd7ce562bc838dae74f7f  ForgeMiner-1.8.4.tar.gz

• Improvements on algorithm 'quantus' for AMD and INTEL GPUs [NVIDIA is still fast :)]

Custom miner for Hiveos

To use it you need to select “Custom miner” when you create Flight Sheet and paste this into 'Installation url' : https://github.com/doktor83/SRBMiner-Multi/releases/download/3.7.1/srbminer_custom-3.7.1.tar.gz

After that you must set everything manually (--algorithm, --pool, --wallet) through the 'Extra config arguments' field by using parameters. Parameters list here : ( https://github.com/doktor83/SRBMiner-Multi/blob/master/Parameters )

Archive MD5 hashes e9c600af76a81e696fcad2345961a686 *SRBMiner-Multi-3-7-1-win64.zip 112223a663506023e31d7f9dbce3dfe2 *SRBMiner-Multi-3-7-1-Linux.tar.gz

• Added support for INTEL ARC GPUS on algorithm 'quantus'

• Minor improvements on 'pearlhash' for NVIDIA GPUs

• Hashrate stats changed to 1m/15m/1h/6h

• Integrated GPUs are now excluded from automatic GPU selection (enable using --enable-igpu)

Custom miner for Hiveos

To use it you need to select “Custom miner” when you create Flight Sheet and paste this into 'Installation url' : https://github.com/doktor83/SRBMiner-Multi/releases/download/3.7.0/srbminer_custom-3.7.0.tar.gz

After that you must set everything manually (--algorithm, --pool, --wallet) through the 'Extra config arguments' field by using parameters. Parameters list here : ( https://github.com/doktor83/SRBMiner-Multi/blob/master/Parameters )

Archive MD5 hashes 1400f75cfed986bea21b952c2d74a8d8 *SRBMiner-Multi-3-7-0-win64.zip 62b1651826c158945b0ede85bad94258 *SRBMiner-Multi-3-7-0-Linux.tar.gz

ForgeMiner v1.8.3

Faster Quantus on every GPU, plus a startup fix for 6 GB cards.

What's new

• Fix — 6 GB cards (e.g. RTX 2060) on Windows: in 1.8.2 Pearl could start and then show 0 H/s on a card with little free memory. Fixed — these cards mine normally again.
• Quantus (--algorithm quantus) is faster and more efficient on every supported GPU — up to about +3% more hashrate, and more hashrate-per-watt too, depending on the card (RTX 20/30/40/50-series). Same dev fee, same pools.
• New — skip a card in the overclock flags with *: e.g. --cclk 1500,1500,*,1500 sets the 1st, 2nd and 4th cards and leaves the 3rd untouched. Works for --cclk, --coff, --mclk, --moff, --plimit and --fan.
• The RTX 50-series (Blackwell) requires NVIDIA driver 580 or newer (unchanged).
• Everything else is unchanged from 1.8.2.

Checksums (sha256)

0ae45c24e7a1832a48a5eba1ad3bc3cf67d6a291c5ee8234ab3f08a8098ed090  ForgeMiner-1.8.3-windows.zip
3849b75e5e0eab89aeb04895449c377cbbf43ba9baff2372f4bdbe6aa0e8008b  ForgeMiner-1.8.3-linux.tar.gz
73d0f3fc637f67c49f27662364c810f39c2c67ee7dc7bf95897a044b15298b60  ForgeMiner-1.8.3.tar.gz

0ae45c24e7a1832a48a5eba1ad3bc3cf67d6a291c5ee8234ab3f08a8098ed090  ForgeMiner-1.8.3-windows.zip
3849b75e5e0eab89aeb04895449c377cbbf43ba9baff2372f4bdbe6aa0e8008b  ForgeMiner-1.8.3-linux.tar.gz
73d0f3fc637f67c49f27662364c810f39c2c67ee7dc7bf95897a044b15298b60  ForgeMiner-1.8.3.tar.gz

ForgeMiner v1.8.2

Pearl runs cooler and more efficient on every GPU, and faster on the RTX 50-series.

What's new

• Pearl (--algorithm pearlhash) draws less power on every supported GPU — the same hashrate at lower wattage, so higher efficiency (hashrate per watt). Up to about 8% more efficient depending on the card. Same dev fee, same pools.
• RTX 50-series (Blackwell): faster Pearl — about +2%.
• RTX 20-series (Turing): higher Pearl hashrate — about +2%.
• The RTX 50-series (Blackwell) requires NVIDIA driver 580 or newer (unchanged).
• Everything else is unchanged from 1.8.1.

Checksums (sha256)

9a8d6371ab68f0751048e7ce5d46086e29c803472621bac52ceb6c6d53a88e27  ForgeMiner-1.8.2-windows.zip
2c8921708eeedad79f95e7ebe2e6f142c9ab28a6195bb8a884401d0b1779b299  ForgeMiner-1.8.2-linux.tar.gz
ee7936854a4e83af567691edaea4e20b423711b599d1db3a555a532e698096a8  ForgeMiner-1.8.2.tar.gz

9a8d6371ab68f0751048e7ce5d46086e29c803472621bac52ceb6c6d53a88e27  ForgeMiner-1.8.2-windows.zip
2c8921708eeedad79f95e7ebe2e6f142c9ab28a6195bb8a884401d0b1779b299  ForgeMiner-1.8.2-linux.tar.gz
ee7936854a4e83af567691edaea4e20b423711b599d1db3a555a532e698096a8  ForgeMiner-1.8.2.tar.gz

Download the assets below · docker pull hashraptor/forge · forgeminer.org · Telegram · Discord

Release v100.40 of bzminer

All feedback is welcome ;)

• Big Nvidia & AMD pearl optimizations
• Further randomx optimizations

Mines Tari, Conceal, Ryo, Ergo, Ethereum Classic, EthereumPoW, Ravencoin, Neurai, Neoxa, Meowcoin, Clore, nexa, Pearl, Quantus, Monero, Zephyr, Salvium, VERUS, Warthog and XELIS, and ships sha256d as the open-source SDK example.

Downloads

Verify before running:

# Linux / macOS
sha256sum -c <<< "<hash>  <file>"

# Windows (PowerShell)
Get-FileHash .\<file> -Algorithm SHA256

A checksum only proves the file is the one that was published — always download from the official release page.

Getting started

1. Unpack the archive for your platform.
2. Open a start_<algo> script and replace the placeholder wallet with your own.
3. Run it, then open http://127.0.0.1:4014/ for the dashboard.

readme.txt inside each archive has the full quick start, the common options, and the hardware-safety settings. config.txt is a commented copy of every setting, generated from the shipped binary, so it always matches the build you have.

config.txt may be JSON or a command line. The shipped file is JSON — every setting inside one { } object. bzminer equally accepts the same file written as the options you would have typed, which is what a mining OS generates and the easier form to write by hand:

# one option per line, or a flag and its value on one line
-a pearl
-p stratum+tcp://pool:1234
-w YOUR_WALLET
--worker "My Rig"

Quote a value containing a space, and start a comment with #. An option you type on the command line beats the file's copy of it, so the file is a default you can override without editing it.

Docker

There is an image, and it carries the GPU userspace as well as the miner - no ROCm install, no driver packages, nothing on the host but a kernel driver:

docker pull bzminer/bzminer:v100.40
docker run --rm -it --gpus all bzminer/bzminer -a pearl -o stratum+tcp://pool:port -w YOUR_WALLET

The identical image is on GitHub as ghcr.io/bzminer/bzminer:v100.40 if you would rather not pull from Docker Hub.

Or keep your config, log and plugins on the host and run it as a service:

docker run -d --name bzminer --restart unless-stopped --gpus all \
    -v /opt/bzminer:/data -p 127.0.0.1:4014:4014 \
    bzminer/bzminer --set http_address=0.0.0.0

With no arguments it runs /data/config.txt; anything you pass goes straight to bzminer, so every command line on this page works unchanged. http_address has to be 0.0.0.0 for the dashboard, because the default 127.0.0.1 binds the container's loopback, which no published port can reach.

GPU flags differ per vendor. NVIDIA is --gpus all (with nvidia-container-toolkit on the host). AMD and Intel are --device /dev/kfd --device /dev/dri --group-add video --group-add render and --device /dev/dri. Overclocking, MSR tuning and huge pages additionally need --privileged; mining does not.

Update with a pull, not the miner's self-update - and the old tag stays published, so a rollback is just naming it:

docker pull bzminer/bzminer && docker restart bzminer

The binary inside the image is byte-identical to the one in bzminer_v100.40_linux.tar.gz above. Full documentation: docker run --rm bzminer/bzminer cat /opt/bzminer/docs/DOCKER.md.

Updating on a mining OS

Both fetch this exact version, so they can be pasted as-is - the version below is already the one on this page.

MMPOS

Put this in miner profile → advanced → "Initiate command prior to miner launch". It downloads once; on every later launch the if sees the archive already in /tmp and exits immediately, so it costs nothing per restart.

export version="v100.40"
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

Hive OS custom miner

The Linux release now includes bzminer_custom-v100.40.tar.gz, a complete Hive OS custom miner: the full bzminer binary, flight-sheet config adapter, log launcher, and native /hive_status reporting.

1. Click Copy on the Flight Sheet JSON below.
2. Open the Hive OS farm page that lists all workers.
3. Open the Flight Sheets tab.
4. Click Import from Clipboard.
5. Create/save the flight sheet and add your PEARL wallet.
6. Apply the flight sheet to the workers.

The sample mines Pearl on HeroMiners. Change url, pool_urls, algo, and coin for another pool or algorithm. The package maps those fields, %WAL%, the Hive worker name, and pass directly to bzminer. Put optional bzminer CLI arguments in user_config.

Flight Sheet JSON

{
  "name": "PEARL_BZMINER_CUSTOM",
  "isFavorite": false,
  "items": [
    {
      "coin": "PEARL",
      "pool_ssl": false,
      "pool_urls": [
        "us.pearl.herominers.com:1200"
      ],
      "dpool_ssl": false,
      "miner": "custom",
      "miner_alt": "bzminer_custom",
      "miner_config": {
        "url": "us.pearl.herominers.com:1200",
        "algo": "pearl",
        "pass": "x",
        "miner": "bzminer_custom",
        "template": "%WAL%",
        "install_url": "https://github.com/bzminer/bzminer/releases/download/v100.40/bzminer_custom-v100.40.tar.gz",
        "user_config": ""
      },
      "pool_geo": []
    }
  ]
}

Hive OS built-in miner (manual binary replacement)

Run it over SSH or in the Hive web shell.

You do not need to know which bzminer version is installed. Hive keeps one folder per version under /hive/miners/bzminer/, and the flight sheet decides which one runs - so this replaces the binary in every bzminer folder it finds and whichever one your flight sheet points at gets the new build. That is the whole reason it does not name a version directory.

version=v100.40
cd /tmp && wget -q https://github.com/bzminer/bzminer/releases/download/${version}/bzminer_${version}_linux.tar.gz && tar -xf bzminer_${version}_linux.tar.gz || { echo "download failed"; exit 1; }
miner stop
n=0; for d in /hive/miners/bzminer/*/; do [ -d "$d" ] && cp -f "bzminer_${version}_linux/bzminer" "$d" && n=$((n+1)); done
[ "$n" -gt 0 ] && echo "updated $n bzminer folder(s)" || echo "no /hive/miners/bzminer/<version>/ found - install bzminer from the flight sheet first"
miner start

It prints how many folders it updated. 0 means bzminer has never been installed from a flight sheet on that rig, so there is nothing to replace yet.

Reporting problems

Please include: your OS, GPU model(s) and driver version, the algorithm and pool, and the first ~40 lines of the log (it prints the build, the devices it found, and what each backend reported). --list-metrics output helps for sensor issues.