How to configure SRBMiner for multi-algorithm? (Solo mining)

Understanding SRBMiner Multi-Algorithm Architecture

1. SRBMiner is a high-performance, open-source GPU miner designed to support multiple cryptographic algorithms simultaneously across different blockchains.

2. It natively handles algorithms including RandomX, KawPow, Octopus, CuckooCycle, and BeamHash III without requiring separate binaries or manual switching.

3. The miner uses a configuration-driven execution model where each algorithm runs in its own isolated thread group, preventing interference between workloads.

4. Algorithm selection is defined at runtime through JSON-based configuration files that specify coin parameters, difficulty targets, and hashing kernels.

5. Memory allocation for each algorithm is pre-calculated during initialization based on GPU VRAM capacity and kernel requirements, ensuring optimal utilization without overflow.

Prerequisites for Solo Mining Setup

1. A fully synced and RPC-enabled node for the target blockchain must be running locally or accessible via LAN with authentication credentials.

2. NVIDIA drivers version 470+ or AMD Adrenalin 21.10+ are mandatory; older versions trigger fallback kernels with reduced hashrate.

3. Windows 10/11 64-bit or Linux kernel 5.4+ is required; macOS is explicitly unsupported due to OpenCL driver limitations.

4. At least 16GB of system RAM is recommended when mining RandomX alongside other memory-hard algorithms concurrently.

5. Firewall rules must allow outbound connections from SRBMiner to the local node’s RPC port (e.g., port 18081 for Monero) and inbound traffic for stratum proxy forwarding if used.

Building the Solo Configuration File

1. Create a file named config.json in the SRBMiner root directory containing algorithm-specific sections under the 'algorithms' key.

2. Each algorithm entry includes 'coin', 'pool', 'wallet', and 'rig-id' fields — for solo mining, 'pool' points to 127.0.0.1:PORT and 'wallet' is set to the local node’s mining address.

3. Use 'algorithm': 'randomx' for Monero, 'kawpow' for Ravencoin, and 'octopus' for VeChain; mixing incompatible algorithms like Ethash and RandomX on the same GPU may cause instability.

4. Enable 'solo': true inside each algorithm object to bypass pool logic and submit directly to the local daemon’s RPC interface.

5. Set 'api-port': 5000 to expose real-time metrics via HTTP, allowing external dashboards to monitor per-algorithm acceptance rates and stale share counts.

Launching and Validating the Miner

1. Execute SRBMiner-MULTI.exe --config config.json from command line; output displays detected GPUs, algorithm initialization status, and initial job fetch timestamps.

2. Monitor console logs for lines containing 'Accepted' or 'Stale' to verify successful block template submission and response parsing from the local node.

3. Run curl http://127.0.0.1:5000/api/status to retrieve JSON-formatted statistics showing active algorithms, current hashrate per device, and average latency to the RPC endpoint.

4. Check the node’s debug.log for entries like 'miner submitted block' or 'new block template' to confirm bidirectional communication integrity.

5. Observe GPU memory usage via nvidia-smi or rocm-smi; sustained VRAM occupancy above 95% indicates kernel contention and warrants disabling one algorithm.

Frequently Asked Questions

Q: Can SRBMiner submit valid blocks to a solo-mined chain without a wallet RPC endpoint?A: No. The miner requires a wallet-enabled daemon with enable-mine and rpc-bind-ip configured. Without wallet RPC access, it cannot sign transactions or construct coinbase outputs.

Q: Why does KawPow show zero hashrate while RandomX operates normally on the same GPU?A: This occurs when VRAM exceeds 8GB but the GPU lacks compute capability 6.1+. SRBMiner disables KawPow kernels automatically on unsupported architectures and logs a warning during startup.

Q: Is it possible to assign different GPUs to different algorithms within one config file?A: Yes. Use the 'devices' array inside each algorithm section to specify CUDA or OpenCL indices, e.g., 'devices': [0] for GPU 0 only on RandomX and 'devices': [1,2] for dual-GPU KawPow mining.

Q: Does SRBMiner validate block solutions before submitting them to the local node?A: Yes. Each solution undergoes full PoW verification using the same hash function and difficulty threshold as the node. Invalid shares are dropped silently without network transmission.