How to configure HiveOS for Radiant (RXD) mining? (Flight Sheet Setup)

Understanding Radiant Mining on HiveOS

1. Radiant (RXD) is a proof-of-work cryptocurrency built on the Qubic protocol infrastructure, utilizing CPU-bound computational tasks rather than GPU hashing.

2. HiveOS supports Radiant mining through custom miner integration, requiring precise configuration of pool endpoints, worker identification, and hardware-specific tuning parameters.

3. Unlike Ethereum or Kaspa, Radiant does not rely on standard stratum protocols; it uses HTTPS-based job distribution with JWT authentication tokens embedded in miner startup commands.

4. The official Radiant miner binary must be manually specified in the flight sheet since it is not included in HiveOS’s default miner repository.

5. Flight sheets serve as immutable configuration templates applied across rigs, ensuring consistent behavior for all machines assigned to RXD mining.

Required Components for RXD Flight Sheet

1. A valid Radiant wallet address registered on https://radiant.qubic.li, used as the payout destination.

2. A unique worker name formatted as USERNAME.RIGID, where USERNAME matches the account owner and RIGID is an alphanumeric identifier tied to physical hardware.

3. The latest qubminer release compatible with Radiant’s v1.9+ consensus layer—verified SHA256 checksum must match published hashes from qubic-li GitHub releases.

4. An active access token issued by the Radiant API endpoint, valid for 30 days and scoped to mining permissions only.

5. Hardware optimization flags including core offset, memory offset, and power limit settings tailored for AMD Ryzen or Intel Core i-series CPUs.

Constructing the Flight Sheet JSON

1. Open the HiveOS web dashboard and navigate to Farms > Flight Sheets > Add New.

2. Paste the following base structure, replacing placeholders marked with BRACKETED_TEXT:

3. Set 'coin': 'radiant' explicitly—HiveOS treats this as a distinct coin type separate from qubic.

4. Configure 'url': 'https://mine.radiant.qubic.li/' as the primary pool endpoint; fallback URLs are not supported in current RXD implementations.

5. Embed the JWT token inside the 'accessToken' field using raw string format without line breaks or escaping.

6. Assign 'miner': 'qubminer' and point 'install_url' to the exact GitHub release archive URL containing the static-linked binary for Linux x86_64.

7. Insert NVidia or AMD-specific tuning lines under 'user_config', even if unused—omission causes miner launch failure due to missing config validation.

Applying and Validating the Configuration

1. Save the flight sheet with a descriptive name such as Radiant-CPU-Optimized-v1.9.3.

2. Assign the sheet to one or more rigs via the Assign to Rigs button—assignment triggers immediate reboot and reconfiguration.

3. Monitor the Logs tab for miner initialization output; successful startup displays 'Connected to radiant.qubic.li' followed by job fetch timestamps.

4. Confirm hash rate reporting under Mining Stats > Hashrate; stable values between 0.8–1.4 KH/s indicate proper CPU thread binding and thermal throttling avoidance.

5. Cross-check submitted shares against the Radiant explorer at https://explorer.radiant.qubic.li using the configured worker name.

Frequently Asked Questions

Q: Can I run Radiant and Qubic simultaneously on the same rig?No. Both protocols use identical computational primitives and share overlapping memory regions. Concurrent execution results in invalid shares and kernel-level resource contention.

Q: Why does my rig show zero accepted shares despite stable connectivity?This occurs when the JWT token has expired or lacks mining.write scope. Regenerate the token via the Radiant dashboard and update the flight sheet immediately.

Q: Is overclocking recommended for Radiant mining?Overclocking increases rejection rates due to timing-sensitive proof verification. HiveOS enforces strict clock stability checks; deviations beyond ±1.5% trigger automatic miner termination.

Q: Does Radiant support ASIC devices?No ASIC firmware exists for Radiant. All active miners operate exclusively on general-purpose CPUs. Claims of ASIC compatibility refer to outdated testnet binaries no longer valid on mainnet.