How to mine

How to mine Ergo

Autolykos v2, GPU only. Why it needs 2 GB of VRAM and what to do with the rest.

Algorithm
Autolykos v2 (-a ergo)
Mines on
NVIDIA, AMD, Intel and Apple GPUs. Not the CPU
Dev fee
1%
Wallet
Starts with 9
VRAM
About 2 GB free per card, growing slowly with block height
Launcher
start_ergo in the archive

Ergo is a smart-contract proof-of-work chain, and Autolykos v2 is memory-hard on purpose: before a card can mine it has to fill a table of about 2 GB in its own VRAM. That one fact explains most of what is different about mining it — the pause at startup, the VRAM requirement, and why the memory clock matters more than the core.

Before you start

  • An Ergo wallet address. Mainnet addresses start with 9.
  • A pool. stratum+tcp://pool.us.woolypooly.com:3100 (WoolyPooly) is in the launcher. MoneroOcean also takes Autolykos work and pays in XMR — that is a different setup, covered below.
  • A GPU with room for the table. A card with less free VRAM than the table needs is reported and skipped at startup rather than quietly producing nothing, so a 4 GB card that is also driving a display can fall short.

The command

./bzminer \
  -a ergo \
  -p stratum+tcp://pool.us.woolypooly.com:3100 \
  -w 9YOUR_ERGO_WALLET \
  --worker rig1
  • -a ergo — the algorithm.
  • -p — the pool. Repeat it for a backup pool.
  • -w — your 9... address, with nothing appended; bzminer adds the worker name itself.
  • --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_ergo.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 ergo -p stratum+tcp://pool.us.woolypooly.com:3100 -w 9YOUR_ERGO_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_ergo.sh in any editor and replace the placeholder wallet. Other pools are in the same file as commented-out lines.

  3. Run it

    ./start_ergo.sh

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

    ./bzminer \
      -a ergo \
      -p stratum+tcp://pool.us.woolypooly.com:3100 \
      -w 9YOUR_ERGO_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

On Apple Silicon the 2 GB table comes out of unified memory, sized against what Metal says it may use. It fits an 8 GB M2 with room to spare, but it is the Mac’s own memory, so leave the machine something to live in.

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

  3. Run it

    ./start_ergo.sh

    Or written out:

    ./bzminer \
      -a ergo \
      -p stratum+tcp://pool.us.woolypooly.com:3100 \
      -w 9YOUR_ERGO_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 algorithmergo
    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 URLpool.us.woolypooly.com:3100 — 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 ergo is not among the algorithms mmpOS offers for bzminer, pick any and add --force_algo ergo 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

After the device roster and the pool connection, each card spends a moment building its table. The hashrate is zero during that and the log says what is happening; it is not stuck. The table is rebuilt when the chain crosses into a new size, which is rare and also announced. Then the accepted lines begin.

On the mining table, cfg shows each card’s intensity (i0 is auto) and poolhr shows the pool’s credited rate against your own. Give it an hour before reading anything into that percentage.

Tuning

Autolykos is bound by memory bandwidth. The core has slack, so the usual recipe on NVIDIA is a memory offset first, then trim the power limit until the hashrate starts to follow it:

./bzminer -a ergo -p stratum+tcp://pool.us.woolypooly.com:3100 -w 9YOUR_ERGO_WALLET \
  --oc-memory-clock-offset 1000 --oc-power-limit 170 \
  --oc-fan-speed "t:60[25-75] tm:80[50-100]"

On Linux those flags need root. AMD cards accept a fan setting only; their clocks are not controllable from bzminer. The overclocking guide has the per-card form and the live hotkeys.

Mining Ergo’s algorithm for XMR

MoneroOcean accepts Autolykos2 work and pays in Monero. The wallet becomes a Monero address, and the algorithm has to be pinned in the password, because MoneroOcean otherwise serves whatever it happens to be mining and an Ergo miner handed KawPow work finds nothing:

./bzminer -a ergo -p stratum+tcp://gulf.moneroocean.stream:10128 \
  -w 4YOUR_MONERO_WALLET --pass "rig1~autolykos2"

The MoneroOcean guide explains the pin, the ports, and the other algorithms it takes.

Problems

  • A card is skipped at startup. The table did not fit beside whatever else is in that card’s VRAM. Free the card (close a game, move the display to another card) or leave that card out of the run.
  • Shares are rejected. Check the wallet with u in the console. An address for another coin looks the same to you and different to the pool.
  • The hashrate drops to zero for a while after a job change. The card is rebuilding its table, which the log announces, and it resumes on its own.

More in the troubleshooting guide.