When a mining pool stops supporting a coin, first check which services are ending and their deadlines. Save relevant records, follow the instructions for remaining balances, and stop sending deposits to addresses whose deposit service has ended. If your mining connection is affected, choose a compatible destination, update your settings, and confirm that shares are being accepted before the cutoff.

Not every coin discontinuation requires a hardware migration. If the pool is only ending support for a merged-mined coin while your primary coin's mining service continues, you may be able to keep your existing connection. The pool's notice determines what action is needed; it does not, by itself, mean that the coin's network has stopped operating.

1. Confirm Which Services and Connections Are Affected

Read the discontinuation notice in full. Check whether it affects mining, deposits, withdrawals, conversions, or access to historical records. Note the time zone and any separate deadlines for each service.

Distinguish between three situations:

• A directly mined coin is discontinued: If your miner connects to the affected service, you need to choose another destination before that connection stops working.
• A merged-mined coin is discontinued: If the primary mining service remains available, changing your miner's connection may be unnecessary. Check which rewards and asset services are affected.
• The entire pool is closing: Review every mining connection you maintain with that pool and follow its instructions for records and remaining balances.

For example, ViaBTC's SYS discontinuation notice stated that SYS mining and deposits would end on June 29, 2026 (UTC+8), followed by SYS asset-management services on July 20, 2026 (UTC+8). It explicitly stated that BTC mining and the other merged-mined coins listed in that notice would remain unaffected. In that situation, the end of SYS support did not itself require a BTC miner to change pools.

2. Save Records Before Access Ends

Historical data for the discontinued service may become unavailable. Before the relevant deadline, export available records and save any settings you may need:

• Earnings history for the affected coin
• Deposit, withdrawal, and conversion history
• Worker names and relevant pool settings
• Payout method and payout-address settings
• Miner connection details needed for a migration, if applicable

Use the exact export deadline in the notice. If it specifies “24:00” on a particular date, that means midnight at the end of that date—the same instant as 00:00 on the following date. It does not imply a full extra day before service ends. Check export options early enough to save all the records you need.

3. Handle Remaining Balances and Stop Deposits on Time

Mining, deposit, and withdrawal services may end at different times. Record each deadline separately and follow the pool's instructions for withdrawing or otherwise handling your balance.

Do not assume the pool will automatically pay every remaining balance. Check the applicable minimum withdrawal amount, supported withdrawal options, and any instructions for balances below the usual threshold. If the notice leaves your situation unclear, contact the pool's official support before the deadline.

Once deposit service ends, do not send funds to the affected coin's old deposit addresses. Check any saved transfer instructions or automatic transfers that could continue sending funds there. The SYS notice cited above explicitly warns against deposits to old addresses after deposit service ends.

4. Decide Whether Your Hardware Needs a New Destination

If only a merged-mined coin is affected and the pool confirms that your primary mining service continues, you may keep the current connection. Handle the affected coin's records and balance according to the notice, and confirm that primary-coin mining remains operational.

If your mining connection will end, two common options are:

Continue mining the same coin at another pool. This is generally the more direct option. Confirm that the destination supports your hardware and connection protocol, then use its current setup instructions.

Redirect the hardware to another compatible coin. Confirm that your miner model and firmware support the target coin's proof-of-work algorithm. ASIC hardware is designed for specific algorithms; changing the pool address does not make it compatible with a different hashing algorithm. Algorithm compatibility is a prerequisite, and the destination pool's setup requirements still need to be checked.

5. Compare Pool Terms Before Moving Hashrate

Before selecting a destination, compare the factors that affect your setup and payouts:

• Supported coin, mining algorithm, and hardware requirements
• Available payout methods and pool fees
• Minimum payout amount and payment schedule
• Connection endpoints and regional availability
• Account-security controls and worker-monitoring tools

Payout methods do not necessarily carry over between pools. For example, ViaBTC's payment-method documentation describes PPS+ as paying for valid shares through a PPS component, with transaction fees allocated using PPLNS. Under PPLNS, payouts depend on blocks actually found and the miner's qualifying shares in the pool's specified window. Confirm the destination's current rules before choosing a method.

6. Update Miner Connections and Pool Account Settings

Use the destination pool's current official documentation. A migration involves two groups of settings that should be checked separately.

On the miner: Enter the required mining URL and port, account or wallet identifier, worker name, and password field where required. Check any protocol requirements stated by the pool.

In the pool account, where applicable: Confirm the payout method, payout address, and other available payment settings. Some pools use a wallet-based account model, so follow the instructions for that specific service.

Stratum commonly carries mining work and share-related information between a miner and a pool; it does not mean that account-level withdrawal settings automatically transfer. The Bitcoin Developer Guide explains this mining communication process.

You may be able to reuse a worker label or payout address where supported, but verify each setting rather than assuming the previous configuration will work unchanged.

7. Check Backup Connections Where Supported

If your miner's firmware supports backup pool entries, configure them according to the device's documentation. Use compatible endpoints and valid credentials, and check the priority order.

Review existing backup entries as well: an old endpoint for the discontinued service should not remain a fallback destination. A backup connection can help with some connection failures, but its behavior depends on the hardware, firmware, and type of interruption.

8. Verify the Setup Before the Cutoff

After reconfiguration, confirm that:

• The miner is connected to the intended endpoint
• The destination pool shows the expected worker or account
• Shares are being submitted and accepted, with any rejected-share messages reviewed
• The selected payout method matches your intended choice
• The payout address is your intended receiving address and meets the pool's coin and network requirements

Dashboards may take time to update. Follow the destination pool's guidance rather than using a universal waiting period. Allow time before the old service ends to identify and resolve connection problems.

If you retained your connection because only a merged-mined coin was discontinued, confirm that the primary mining service continues to show accepted work and that you have completed the separate record and balance steps for the affected coin.

Conclusion

A pool discontinuation calls for action based on the services actually affected. Start with the official notice, save records, handle remaining balances, and stop deposits by the applicable deadlines. Migrate hardware only when the mining connection is affected or you choose another destination. When you do move, compare pool terms first, use current setup instructions, and verify accepted shares before the cutoff.

FAQ

Does a pool ending support for a coin mean the coin's network has stopped?

Not necessarily. The notice describes that pool's service decision. The blockchain may continue operating with other miners, so a pool announcement alone does not establish that the network has stopped.

Do I need to move my BTC miner if a merged-mined coin is discontinued?

Not necessarily. If the pool confirms that BTC mining remains unaffected, you may keep your existing connection. Follow the separate instructions for the discontinued coin's earnings records and remaining balance.

Will my remaining balance be paid out automatically?

Do not assume so. Follow the pool's notice and applicable withdrawal rules, including any deadlines or minimum amounts. Contact official support before the deadline if your balance cannot be handled through the available options.

Can I point my ASIC at another coin?

Only if the hardware and firmware support that coin's mining algorithm and the destination's setup requirements. Confirm compatibility before changing the connection or comparing expected returns.

Do my old pool settings transfer automatically?

No. Check the destination's connection requirements and payment settings separately. Some values may be reusable, but they must be verified against the new pool's current documentation.

How do I know the migration is working?

Confirm that the intended worker appears at the destination pool and that shares are being accepted. Also check your payout method and receiving address. Allow for the dashboard's documented update delay, and investigate connection or rejected-share errors before the old service ends.