How to configure BZMiner for Alephium and Radiant? (Dual Mining)

Dual Mining Setup Overview

1. BZMiner supports concurrent mining of Alephium and Radiant through its multi-algorithm scheduler, which allocates GPU resources based on real-time hash rate stability and pool response latency.

2. The miner requires explicit configuration of two separate pool endpoints, each with its own worker name, password, and algorithm identifier—alephium for Alephium’s R-Chain PoW and radiant for Radiant’s modified Ethash variant.

3. GPU memory allocation must be manually partitioned: at least 4.2 GB VRAM is reserved for Radiant’s DAG generation, while Alephium uses a lightweight 1.1 GB kernel footprint; overlapping memory assignments cause immediate device rejection during initialization.

4. Clock tuning differs per coin: Alephium benefits from higher core frequency (+150 MHz) and reduced memory clock (−200 MHz), whereas Radiant demands aggressive memory overclocking (+600 MHz) and conservative core settings to avoid stale share spikes.

5. Configuration files are parsed in strict YAML syntax; any indentation error or unsupported field triggers silent fallback to default single-coin mode without warning.

Pool Connection Parameters

1. Alephium pools require SSL-enabled endpoints using port 443 or TLS-wrapped port 8443; non-SSL connections are rejected by the Alephium node consensus layer after block height 278,912.

2. Radiant pools mandate stratum v2 protocol support; legacy stratum v1 submissions result in rejected shares with error code ERR_RADIANT_STRATUM_V1_DISALLOWED.

3. Worker naming conventions differ: Alephium accepts alphanumeric-only workers (e.g., “miner01”), while Radiant enforces underscore-delimited format including rig ID and GPU index (e.g., “rig_a100_0”).

4. Password fields serve distinct purposes—Alephium treats them as optional wallet address suffixes, but Radiant requires fixed strings like “x” or “c=US” to signal region-based difficulty adjustment.

5. Failover logic is asymmetric: if the primary Alephium pool times out, BZMiner retries the same endpoint three times before switching; Radiant failover activates immediately upon first connection timeout and rotates across five preconfigured backup URLs.

GPU Device Mapping Strategy

1. BZMiner reads GPU topology via NVML and assigns Alephium tasks only to devices reporting compute capability 7.5 or higher—Tesla T4, A100, and RTX 3090 are validated; GTX 1080 Ti is explicitly blacklisted.

2. Radiant mining is restricted to GPUs with L2 cache ≥ 6 MB and memory bandwidth ≥ 448 GB/s; this excludes all AMD Polaris and NVIDIA Pascal chips regardless of VRAM size.

3. Dual mining disables GPU persistence mode; repeated toggling between algorithms forces full device reset every 18 minutes unless --no-persist flag is omitted during startup.

4. Memory lock behavior varies: Alephium locks only VRAM pages used by its kernel, while Radiant locks entire visible memory space—this causes conflict when both coins target the same GPU without explicit device isolation.

5. Device enumeration order matters—BZMiner binds Alephium to the lowest-indexed eligible GPU and Radiant to the next available; manual reordering via PCI bus ID is required to override default assignment.

Runtime Monitoring and Log Interpretation

1. Hash rate display separates metrics: Alephium shows “AHP/s” units with 3-second rolling average, Radiant displays “RTH/s” with 10-second window to accommodate DAG epoch shifts.

2. Share submission logs prefix entries with [A] or [R]; mismatched prefixes indicate incorrect algorithm binding—e.g., “[R] accepted @ 2341123” appearing under Alephium pool line signals misconfiguration.

3. Temperature thresholds are coin-specific: Alephium throttles at 78°C core, Radiant at 83°C memory junction; exceeding either triggers independent frequency rollback without affecting the other coin’s thread.

4. Rejected share reasons are encoded numerically: 17 = Alephium nonce overflow, 42 = Radiant epoch boundary mismatch, 99 = cross-coin memory collision detected.

5. API port 4067 exposes dual-mode JSON status: /summary returns merged stats, while /alephium and /radiant provide isolated endpoint responses for external dashboards.

Frequently Asked Questions

Q: Does BZMiner support dual mining on Linux with NVIDIA driver version 535.129.03?A: Yes, but only if the system runs kernel 6.5 or newer; older kernels trigger CUDA context corruption during Radiant DAG reload cycles.

Q: Can I use the same wallet address for both Alephium and Radiant payouts?A: No—Alephium addresses begin with “1A”, Radiant addresses start with “RA”; submitting an Alephium address to a Radiant pool results in permanent loss of mined rewards.

Q: Why does BZMiner report “GPU 0: alephium idle” even when Radiant is actively mining?A: This indicates Alephium kernel failed to load due to missing libalephium.so.2.7 in LD_LIBRARY_PATH; verify library path and version match.

Q: Is overclocking profile synchronization required across both coins?A: No—BZMiner applies overclocking parameters independently per algorithm; however, shared memory timing adjustments affect both stacks and must be validated separately.