Mining — HIDERING (HRG)

Requirements

OS Linux x86_64 · macOS ARM64 · Windows x64
RAM the ~2 GB RandomX dataset is shared by all mining threads, plus ~2 MB per thread
DISK ≥ 8 GB free (daemon pre-allocates ~5 GB LMDB)
PORT 19740 open inbound (optional, for relaying)

Optional: enable Linux huge pages for higher hashrate — echo 1280 | sudo tee /proc/sys/vm/nr_hugepages. Get the binaries first on the Download page.

Public Pool

Pooled mining gives steadier payouts than waiting on a solo block: each block's reward is shared in proportion to the work submitted during that round (PROP). Point any RandomX miner (e.g. XMRig) at the HIDERING public pool. You still need a B-address to receive payouts — create one with the wallet CLI (see the Solo tab, steps 1 & 3).

STRATUMstratum+tcp://pool.hidering.org:3333
STATS APIhttps://pool.hidering.org/stats
ALGORandomX (rx/0)
FEE1%
MIN PAYOUT1 HRG
PAYOUTSPROP (proportional per round)
PAYOUT CYCLEevery 30 min · currently max 50 HRG per payment (balances above 50 HRG are paid in installments of 50 HRG, one per cycle)

One-line command (XMRig)

xmrig -o pool.hidering.org:3333 -u YOUR_HRG_ADDRESS -p x -a rx/0

config.json pool entry

// pools[] entry in your XMRig config.json
{
  "url": "pool.hidering.org:3333",
  "user": "YOUR_HRG_ADDRESS",
  "pass": "x",
  "rig-id": "rig1"
}

Replace YOUR_HRG_ADDRESS with your own B-address. Watch your worker and the pool hashrate live at the stats API above.

Download, verify, and extract

Grab the latest release (v2.0.3) from the Download page. Download the archive and the matching .sha256 into the same folder, then run the three commands below. Pick the archive for your platform: hidering-linux-x64.tar.gz, hidering-macos-arm64.tar.gz, or hidering-windows-x64.zip.

# 1. Verify the archive (must print: OK)
sha256sum -c hidering-linux-x64.tar.gz.sha256

# 2. Extract
tar -xzf hidering-linux-x64.tar.gz

# 3. Move into the extracted folder
cd hidering-linux-x64/

Windows: use right-click → Extract All on the .zip instead of tar. You'll use ./hideringd (node) and ./hidering-wallet-cli (wallet) from this folder.

Launch the daemon & sync

Start the daemon. It connects to seed nodes and syncs automatically. Keep this terminal open while mining.

# Run from the hidering-linux-x64/ folder
./hideringd \
  --add-priority-node seed1.hidering.org:19740 \
  --add-priority-node seed2.hidering.org:19740

Wait for: You are now synchronized with the network.

Create your wallet

Open a second terminal (leave the daemon running) and cd into the same folder. Your address starts with B. Write down the 25-word seed phrase and keep it offline — without it your HRG cannot be recovered.

# Create a new wallet
./hidering-wallet-cli --generate-new-wallet my-wallet

# Or open an existing wallet
./hidering-wallet-cli --wallet-file my-wallet

Start mining

Inside the wallet CLI, launch the miner. Replace 4 with the number of CPU threads to allocate.

start_mining 4

Each block = 42.86 HRG credited to your wallet.

Stop mining & check balance

Stop any time from inside the wallet CLI. Mined HRG unlocks after 60 confirmations (~2 hours).

stop_mining         # stop the miner
balance              # view balance + unlocked
exit                 # close wallet safely

Send HRG to another wallet

Once your balance is unlocked, transfer HRG to any B-address. Keep the default ring size (32): the HIDERING wallet CLI, wallet-rpc and GUI all use it by default, and a different size makes your transaction easier to single out.

transfer B5xxx...address 10

show_transfers       # transaction history

Advanced — choosing a larger ring: in the wallet CLI, the ring size is the number of ring members (any value from 32 to 64) and goes after transfer (and after an optional priority), before the address. A larger ring includes more decoys per input. The ring size is public on-chain, so a size that few people use makes your transaction easier to recognise; we recommend the default (32). The GUI has no ring-size setting.

transfer 48 B5xxx...address 10 # ring of 48 members