Migrating workers between pools.

01 Let pending shares settle first

Moving miners cleanly is mostly about timing, not configuration. On a PPLNS pool your recent shares sit in the window waiting for the next block, and any attributed balance sits as pending until it crosses the pool’s settlement threshold. If you yank every miner off the old pool the instant you decide to move, that pending balance is left behind mid-flight.

So begin by checking where you stand on the old pool: look at the pending balance against the threshold, and decide whether to keep hashing there long enough to cross it.

02 Point miners at the new URL

The move itself is a one-line change per miner: swap the old Stratum URL for the new one and restart. Keep the same wallet address as the username so attribution on the new pool lands on the same destination.

Only the host changes. The address, worker name and placeholder password stay exactly as they were.

03 Use failover during the cut-over

You do not have to switch every machine in one stroke. Most miners accept several pool entries and try them in order, so list the new pool first and the old one as a backup beneath it. The miner moves to the new listener immediately, but if anything is wrong with it the rig falls back to the old pool instead of going dark.

A staged approach works well: move one or two rigs first, confirm they behave on the new pool, then roll the rest. Keeping the old entry as failover means a surprise during the move costs you idle time, not a fleet sitting offline.

04 Confirm and finish the move

Before you remove the old pool entirely, confirm two things. On the new pool, each worker name should be connected, accepting shares and showing a recent last-seen time. On the old pool, the pending balance should have settled to your address at the threshold.

Once every worker is healthy on the new pool and nothing is left pending on the old one, remove the old failover entry and the migration is complete.