Solo Mining Setup Checklist: Clean First-Run Workflow

Most First-Run Problems Are the Same Three Mistakes

We've walked enough people through their first solo mining setup on MySoloPool to know the failure pattern by now. It's almost never the ASIC. It's a wallet address in the wrong format, a stratum endpoint typo, or someone scaling to twenty workers before confirming the first one is even submitting valid shares. This checklist exists so you catch that stuff in the first hour, not the first week.

Before You Touch a Worker

• Confirm your wallet address format matches what the pool expects, and back up the seed or key somewhere that isn't a screenshot on your phone.
• Set both a primary and a backup stratum endpoint before you enable a single worker — not after the first disconnect.
• Pick a worker naming convention now. "worker1, worker2, worker3" is fine until you have twelve of them and a fault to chase.
• Write down the expected hashrate baseline per model — an S19 XP should sit around 140 TH/s, an S21 around 200 TH/s. If a unit reports 60% of that, something's wrong before it ever submits a share.

Bringing Workers Online

1. Power up one worker first and watch for accepted shares before touching anything else.
2. Let it run 30-60 minutes and track the stale and reject rate. Anything consistently above 1-2% rejects on a stable connection usually points to a network or clock issue, not the miner itself.
3. Scale the rest in small batches — five or six at a time — so a bad batch doesn't get lost in the noise of forty units coming online at once.
4. Check the dashboard worker search for every worker name and confirm status matches what you expect, not just that something is "online."

After the Run

Before you walk away, capture the accepted/rejected trend, note any reconnect loops and whether you actually resolved them or they just stopped happening, and manually test both the primary and backup endpoint by failing over on purpose. It takes ten minutes and it's the only way to know your failover actually works before you need it at 2 a.m.

If share quality degrades during scale-up, roll back to the last stable worker batch and troubleshoot there instead of pushing forward blind.

Honest caveat: even a clean setup doesn't guarantee a block. Solo mining variance is real, and a perfectly configured rig can run for months without a hit depending on your share of network hashrate. This checklist just makes sure a bad result is bad luck, not a bad wallet address.

Keep your setup notes from every rollout — worker counts, baseline hashrate, any quirks with that firmware version. Six months from now when you're troubleshooting a new batch of hardware, that log is worth more than you'd think.

The Mistake We See Most Often

The one that trips up new solo miners more than any other: they set a backup stratum endpoint in the config, never actually test it, and assume it'll kick in automatically during an outage. Some firmware handles failover cleanly. Some doesn't, and just sits there retrying the dead primary until someone notices the hashrate dropped to zero. Test the failover on purpose, on a day when it doesn't matter, instead of finding out during an actual outage that it doesn't work the way you assumed.

One more thing worth saying plainly: this checklist assumes your network and power are already stable. If you're dealing with flaky internet or a circuit that trips under load, fix that first — no amount of careful stratum configuration solves a hardware problem one layer down.