Irium (IRM) mining — PoW parameters and early network observations

[irium]

This thread is for technical discussion of Irium (IRM) mining and early network behavior.

Irium is a mine-only Proof-of-Work chain. There was no premine, presale, or airdrop.

────────────────────────────────
Mining Overview
────────────────────────────────

• Proof-of-Work consensus
• Mine-only distribution
• Multicore CPU mining supported
• Public mining software
• No official pool operated by the project

────────────────────────────────
Mining Notes
────────────────────────────────

• The miner utilizes multiple CPU cores by default
• Actual performance depends on core count, CPU architecture, and OS scheduling
• Early hashrate variance is expected on a small network

────────────────────────────────
Current Network Notes
────────────────────────────────

• Early-stage network with a small number of public nodes
• DNS-free peer discovery
• Initial connectivity depends on reachable peers being online at startup

Troubleshooting notes for “no peers”, mobile/Termux setups, and miner behavior at height 0 have been added to the repository documentation.

────────────────────────────────
Discussion Topics
────────────────────────────────

• Multicore mining performance on different CPUs
• Difficulty adjustment behavior at low hashrate
• Solo mining observations
• Peer connectivity from miner-operated nodes

This thread is intended for technical feedback and observations, not promotion or price discussion.

[minerja]

followed steps on github, get to this, and get this response

./target/release/iriumd

Failed to load anchors: anchor signature verification failed: valid anchor signatures below threshold: 0/1

Any ideas?

[irium]

That error means the node could not verify the signed bootstrap anchors file.

Irium verifies bootstrap/anchors.json using ssh-keygen’s signature verification (-Y) and the allowlist in bootstrap/trust/allowed_anchor_signers. If your OpenSSH is too old (no “ssh-keygen -Y”), or those files are missing/modified, verification returns 0/1 and the node exits.

Quick check (please paste output):

ssh-keygen -Y verify

If you see “unknown option” / usage output, your OpenSSH is too old. Fix by updating the OpenSSH client:

Ubuntu/Debian:
  sudo apt update
  sudo apt install -y openssh-client
  ssh-keygen -V

Fedora:
  sudo dnf install -y openssh-clients
  ssh-keygen -V

Windows:
  Use WSL (recommended) or update the “OpenSSH Client” optional feature.

Also make sure the repo files are clean (no local changes):
  cd ~/irium
  git reset --hard
  git clean -fdx
  git pull origin main

Then rebuild + run again:
  source "$HOME/.cargo/env" 2>/dev/null || true
  cargo build --release
  ./target/release/iriumd

If it still fails, please confirm these two files exist and are unmodified:
  bootstrap/anchors.json
  bootstrap/trust/allowed_anchor_signers