F2pool.kz closes on November 21: move miners, check balances and save records
Source report: 2026-10-21 · Editorial analysis published: 2026-11-19
The October 21 notice is now close to its cutoff: 00:00 UTC on November 21. The Kazakhstan site will stop accepting work and account access will end; f2pool.com is unaffected.

A deadline for the Kazakhstan site
F2pool.kz is approaching its announced closure: all its pool products, related services and website operation end at 00:00 UTC on November 21, 2026. Existing users can mine there until November 20 at 23:59 UTC. For someone still connected, the useful action is to move the machines before the cutoff, settle the account’s payout details and save the records that will soon become inaccessible.
This is a deadline reminder checked on November 19, not a claim that the closure was first announced today. The official notice is signed October 21 and says new registrations stopped that day. It explicitly limits the shutdown to f2pool.kz; the main f2pool.com platform continues normally. A shared brand does not mean the two domains have the same service status or that an account automatically moves between them.
Put the cutoff on the right clock
The notice uses UTC. The final shutdown corresponds to 02:00 on November 21 in Kyiv and 05:00 that morning in Kazakhstan. A reader seeing November 20 as the last mining day should therefore keep the stated time zone attached. The important boundary is the same instant worldwide, rather than midnight according to the miner’s computer, the browser’s language or the operator’s local date.
After the cutoff, the site says it will stop calculating revenue, stop accepting hashrate submissions and terminate account access. These are separate operational consequences. A powered ASIC is not evidence that its old destination still accepts payable work. Likewise, being able to open an account before closure does not promise that the same login or history will remain available afterward. Plan the change while the current services are still reachable.

Balance and receiving address come first
The official instructions ask users to bind a receiving wallet address or withdraw their account balance completely before closure, and link to address and withdrawal tutorials. Open those instructions from the official notice and inspect the conditions applying to the actual account. The notice does not specify a universal minimum balance waiver, an account migration or a guaranteed post-closure claim window, so those should not be invented from the general word withdrawal.
Check the currency, receiving address, available balance and any pending payment separately. An address saved in settings is not a transaction receipt. If a transfer has been made, preserve its identifier and compare its status with the receiving wallet. If the account has a restriction or its balance cannot be withdrawn through the normal route, contact official support before access ends rather than relying on an assumed automatic process after the website is gone.
Move the connection, then check accepted work
For the ASIC connection, prepare the destination pool’s current server address, worker name and other required account settings. Confirm that the new destination supports the intended coin and hardware and that its registration and regional rules allow the account. The closure notice says f2pool.com is unaffected; it does not promise that every f2pool.kz user is eligible there or that any other pool is a recommended substitute.
After changing settings, check the destination pool’s worker display and accepted shares. A share is a partial mining result used by a pool to count work. The miner’s local speed display alone cannot show that the replacement pool is crediting it. Check backup server settings too: an old fallback pointing to f2pool.kz could send a machine back to the closing service if its first connection fails. Record which machines have actually switched successfully.

Export the history while it is accessible
F2pool.kz asks users to download or save mining, hashrate and revenue records in advance, because account data becomes inaccessible after services stop. Keep the account identifier, the period covered, payout history and worker records needed for reconciliation. Use the account’s available export functions or save the information it displays. The notice does not promise a particular export format or a permanent public archive.
This is useful even for a small home setup. A pool balance belongs to one stage of the income record; a transaction in the blockchain belongs to another. Saving both helps match what the pool credited with what the wallet received. It also preserves a reference for a missing payment or a later accounting question. Protect the archive as account data, without adding passwords, recovery words or other wallet secrets to a spreadsheet of mining results.
Finish with three separate confirmations
The transition is easier to assess when split into three results: the machines submit accepted work at the chosen destination, the old account’s balance and payout status are understood, and the necessary history has been saved. One does not prove the others. A successful connection does not settle an old balance, while a completed withdrawal does not redirect a single ASIC. Check each result before treating the move as finished.
The reason to act now is the approaching November 21 cutoff, not a new change in Bitcoin’s mining rules or the closure of the whole F2Pool brand. Use the October 21 notice for the exact scope and official support links. Make the switch with time to confirm the result rather than leaving the account, the records and the machines until the same final minute. The current notice gives a clear endpoint for the Kazakhstan website, and no continuing account access afterward.
Source: F2Pool ↗ · Official wallet address configuration tutorial ↗ · Official balance withdrawal tutorial ↗
Mining calculator ↗

