Zecnero
How to mine Zecnero

Mining Zecnero, explained.

How mining Zecnero (ZMR) works, from your CPU to a mined block: the pool or your own node, what RandomX asks for, your odds, and where the reward goes. For the commands, use the step-by-step guide.

01Two ways to mine: the pool or your own node

On the pool, the default, your computer runs one program: xmrig-zecnero, the miner, which hashes with the algorithm rx/zecnero, and rx/zecnero2 from the testnet’s NU2 upgrade, on every CPU thread you give it. It connects to the official pool, pool.zecnero.org, at stratum.zecnero.org:3334 over TLS, and sends it shares: results easier than a block, about one every 15 seconds, which show how much work you do. The pool runs the node and builds the blocks. When one of its miners finds a block, the pool splits the reward by the shares each miner sent before it (PPLNS) and pays balances of 0.5 ZMR or more once the block has 100 confirmations. The official pool’s fee is 0% on the testnet and will be 1% on Mainnet. There is nothing to sync, so mining starts about a minute after the install.

Solo, three programs run side by side on your computer, and they only talk to each other over loopback:

  • zecnerod, the node, follows the chain and builds a block template: the transactions to include, the coinbase that pays you, and the target to beat.
  • zecnero-bridge translates. The node speaks a Bitcoin-style template protocol; the miner expects Monero-style jobs. The bridge hands out jobs and passes solved blocks back to the node.
  • xmrig-zecnero does the hashing, as on the pool.

The node talks to the rest of the network on TCP port 18733. The bridge asks the node for work over its RPC port, 127.0.0.1:18732, and the miner connects to the bridge on 127.0.0.1:3333. Only the first leaves your computer, and none needs a port opened on your router. The bridge trusts the miner’s shares without recomputing them, so it must stay on loopback; never expose it to a network.

Solo, when your machine finds a block, its whole reward is yours, less the 3% founder stream, and nothing comes until then. The pool pays small amounts often; solo pays a whole block rarely. Over time both come to your share of the network’s hashrate. Solo miners also keep the network spread out. The pool page shows the official pool’s share of the network at all times.

This page explains how it works. You do not have to set anything up yourself: one command in the mining guide downloads and checks the programs, makes your mining key and starts mining, on the pool unless you choose solo. The guide also has the manual steps and the downloads.

02What RandomX asks of your CPU

RandomX runs randomly generated programs whose instruction mix and memory use are modelled on ordinary processors, so the hardware that runs it best looks like the desktop you already own. A GPU adds little. Zecnero uses RandomX’s audited version 1 settings with its own salt, which gives it a hash function of its own: Monero hardware and hashrate cannot be pointed at it unchanged.

WhatWhy it matters
About 2,080 MiB of RAM to mineThe miner builds a dataset of that size in fast mode, 2,336 MB with its cache. Solo, the node takes about 1 GB more. The mining guide asks for a computer with 8 GB.
A new key every 2,048 blocksAbout every 42.7 hours the RandomX key changes and the miner rebuilds its dataset. Expect a short pause.
256 MiB to verifyThe node checks blocks in light mode, a few milliseconds per hash.
x86-64, Linux or WSL2The released binaries are Linux x86-64. On Windows they run inside WSL2, the default. For pool mining there is also a native Windows miner, an opt-in beta that needs an update at the next network upgrade: see the mining guide.

03How often you find a block

A block is due every 75 seconds on average. Difficulty starts at a level where one block takes about 220 hashes, which the specification sizes to a desktop processor at around 14,000 hashes a second. From there the aserti3-2d algorithm moves it, with a half-life of one hour from network upgrade NU1: every hour the chain falls behind schedule the target doubles, every hour ahead it halves. Mainnet has NU1 from its first block. The testnet uses two hours until its network upgrade.

Which miner finds each block is chance. Over time your share of blocks tends to your share of the network’s total hashrate, and nothing more; nothing about the design makes mining profitable. On testnet that is beside the point: the coins have no value, and every block you mine helps prove the rules hold.

04Getting more hashes

  • Huge pages and the MSR tweak. RandomX runs noticeably faster with both. XMRig can apply them on native Linux when it runs with root rights; inside WSL the MSR tweak is not available, so WSL hashes slower than native Linux on the same machine. Fine for the testnet, but not a reference number.
  • Threads. By default the miner picks a thread count from your CPU’s cache, which is often most of your cores. --threads=<n> leaves some free for the node and for you.
  • Laptops work, but heat up and throttle. Fewer threads and mains power help.
  • Antivirus. Windows Defender flags every XMRig build, ours included, as a potentially unwanted application. Verify the signed checksums first, then allow the one file or folder; never turn the scanner off.

To compare CPUs and see how to measure a hashrate others can reproduce, see the rig and benchmark board, which also has a reference rig and a tuning guide.

05Where the reward goes

Per block, first halvingZMR
Block subsidy6.25
Founder stream, 3%0.1875
Your share of the subsidy6.0625, plus every fee in the block

Solo, the payout goes to the miner_address in the node’s configuration, and the -u you pass the miner is ignored. On the pool, -u is the address the pool pays: the block reward goes to the pool, which pays you your part of it. The founder stream is enforced by every node: a block without it is rejected, the pool’s and yours included.

Mined coins can be spent 100 blocks later, which is why the pool pays a block only after 100 confirmations. On Mainnet mined coins must also be shielded first, moved into Orchard (a unified address), before they can go anywhere else. The wallet applies that rule on testnet too, so solo, import the key your coins were mined to, shield, then send.

06Start mining

One command starts it all. On Linux, or in Ubuntu under WSL on Windows, it is curl -fsSL https://downloads.zecnero.org/install-miner.sh | bash; in Windows PowerShell, irm https://downloads.zecnero.org/install.ps1 | iex. It downloads and checks the signed release, asks you to save your mining key, then asks how you want to mine. Press Enter for the pool, which makes a wallet for your payouts (its 24-word seed is the only way to spend them) and starts the miner, or choose solo, which starts the node, the bridge and the miner. If you installed before, zecnero-miner update then zecnero-miner mode pool moves you to the pool. The mining guide explains each step, walks a Windows PC through WSL, and has a manual setup for anyone who wants to run the programs by hand. The files themselves are listed under Downloads.

Open the mining guide  →

The commands on one shorter page: How to mine Zecnero.

Stuck? Ask on Discord, or open an issue on GitLab with your log output and whether you run WSL or native Linux.