A mining pool can lose its customers without losing a single machine. Binance is reportedly shutting down its Bitcoin pool, but where its miners will go, or whether they will keep mining, is still unknown.
- Reported cutoff: 07:00 UTC on November 10, 2026.
- No confirmed destination: Miners may switch pools, mine solo or pause.
- Immediate concern: Final share records, account checks and reward settlement.
- Bitcoin’s rules: A pool closure does not change consensus or shut down the network.
A notice attributed to Binance, reportedly announced on October 13, covers Binance Pool, Pool Savings, Cloud Mining and the transaction accelerator. It says Binance will disable the pool’s Stratum URLs and mining endpoints at 07:00 UTC on November 10, 2026. Shares submitted after the cutoff will not be accepted or credited. Eligible shares submitted before then will count toward the final reward calculation.
The reported notice gives customers until 23:59 UTC on November 10 to complete any required identity verification for processing. Historical pool pages are expected to remain accessible until 07:00 UTC on November 24, and Binance asks customers to download their records. These are separate deadlines. The notice does not say the November 24 date extends the time to submit shares or complete verification. Confirm the details in Binance’s official notice.
The reported terms do not say when customers will actually be paid, the total amount owed or how outstanding balances will be handled. Before making decisions, miners should confirm the deadlines and settlement conditions in Binance’s official notice and the terms that apply to their accounts.
Where could Binance’s miners go?
No public list identifies where Binance Pool customers will go next. Some may move to other pools. Others could split their machines across providers, mine independently or temporarily switch them off. Solo mining avoids a pool’s payout rules, but rewards are highly variable, and it may not be practical for many operators.
Hosting, financing or equipment contracts could limit an individual miner’s ability to change configurations. The reported closure notice does not say whether such restrictions apply to any particular customer.
Reported hash-rate estimates also need a careful look. Reporting that cites Hashrate Index puts Binance Pool at about 9.2 exahashes per second (EH/s) in October, or below 1% of the network. But Hashrate Index’s available pool data are inconsistent. One summary lists Binance at 0.41%, while a table shows 0.64% and 7.4 EH/s, with no clear snapshot date. Those figures neither confirm the October estimate nor establish a reliable trend in Binance’s share.
A change in another pool’s reported share would not, by itself, prove that it received Binance’s miners. Network hash rate, miners switching on or off, short-term changes in block production and differences in measurement windows can all affect reported percentages. The distribution of miners will be clearer after the shutdown. A single snapshot cannot predict it.
What miners should check before switching
A mining pool combines work from independent miners and distributes rewards according to a payout method. Miners connect their machines using details called Stratum URLs or mining endpoints, receive work and submit “shares.” These are units of work the pool uses to track each participant’s contribution. A share is not necessarily a Bitcoin block.
Hashrate Index lists Binance Pool as using full pay per share (FPPS). In general, FPPS pays miners based on the expected value of their work, including block rewards and transaction fees. That can smooth out short-term swings in block-finding luck. The provider’s rules determine the exact fee treatment, payment obligations and settlement terms. The label alone is no substitute for reading those rules.
Another common model, pay per last N shares (PPLNS), bases payouts on a pool’s blocks and a defined window of submitted work. The details depend on the pool’s share window and other rules, and earnings may vary more over short periods. When comparing providers, miners should check fees, payout thresholds, settlement timing, policies on rejected or stale shares, and endpoint reliability. A guide to Bitcoin mining pool payouts explains how these methods differ. Pool profiles and comparisons can help miners assess provider fees and decentralization.
Custody matters, too. Rewards held in a pool or exchange account before withdrawal carry different risks from payouts sent to a wallet controlled by the miner. Check who holds accrued rewards, how withdrawals work and which identity checks apply.
- Download account records and save pool statements before access ends.
- Keep local mining logs and compare submitted shares with account records and the final settlement.
- Review the new provider’s payout method, fees, thresholds, schedule and transaction-fee treatment.
- Confirm where rewards are held and how withdrawals and identity checks work.
- Test the new endpoint and monitor rejected or stale shares, which can reduce effective earnings.
A pool can coordinate work, not rewrite Bitcoin’s rules
In a conventional pool arrangement, the pool generally prepares a block template, a candidate block containing transactions selected for miners to work on. Pool operators can influence which transactions their participants attempt to include.
That does not give them control over Bitcoin’s consensus rules. Bitcoin nodes independently check whether a proposed block is valid. A pool cannot make an invalid block valid by gathering more hash power. Miners who object to its policies can choose another pool or arrangement.
Miners choosing a new pool may also want to consider who controls transaction selection. Stratum V2 and job negotiation are designed to give participating miners more say over block templates, depending on how a provider implements them. A provider’s involvement in Stratum V2 work does not mean ordinary customers can use job negotiation. Check what the provider actually offers.
Three measures are easy to mix up. Hash share estimates the computing power directed to a pool. Block share counts the blocks attributed to it over a period and can fluctuate with mining luck. Template control concerns who selects transactions. None of these measures alone captures the full picture of mining decentralization.
Key questions about the Binance Pool shutdown
-
When is Binance Pool reportedly scheduled to stop accepting shares?
The reported cutoff is 07:00 UTC on November 10, 2026. Eligible shares submitted before then are to count toward the final reward calculation, but the reported notice does not specify a payment date.
-
Where will Binance’s Bitcoin miners go?
That is not known. Miners may join other pools, split their machines, mine solo or pause operations.
-
Will Bitcoin stop producing blocks?
No. The closure affects a pool service, not Bitcoin’s consensus rules or the underlying mining machines. Miners using other pools or arrangements can keep producing blocks.
-
How much hash power is leaving Binance Pool?
Reporting has cited about 9.2 EH/s in October, but available Hashrate Index figures conflict and lack a clear snapshot date. Treat the estimate cautiously. It is not a confirmed count of machines that will move elsewhere.
-
What should customers do before the reported deadlines?
Verify the deadlines and account-specific terms with Binance, complete any required identity checks, download records and review how rewards will be settled. Check any separate hosting, lending or cloud-mining agreements, too.
For miners, the priority is to save records and understand the settlement terms before changing endpoints. The broader effect on pool distribution will become clearer once post-shutdown data can be compared across consistent dates and measurement windows.
