How to mine Radiant with a GPU? (RXD Setup Tutorial)

Understanding Radiant Mining Mechanics

1. Radiant (RXD) operates on a proof-of-work consensus model optimized for GPU-based computation, emphasizing memory bandwidth and parallel thread execution over raw hash rate.

2. The algorithm used is called RadHash, a modified variant of RandomX designed to resist ASIC dominance while maintaining fairness across consumer-grade AMD and NVIDIA graphics cards.

3. Block rewards are distributed every 90 seconds, with base reward starting at 12.5 RXD per block, adjusted dynamically based on network difficulty and total active hashrate.

4. Difficulty retargets every 2016 blocks—approximately once every 5.25 days—ensuring consistent block times despite fluctuations in miner participation.

5. Memory requirements exceed 4 GB VRAM for stable operation; cards with less than 6 GB may experience rejected shares due to cache overflow during dataset rotation.

Hardware and Driver Preparation

1. Supported GPUs include AMD Radeon RX 570/580/590, RX 6600/6700 XT, and NVIDIA GTX 1060 6GB or higher; older models like the GTX 970 suffer from memory segmentation issues that cause persistent stale shares.

2. AMD drivers must be version 23.5.1 or newer; earlier releases contain memory timing bugs that reduce effective hashrate by up to 18% under sustained load.

3. NVIDIA users require CUDA Toolkit 12.1 compatibility; driver versions below 535.86.05 introduce kernel-level race conditions affecting share submission reliability.

4. System RAM should be at least 16 GB DDR4; insufficient host memory leads to pagefile thrashing during DAG generation, increasing latency between share submissions.

5. Power supply units must deliver stable +12V rail output; voltage droop exceeding ±3% triggers automatic GPU throttling, cutting hashrate by 22–35% without warning.

Wallet and Pool Configuration

1. Radiant Core Wallet v2.4.7 is mandatory; lightweight wallets do not support RPC commands required for local mining control or real-time share validation.

2. Create a new wallet address using the generateaddress command inside the CLI interface—reusing addresses from other coins causes transaction parsing failures during payout reconciliation.

3. Choose pools supporting stratum v2 protocol: RadiantPool.io, RXDMine.net, and HashNova-RXD are verified to process shares within sub-150ms latency windows.

4. Configure pool credentials using --url stratum+tcp://pool.radiantpool.io:3333 --user YOUR_RXD_ADDRESS --pass x; omitting the password field or entering non-alphanumeric characters breaks authentication handshake.

5. Enable auto-reconnect with --retry-pause 5 and disable GPU persistence mode if running on Linux systems with Nouveau drivers enabled.

Optimizing GPU Parameters

1. For AMD cards, use --gpu-plotting 1 --gpu-threads 4 to maximize L2 cache utilization without triggering thermal throttling above 72°C.

2. NVIDIA tuning requires setting --cuda-bfactor 12 --cuda-bsleep 25 to align memory access patterns with RadHash’s pseudo-random memory walk sequence.

3. Core clock offsets should remain within ±125 MHz; exceeding this range introduces arithmetic errors in modular exponentiation steps, resulting in invalid shares.

4. Memory clock adjustments above +800 MHz on GDDR6-based cards produce diminishing returns—hashrate gains plateau while error rates climb exponentially beyond that threshold.

5. Fan curves must maintain GPU junction temperature below 85°C; sustained operation above this level degrades memory controller stability, causing intermittent share rejection spikes.

Frequently Asked Questions

Q: Can I mine Radiant using integrated graphics?A: No. Integrated GPUs lack sufficient VRAM bandwidth and dedicated compute units required to execute RadHash’s memory-hard operations. Attempts result in immediate process termination or zero accepted shares.

Q: Why does my miner report “Invalid job ID” repeatedly?A: This occurs when the pool server sends an outdated job template after a network partition. Restarting the miner forces rehandshake; ensure NTP sync is active on the host machine to prevent timestamp-related job invalidation.

Q: Is overclocking safe for long-term Radiant mining?A: Aggressive overclocking increases electromigration risk in GPU memory dies. Observed failure rates rise by 300% after 400 continuous hours at +1000 MHz memory offset, even with adequate cooling.

Q: Do I need to run a full node to mine Radiant?A: No. Solo mining requires a synced full node, but pool-based mining only needs outbound TCP connectivity to the chosen stratum endpoint. Wallet synchronization is optional unless claiming payouts directly to a local wallet file.