I’ve been tightening an Ergo setup on Hive with Rigel and wanted one practical checklist: a clean flight sheet, a few stability checks, and the habits that saved me the most time. Not a profitability post.
- Flight sheet basics
- Coin: ERG (Autolykos 2).
- Wallet: your own ERG address, copied twice and checked.
- Miner: Rigel. It’s been stable for me on Autolykos 2.
- Pool: any remote pool, or “Custom / Configure in miner” if you point the rig at a machine on your own LAN.
If you run a local stratum on your LAN, Rigel wants something like stratum+tcp://:. Make sure the host’s firewall allows the port and the rig can actually reach the host’s IP. That’s where most “miner starts but no shares” problems come from.
- Tuning checks that matter more than copying someone else’s clocks
- Autolykos 2 is memory-heavy, and the miner briefly rebuilds its dataset when block height changes. Your sustained hashrate will sit a bit under the peak number Rigel flashes, so plan around the average, not the highlight.
- Watch free VRAM, not just whether the miner started. The requirement grows as the chain grows, so older/smaller cards get squeezed over time.
- Change one variable at a time: power limit, then memory, then core. Keep a known-good profile you can roll back to.
- Measure wall power if you can, not just the watts the miner reports.
- Don’t treat someone else’s OC as a target. Cards, risers, and room temps differ.
- Habits that saved me headaches
- Name flight sheets clearly (coin + miner + pool) so switching is one click and hard to mess up.
- After any change, let it run long enough to see rejected/stale shares, not just hashrate.
- Keep notes per card. Two “identical” GPUs often like different memory clocks.
- Questions for other Hive users
What’s been stable for Autolykos 2 lately on your cards with Rigel or other miners? Any flight-sheet gotchas with a custom LAN stratum (stale jobs, firewall, reaching the host from the rig)?