How to configure HiveOS Flight Sheets for Alephium? (Pro Setup)

Understanding Flight Sheets in HiveOS

1. Flight Sheets are dynamic configuration templates within HiveOS that define mining parameters for specific algorithms and coins.

2. Unlike static miner configurations, Flight Sheets allow real-time adjustments without restarting miners or rebooting rigs.

3. Alephium uses the RChain PoW algorithm, which requires precise memory tuning, GPU clock offsets, and custom kernel parameters not auto-detected by default.

4. HiveOS does not ship with prebuilt Alephium Flight Sheets — users must manually configure them using JSON-based definitions aligned with Alephium’s RPC and stratum protocol requirements.

5. The absence of native Alephium support means misconfigured Flight Sheets often result in rejected shares, unstable DAG generation, or persistent “no connection” errors in miner logs.

Required Pre-Deployment Components

1. A working Alephium full node or access to a public Alephium stratum pool supporting stratum+tcp or stratum+ssl.

2. Valid Alephium wallet address configured as the payout destination — HiveOS validates this during Flight Sheet import and rejects malformed addresses.

3. Compatible miner binaries: alephium-miner v1.3.0+ (CUDA 12.1 or ROCm 6.1 compatible) must be placed in /hive/miners/alephium-miner/ with executable permissions.

4. GPU firmware updated to support >4GB VRAM allocation per device — older BIOS versions on AMD RX 6700 XT or NVIDIA RTX 3060 Ti cause DAG initialization failures.

5. HiveOS version 0.6-2212+ required; earlier versions lack RChain algorithm detection hooks and fail to parse Alephium-specific JSON fields like 'rchain_dag_mode' or 'alephium_pool_port'.

Manual Flight Sheet Construction

1. Navigate to Farm → Settings → Flight Sheets → Create New in the HiveOS web interface.

2. Set Algorithm to RChain, then select Custom under Coin — HiveOS will not list Alephium in dropdowns.

3. Paste raw JSON containing mandatory keys: 'coin': 'ALEPHIUM', 'pool_host', 'pool_port', 'wallet', 'rchain_dag_mode': 'fast', and 'gpu_mem_offset': -300 for stability on most LHR cards.

4. Include 'extra_args': '--no-nvml --disable-watchdog' to suppress false thermal alerts triggered by Alephium’s nonstandard GPU polling behavior.

5. Save and assign the Flight Sheet to target GPUs — verify assignment via Miner → Status → Config to confirm all fields render without red warning icons.

Troubleshooting Common Failures

1. Miner process exits immediately after launch: indicates incorrect miner binary path or missing libcudart.so.12 symlink in /usr/lib/.

2. Shares rejected with error “invalid header”: points to mismatch between pool_host port and actual stratum endpoint — Alephium pools use nonstandard ports like 3333 instead of 3333/4444 defaults.

3. GPU utilization stuck at 0% despite active miner process: caused by rchain_dag_mode set to “auto” — must be explicitly “fast” or “slow” depending on VRAM size.

4. HiveOS reports “No valid shares in last 10 minutes” while pool dashboard shows accepted work: implies wallet address checksum validation failure — Alephium addresses require strict base32 encoding with correct prefix “alephium”.

5. Reboot loop after applying Flight Sheet: occurs when extra_args contain unsupported flags like “--intensity” — Alephium-miner ignores intensity and crashes if passed.

Frequently Asked Questions

Q: Can I reuse an Ethereum Flight Sheet for Alephium by changing only the pool and wallet?A: No. Ethereum Flight Sheets rely on Ethash parameters and DAG generation logic incompatible with RChain. Attempting reuse causes immediate miner termination.

Q: Does HiveOS support Alephium auto-switching between pools based on profitability?A: Not natively. Alephium lacks integration with HiveOS’s built-in profit-switching engine due to absence of standardized API endpoints for block reward estimation and network difficulty feeds.

Q: Why does my RX 7900 XTX show “DAG build failed: out of memory” even with 24GB VRAM?A: Alephium’s RChain implementation enforces strict 16GB ceiling for DAG allocation regardless of physical VRAM — downclocking memory clocks or enabling compute mode is required before DAG init.

Q: Is there a way to monitor Alephium-specific metrics like block height or confirmed transactions via HiveOS dashboards?A: No. HiveOS telemetry collects only hardware and miner-level stats. Alephium blockchain data requires external integration via Prometheus exporters or manual RPC polling outside HiveOS scope.