How to mine Radiant (RXD) with Gminer?

Understanding Radiant (RXD) Mining Fundamentals

1. Radiant (RXD) operates on a proof-of-work consensus mechanism, specifically utilizing the RandomX algorithm optimized for CPU mining. GPU-based mining is not supported due to algorithmic design constraints.

2. GMiner does not natively support RandomX or RXD mining. It is built primarily for Ethash, KawPow, CuckooCycle, and similar GPU-targeted algorithms. Attempting to configure GMiner for RXD results in immediate rejection by the miner or failure to initialize the kernel.

3. The official Radiant documentation explicitly recommends using XMRig for RXD mining. XMRig is actively maintained, supports RandomX with hardware acceleration flags, and integrates seamlessly with RXD’s network parameters.

4. RXD block rewards are distributed through merged mining with Monero (XMR), meaning miners must connect to an RXD-compatible pool that also relays Monero-style stratum jobs.

Why GMiner Fails with Radiant

1. GMiner lacks RandomX implementation—no source code, no binaries, and no developer roadmap indicates future support.

2. When users force GMiner to connect to an RXD stratum endpoint, the miner sends an unsupported algorithm handshake and receives “job not found” or “algorithm mismatch” errors from the pool server.

3. GPU memory bandwidth and latency characteristics make RandomX inefficient on GPUs. GMiner’s architecture prioritizes high-throughput memory access patterns incompatible with RandomX’s cache-sensitive execution.

4. Community reports across Reddit, GitHub issues, and Discord channels confirm repeated failures when substituting GMiner binaries into RXD mining rigs—even after modifying config JSONs or overriding device parameters.

Correct Tools for Radiant Mining

1. XMRig v6.18.0 or newer is the only production-ready miner for RXD.

2. Validated pools include radiantpool.io, rxdpool.com, and xmrpool.eu/rxd—each offering low fees, stable uptime, and real-time dashboard metrics.

3. CPU requirements mandate AVX2 support; older CPUs without AVX2 will either crash XMRig or fall back to significantly slower interpreted mode.

4. Configuration requires setting 'algo': 'rx/0' and 'coin': 'rx' in the JSON config, along with correct wallet address and pool URL in stratum+tcp format.

5. Linux users should disable transparent huge pages (THP) and enable CPU frequency scaling governor set to “performance” for optimal hashrate stability.

Common Misconfigurations and Fixes

1. Using --algo rx instead of --algo rx/0 causes connection rejection—RXD enforces strict variant selection.

2. Forgetting to append .rx to the wallet address (e.g., RXD...xyz.rx) leads to rejected shares; the suffix signals merged mining intent to the pool.

3. Running XMRig without --randomx-no-jit on systems with SELinux or strict AppArmor policies triggers permission-denied crashes during JIT compilation.

4. Overclocking RAM beyond 3200MHz without tightening timings often introduces share invalidation due to memory corruption during RandomX scratchpad initialization.

Frequently Asked Questions

Q: Can I mine RXD using HiveOS with GMiner preinstalled? A: No. HiveOS allows installing custom miners, but GMiner binaries cannot be repurposed for RXD. You must manually install XMRig via script or use HiveOS’s built-in XMRig installer.

Q: Does Radiant support dual mining like ETH+ETC? A: No. RXD only supports merged mining with Monero through shared RandomX infrastructure. There is no secondary coin or auxiliary reward stream.

Q: Why does my RXD miner show “low difficulty share accepted” repeatedly? A: This indicates your rig is submitting shares at a difficulty lower than the pool’s current threshold—usually caused by incorrect 'variant' setting or stale job polling due to unstable network latency.

Q: Is overclocking the CPU beneficial for RXD hashrate? A: Moderate CPU core overclocking (up to +200MHz) can yield 3–7% gains, but excessive voltage or frequency increases cause thermal throttling and higher error rates, reducing net profitability.