Binance will discontinue its mining pool and related products on November 10, according to an October 13 notice. The shutdown starts at 07:00 UTC and covers Pool Savings, cloud mining, the transaction accelerator and associated alerts and APIs, not just the pool's public entry page.
The notice creates an operational deadline for miners: work submitted after the cutoff will not be credited. Binance says its services are expected to continue normally until then. It describes the decision as part of a product review, without providing a more specific explanation.
Two deadlines, different jobs
Mining connections and Stratum endpoints will be disabled at the service cutoff. Binance asks users to redirect their equipment beforehand, review Savings positions and complete necessary account-verification steps by November 10 at 23:59 UTC. Historical pages are scheduled to remain available until November 24 at 07:00 UTC.
Eligible earlier rewards and settlements remain subject to product rules, account status and compliance checks. The announcement is not an unconditional refund promise. Its schedule also does not say that keeping access to a historical page permits continued mining after the service has stopped.
For an operator, connection settings and account paperwork are separate tasks. Completing an identity check does not repoint a miner. Conversely, changing a pool address does not resolve a remaining balance or supply the records needed to reconcile earlier payouts.
A pool exit is not Bitcoin switching off
A mining pool combines participants' work and distributes rewards under its own payout rules. An individual miner uses a pool endpoint to submit shares: evidence of work that lets the operator account for participation. A share is not the same thing as a successful Bitcoin block, and an equipment status light alone does not prove that work is being credited.
Changing providers can therefore preserve the same hardware's role in mining while changing the party that receives its submissions and administers its payouts. A useful migration check distinguishes an established network connection from accepted shares and from actual payment records. These are different observations, and any one of them on its own gives an incomplete picture.
Binance's exit also should not be described as a preannounced reduction in Bitcoin's network difficulty. Difficulty is a protocol measure, not a setting controlled by one commercial pool. Our guide to Bitcoin mining difficulty explains why changes in network work and changes in a provider's business are different questions.
Record keeping outlasts the connection
The practical issue is continuity: where equipment submits work, how an account reconciles the final period and which records remain available afterward. Saving one's own reports is useful because a service closure can remove the interface normally used to check old activity.
This report does not estimate how much computing power will move to another pool or leave the network. Neither outcome follows automatically from the notice. The verified development is a scheduled end to Binance's services; its eventual effect on mining distribution requires evidence after operators respond.