Binance Pool Shutdown:
Bitcoin Miner Migration Guide
November 10 deadline · Final settlement · Replacement pool checks · Backup Stratum setup · Post-migration monitoring
On This Page
1Quick Answer: Move Your Miners Before the Binance Pool Cutoff
Binance will discontinue Binance Pool and its related mining services on November 10, 2026 at 07:00 UTC, which is 15:00 in Beijing. At the cutoff, Binance says it will begin disconnecting mining connections and disable its Stratum URLs and mining endpoints. Shares submitted after that time will no longer be accepted, processed, or credited.
Miners do not need to shut down or replace their ASICs. They need to point each machine to a different Bitcoin mining pool, confirm the payout address and worker format required by that provider, and verify that the new pool is receiving accepted shares. A careful migration also includes saving Binance records, checking remaining balances, configuring backup endpoints, and monitoring pool-side hashrate for at least one full day.
Binance has instructed users to reconfigure their miners before the deadline. A miner left on a disabled endpoint can continue consuming electricity while producing no credited pool work.
Bitcoin miners can redirect compatible SHA-256 equipment to another Bitcoin pool without changing the machine's algorithm. The closure does not alter Bitcoin's proof-of-work rules or stop the network.
2What Binance Is Closing and When
Binance published its closure notice on October 13, 2026. The scope extends beyond the basic mining endpoint. It includes Binance Pool, Pool Savings, Cloud Mining, Transaction Accelerator, Telegram hashrate alerts, email notifications, and mining-pool API services.
| Deadline or Period | Published Action | What Miners Should Do |
|---|---|---|
| Before Nov 10, 07:00 UTC | Pool remains scheduled to operate normally | Save records, select a replacement, and prepare new Stratum details |
| Nov 10, 07:00 UTC | Mining connections begin disconnecting; endpoints are disabled | Complete the switch before this time |
| After the cutoff | Eligible balances, refunds, or settlements are processed under applicable rules | Keep the account accessible and complete required verification |
| By Nov 10, 23:59 UTC | Binance requests completion of any required identity-verification steps | Resolve account restrictions that could delay settlement |
| Until Nov 24, 07:00 UTC | Pool pages remain available for historical records and payout status where available | Download statements before the pages become inaccessible |
Eligible shares submitted before the service cutoff remain part of the final reward calculation under the applicable Binance Pool rules. That does not remove the need to export records. Save worker histories, payout statements, account balances, settlement status, and any information needed for accounting before access ends.
3What the One-Block Week Shows, and What It Does Not
Immediately before the closure, public block-identification data showed Binance Pool finding one of roughly 925 Bitcoin blocks over a seven-day observation period, or about 0.11%. The most recent identified Binance block in that report was block 974,743, mined on November 6 at 01:15 UTC. It contained 1,353 transactions and paid about 3.134 BTC including fees.
This is useful evidence that Binance Pool's visible block-production share had become small. It is not an exact measurement of its remaining hashrate. Mining is probabilistic: a pool can find more or fewer blocks than its expected share over a short window. A longer hashrate series, accepted-share data, and multiple observation periods provide a stronger estimate than a single week.
For a live view, use a transparent block-data source such as the mempool.space mining dashboard. Treat current rankings as a snapshot, not a permanent recommendation.
4What to Complete Before the Cutoff
Prepare the replacement first, then change the miners. This keeps the interruption short and creates a clean record of which configuration was used.
- Export Binance records: save worker history, earnings, payout records, balances, and settlement status.
- Check account access: confirm two-factor authentication, email, identity verification, and withdrawal settings still work.
- Confirm the final payout path: verify the wallet or account that will receive eligible remaining rewards.
- Select a replacement: compare payout method, fee, threshold, server location, custody model, account requirements, and support.
- Prepare official Stratum addresses: copy endpoints only from the selected pool's official documentation.
- Create worker names: use a consistent site-device format that makes failures easy to identify.
- Configure backups: use the miner's second and third pool fields for compatible Bitcoin endpoints.
- Document the old settings: take a screenshot or export the configuration before editing.
A shutdown creates an opportunity for fake support accounts, copied pool websites, malicious firmware, and false Stratum addresses. Do not share seed phrases or private keys. A legitimate mining pool needs a payout address or account configuration, not control of your wallet.
5How to Compare Replacement Bitcoin Mining Pools
There is no single best pool for every miner. A large hosted fleet may prioritize contract support, reporting, and access controls. A small operator may care more about payout threshold, regional latency, non-custodial settlement, or Lightning payouts. Use the table as a starting point and verify the provider's live terms on the day you switch.
| Pool | Current Published Model | Potential Fit | Verify Before Switching |
|---|---|---|---|
| Foundry USA Pool | FPPS; institutional controls and KYC | Commercial operators that value formal access controls and reporting | Eligibility, onboarding, contract terms, withdrawal controls, regional endpoint |
| AntPool | BTC page lists FPPS and PPLNS | Miners wanting a large multi-coin provider | Current fee, threshold, account security, server location, payout timing |
| F2Pool | BTC FPPS or PPLNS; official support page publishes fees and thresholds | Miners wanting regional endpoints and selectable payout structures | Current commission, threshold, payout-address hold period, closest server |
| ViaBTC | PPS+ or PPLNS; SOLO was discontinued in May 2026 | Miners comparing steady-share and block-dependent methods | Current fee schedule, payout method, account verification, server latency |
| Braiins Pool | FPPS with on-chain and Lightning payout options | Operators wanting detailed worker controls or low-value Lightning payouts | Pool fee, payout rule, firmware-linked discounts, regional endpoint |
| OCEAN | TIDES, direct coinbase-style distribution where possible, optional DATUM | Miners prioritizing non-custodial payout and block-template decentralization | Variance, payout threshold, Lightning option, DATUM requirements |
Do not choose only by weekly block share. Large pools generally reduce payout variance, but concentration, custody, policy, account restrictions, payout thresholds, and regional latency also matter. Smaller or non-custodial designs may improve miner control while exposing the operator to greater payout variance or different setup requirements.
For the economic difference between regular pool mining, solo pools, and true solo mining, use the separate solo mining versus pool mining guide. This page focuses on migration from a closing provider.
6Step-by-Step Miner Migration
- Open the miner's local dashboard. Use the device IP on the local network. Do not expose the admin interface directly to the public internet.
- Record the current configuration. Save the existing pool URLs, worker name, performance mode, and firmware version.
- Enter the new primary endpoint. Use the exact Stratum URL and port from the replacement pool's official setup guide.
- Enter the required identity. Depending on the pool, this may be an account and worker name or a Bitcoin payout address plus worker suffix.
- Add secondary and tertiary endpoints. They must support Bitcoin's SHA-256 work and the pool format expected by the miner.
- Save and apply. Reboot only if the miner interface or manufacturer documentation requires it.
- Watch the local status. Confirm that the pool shows connected and that hashrate begins to stabilize.
- Check the new pool dashboard. Accepted shares should appear and the worker should become online.
Move one or two machines first. After the new pool reports valid shares and the payout identity is correct, apply the same verified configuration to the remaining fleet. This limits the cost of a typo or wrong worker format.
7How to Verify the Switch Worked
A green light on the miner is not enough. Compare local and pool-side evidence over several time windows.
| Check | Expected Result | If It Fails |
|---|---|---|
| Pool connection | New primary endpoint shows active | Recheck host, port, DNS, firewall, and TLS requirements |
| Accepted shares | Accepted count rises within the provider's normal reporting delay | Check worker syntax, algorithm, clock, firmware, and endpoint |
| Rejected or stale rate | Low and stable after warm-up | Try a closer server and inspect network quality or overclock settings |
| Pool-side hashrate | Approaches the miner's normal average over time | Compare 1-hour and 24-hour windows before diagnosing a hardware fault |
| Payout identity | Correct account or wallet is displayed | Stop expansion and correct it before migrating more machines |
| Backup behavior | Miner can fail over without changing algorithm | Test during a controlled window and restore the primary afterward |
Pool-side hashrate is calculated from submitted shares and can fluctuate around the local reading. Compare longer averages before deciding that performance has fallen. Keep the old and new records separate so the final Binance settlement can be reconciled with the first payout from the replacement pool.
8What Binance Pool's Exit Means for Bitcoin
When a pool closes, independent miners can redirect their equipment to another coordinator. The physical hashrate does not necessarily disappear; it may be redistributed among existing pools. Bitcoin's difficulty and block-production rules continue to operate at the network level.
The more important question is where the hashrate goes. If most displaced miners choose the same large provider, pool-level concentration can rise even though ownership of the underlying machines remains distributed. Miners can therefore consider not only payout stability but also template control, custody, transparency, geographic diversity, and the concentration effect of their choice.
Binance's one-block week suggests its visible contribution had already become small before the shutdown, so the immediate network effect is likely to be limited. The operational effect on individual miners is more direct: anyone who fails to change endpoints can lose credited mining time.
9Binance Pool Shutdown FAQ
When does Binance Pool close?
Binance says pool services will end on November 10, 2026 at 07:00 UTC, or 15:00 Beijing time. Mining endpoints will be disabled and shares submitted afterward will not be credited.
Do I need to replace my Bitcoin miner?
No. A compatible SHA-256 ASIC can normally be redirected to another Bitcoin mining pool by changing the Stratum endpoint and worker or payout details.
Will Binance automatically send my miner to another pool?
The official notice tells users to disconnect and reconfigure their miners. Do not assume an automatic migration or redirect.
What happens to unpaid Binance Pool rewards?
Binance says eligible outstanding rewards, balances, refunds, or settlements will be processed after the cutoff under applicable product rules, account status, risk controls, compliance checks, and law. Save records and complete required verification.
Which replacement mining pool is best?
The best choice depends on payout method, fee, minimum threshold, latency, custody model, account requirements, transparency, and support. Verify live terms directly with each provider before switching.
Does one block out of 925 mean Binance had exactly 0.11% of hashrate?
No. It is a seven-day observed block share. Short-term block discovery is random, so it cannot establish an exact hashrate figure by itself.
10References and Data Sources
Deadline and settlement instructions come from Binance's official announcement. Current pool features come from each provider's own documentation. Fees, thresholds, endpoints, and eligibility can change and must be checked again before migration.
- Binance: Notice on the Closure of Binance Pool ServicesOfficial scope, cutoff, settlement, record-access period, and required user actions.
- CoinDesk: Binance Pool Finds One Block in a Week as Shutdown NearsTime-stamped report using public block attribution and explaining short-window variance.
- mempool.space Mining DashboardLive Bitcoin pool rankings, blocks, estimated hashrate, difficulty, and reward data.
- Foundry USA Pool: FPPS MethodologyOfficial explanation of accepted shares, daily calculation, and FPPS settlement.
- AntPool: Official BTC Pool PageCurrent supported earnings modes, threshold, and network information.
- F2Pool Mining SupportOfficial BTC payment methods, fees, thresholds, regional Stratum servers, and payout guidance.
- ViaBTC Pricing and Payment MethodsOfficial PPS+ and PPLNS descriptions and current fee framework.
- Braiins Pool: Rewards and PayoutsOfficial FPPS, fee, payout-rule, on-chain, and Lightning details.
- OCEAN: Pool Model and SetupOfficial non-custodial, TIDES, DATUM, fee, and payout information.
Final Verdict
Binance Pool's closure is primarily an operational deadline for miners, not a threat to Bitcoin's continued operation. The correct response is to preserve account records, select a replacement using current official terms, configure primary and backup endpoints, and verify accepted shares before expanding the migration.
Do not choose a pool from a static popularity list alone. Compare payout risk, fees, thresholds, custody, security, latency, transparency, and concentration. Then monitor the new setup long enough to confirm that local hashrate is becoming credited pool-side work.
Leave a comment
This site is protected by hCaptcha and the hCaptcha Privacy Policy and Terms of Service apply.