What happens when one of the bigger names in crypto mining decides to walk away from the game? On November 10 at 07:00 UTC, Binance stops accepting mining shares. Any machine still pointed at its pool after that exact moment simply stops earning through it. I keep thinking about the operators staring at their controllers right now, wondering whether a quick config change is enough or if the real work starts after the machines reconnect.
Binance Pool Closing Forces a Hard Choice for Bitcoin Miners
The notice landed on October 13. It covers not only the mining pool but also Pool Savings, Cloud Mining and the transaction accelerator. The stated reason is a product review. No profit numbers. No detailed roadmap for customers. Just a firm deadline and a reminder to finish any identity checks by 23:59 UTC on the same day if you want smoother final settlement.
Hashrate estimates show the pool sitting around 9.2 EH/s in October. That is under 1 percent of the Bitcoin network. Back in December it was closer to 26 EH/s and 2.3 percent. The drop already tells part of the story. Miners have been leaving for months. The ones who remain now face a clean cutoff.
Historical pages stay visible until November 24 at 07:00 UTC. Anyone still using the service should download every hash history, payment statement and share record before that window closes. Changing pools does not move balances or tax records. Those stay behind unless the operator takes them.
The Practical Deadline Every Operator Must Respect
Binance disables its Stratum URLs and mining endpoints at the stated time. Shares submitted after the cutoff are neither accepted nor credited. Eligible work sent before that moment enters the final reward calculation. Outstanding balances and any refunds follow the product terms, account status and applicable rules.
Pool Savings users have their own checklist. They need to redeem or unsubscribe before the service ends. Cloud contracts and the accelerator shut under the same notice. Physical mining fleets and cloud contracts behave differently, so the reported hash power does not equal the number of people who must reconfigure hardware.
Some operators may already sit behind hosting providers or other arrangements. In those cases the person who actually controls the endpoint has to make the change. Waiting until the last hour raises the chance of a gap in credited shares if new settings, account approvals or backup addresses fail. That gap costs revenue. It does not stop the Bitcoin network from producing blocks.
Nine Exahashes Cannot Simply Vanish or Land in One Place
A mining pool gathers independent computing power and distributes rewards according to its chosen method. The 9.2 EH/s figure is an estimate drawn from observed activity over a period. It is not a fixed list of machines with signed transfer papers. Hash power already moves between providers, and different measurement windows produce different numbers.
Imagine every remaining machine jumped to a single large pool while the rest of the network stayed constant. The recipient would gain a little under one percentage point on a network above 1,000 EH/s. Spread the same amount evenly across three providers and each might pick up roughly three tenths of a point. Neither scenario is a forecast. The total network hash rate shifts with price, difficulty, seasons and new hardware. Published estimates rarely agree on the exact same snapshot.
Recent comparisons put the three largest pools—Foundry USA, AntPool and F2Pool—together near 64.2 percent. Earlier readings showed a slightly lower combined share with a different third-place name. Concentration numbers move when the ranking changes, not only when hash power relocates. If every remaining Binance miner chose those three leaders, the combined figure could edge toward 65 percent on a fixed base. If some operators pick smaller pools or solo mine, the measure can drift the other way.
Pool share of blocks is not ownership of the machines. Operators coordinate transaction selection and payout systems. Customers can still redirect their hardware. The real test of choice is whether viable alternatives exist for a given mine’s power costs, settlement needs and technical setup.
Payout Policy Often Decides the Destination
Binance ran full pay-per-share, or FPPS. In simple terms the method pays for submitted work based on expected block and fee value while the pool absorbs some of the variance in actual blocks found. Miners trade a degree of luck risk for steadier settlement and accept the pool’s fee in return. Exact accounting intervals and thresholds differ by provider.
Pay-per-last-N-shares systems link payments more tightly to blocks the pool actually finds during the relevant window. Stated fees can look lower, yet short-term revenue swings more. A smaller operation with regular power bills often prefers the predictability of FPPS. A larger firm with cash reserves may accept more variance for a better effective rate. Comparing headline fees without adjusting for fee treatment, stale shares, minimum thresholds and settlement timing can easily point someone toward the wrong partner.
Where the coins land matters just as much. A pool that sends Bitcoin straight to a wallet the miner controls creates one custody profile. Leaving rewards inside an exchange account creates another. The closure makes that distinction concrete. Machines can keep hashing until the cutoff while the final account balance follows a separate settlement path. Minimum withdrawal amounts and rules for changing payout addresses can outweigh a few basis points of advertised fee.
Technical fit counts too. A distant endpoint, shaky Stratum connection or poorly matched job assignments raise the rate of rejected or stale work. Electricity is paid for computations that may not earn full credit. Testing two backup endpoints and comparing credited shares against a machine’s reported hash rate gives clearer information than any global ranking.
Who Actually Chooses the Transactions Inside a Block
Under a standard pool arrangement the operator usually prepares the block template. Miners work on that template. The pool can include or exclude fee-paying transactions within consensus rules. A large share of hash power therefore carries influence over transaction selection even though the pool does not own the hardware or rewrite Bitcoin’s validity rules.
Work on Stratum V2 includes major operators. Job negotiation aims to give participating miners more say over the transaction set they mine, depending on actual deployment. Support for the working group does not guarantee every customer’s firmware currently builds its own template. An exiting miner should check the Stratum version in use, whether job negotiation is available on the new account, and whether the equipment can take advantage of it.
Transaction selection becomes relevant when a payment is controversial, when a regulatory request reaches an operator, or when fee revenue favors one set of transactions over another. A miner able to construct a valid template reduces reliance on a single operator’s preferences. The protection is incomplete. The provider still runs the endpoint, calculates payouts and sets participation conditions. Yet the migration moment is useful for comparing the control each candidate actually offers.
Block share charts have limits. Over short windows a pool can find more or fewer blocks than its true hash power predicts. Longer periods and multiple data sources give a clearer picture. Public attribution relies on coinbase identification or known payout patterns. Unidentified blocks can blur the view.
Earlier Pool Exits Offer Context Without Perfect Parallels
Other branded pools have closed in recent years. One major Asian operator shut its service after holding roughly 2 percent of network hash. Another exchange ended pool services earlier. These cases show that a pool can disappear while the underlying machines continue operating elsewhere. They do not prove identical motives for every closure. The current notice frames the decision as a product review and does not disclose operating losses.
Mining once formed a larger part of the business. Earlier lending programs targeted miners with substantial facilities. The present notice is silent on whether any related loans remain open or require separate action. Pool termination and credit agreements are distinct relationships. Neither the presence nor the absence of outstanding balances can be read from the shutdown text alone.
A provider may close a smaller service because support, compliance and payout guarantees cost more than the revenue justifies, or because management prefers to focus elsewhere. Those are general possibilities, not disclosed reasons. The sharp drop in estimated hash power shows the scale of departure, yet without fee income, staffing costs and financing exposure it cannot prove profitability. A miner picking a replacement should not assume larger hash share automatically equals stronger financial footing.
The Case for Smaller Pools and the Case Against Them
Sending work to a smaller operator can spread template decisions across more parties. A miner who values that property might accept greater short-term payout swings or a different settlement rhythm. Smaller size is not automatic safety or independence. Customers may still share a common custodian. Software may depend on larger infrastructure. Reserves backing FPPS payments may be thinner. Each operator has to be judged on its actual record.
Large pools bring their own strengths. They can fund reliable endpoints in multiple regions, stronger support teams and smoother payment systems. Higher block discovery rates reduce variance under methods that track actual wins. Firms carrying payroll and debt often prioritize predictable daily proceeds over abstract concentration statistics. The practical question is whether those advantages force miners to surrender template control and custody options they care about.
Earlier discussions of mining margins placed protocol upgrades beside rising cost pressure. An operator running close to break-even cannot make a purely symbolic pool choice without examining rejected work, fees and payment delays. A few basis points of savings lose value if records disappear or payments stall. A rational comparison sets a fixed period and calculates net Bitcoin actually credited per unit of accepted work.
How to Track Where the Hash Power Actually Lands
No public list names the next pool for every departing miner. The first usable signals will appear in attributed blocks and estimated hash power after the announcement, then again after the November 10 cutoff. Individual company disclosures can identify some moves, yet they will never cover every customer. The period before the shutdown matters because early leavers already reshape the numbers.
Consistent denominators are essential. A receiving pool’s absolute hash rate can rise while its percentage falls if the total network grows faster. A percentage can climb without any Binance customers if competing machines switch off. The strongest inference combines named migrations with a sustained rise in the recipient’s hash and block share plus a matching decline at the closing pool, all measured over the same interval.
Broader market conditions can hide a clean transfer. Bitcoin price, difficulty adjustments, electricity contracts and new equipment all affect whether machines stay online. The closure does not force every reported exahash to remain active the next day. Some fleets may pause for configuration, economics or hosting decisions. A lower share at the closed pool together with a smaller measured network does not prove permanent destruction of capacity.
The effect on ordinary users should stay narrow. Difficulty and remaining hash power set the long-term mining pace. Moving pooled equipment between endpoints changes coordination, not total computing power, provided the machines stay running. A temporary gap can alter short-term output, yet an exit under 1 percent does not forecast a network halt.
Fees Are Only One Line on the Miner’s Ledger
Suppose two pools quote 2 percent and 2.5 percent. On one Bitcoin of otherwise identical expected rewards the difference is 0.005 BTC. That comparison collapses if one provider excludes transaction fees from the base or routinely credits less of a machine’s submitted work. A transparent review places expected subsidy, fee sharing, pool charge, rejected shares and payout interval inside the same accounting window. Those inputs belong to the specific providers under consideration.
FPPS can require the pool to pay miners even when its own block wins temporarily lag expectations. That creates credit exposure to the operator. Methods more tightly linked to actual blocks shift short-term luck onto participants. Size may support the ability to absorb variance, yet the legal promise to pay and the custody of accrued balances remain central. A familiar brand cannot replace reading the payout terms.
Loans or hosting agreements can further limit options. A lender might require proceeds to land in a designated wallet. A hosting company might control configuration changes. Curtailment programs can shut power during expensive hours. The closure notice does not claim such arrangements apply to every user. It simply means each customer should verify who has authority to change the endpoint and whether reward flows are already pledged before treating the migration as a personal dashboard click.
Rewards should be compared both in Bitcoin and in the currency used to pay costs. An operator who pays electricity in dollars while holding BTC feels price moves independently of pool choice. A higher quoted Bitcoin payout paired with longer settlement can leave a thinly capitalized mine short of working cash. Scheduled payment and actual withdrawal into the chosen wallet are separate events.
What the Handover Looks Like on the Machines Themselves
Most mining equipment stores a primary pool endpoint, worker credentials and one or more fallback addresses. Moving requires a new account or payout identity, a fresh endpoint and a valid reward destination. Testing accepted shares and reported hash rate on a few machines before rolling the change across an entire fleet reduces the risk of repeating the same mistake at scale.
Stratum connections carry work and share submissions. They do not transfer historical reward balances from one company to another. A miner who changes the endpoint today begins accumulating credit under the new provider’s accounting while the old pool separately processes eligible prior shares. Keeping both statement sets is necessary to reconcile any period that spans the transition. The final payout may arrive after the last share left the closing pool.
Unexpected interruptions become easier to diagnose when three timestamps are recorded: the last accepted share at the old pool, the first accepted share at the new one, and the first new payout. The gap between the first two measures production lost to reconnection or misconfiguration. The wait until payment reflects the new pool’s threshold and schedule, not necessarily uncredited work. A pre-tested backup endpoint can shorten downtime if the primary new address fails.
The precise cutoff turns the event into an observable operational story. Listed mining firms can be asked where they redirected equipment. Disclosed payouts or hashrate before and after can be compared. Anonymous claims by a pool that it attracted former customers need independent corroboration. Sign-ups alone cannot prove sector-wide allocation.
Three Different Ways to Measure Concentration
Hash share approximates the computing power pointed at an operator. Block share counts blocks attributed over a period. Template control asks who selected the transactions inside those blocks. The three measures do not always move together. A pool can adopt job negotiation while keeping high hash share, reducing centralized transaction choice without reducing concentration in payout coordination. A miner can redirect work to a smaller pool that still relies on another firm’s hosted software.
The simple sum of the top three is sensitive to who occupies third place. Earlier comparisons featured a different third name. A rise from roughly 61 percent to 64 percent does not prove a fixed coalition consolidated power. Looking at the top five over several weeks can help separate broad drift toward large operators from a one-month reshuffle. Data sources should state whether they use estimated hash or identified blocks.
There is also a practical governance angle. If a pool announces it will exclude a valid category of transactions, can customers select their own templates or leave quickly? If an endpoint fails, how fast can a fleet reconnect elsewhere? If rewards are withheld, does the miner hold independently saved proof of accepted shares? The dated exit supplies a clear example of why those capabilities matter even when no misconduct is alleged.
Pool Software Is Not Bitcoin Consensus
Some observers treat mining pool concentration as if a handful of operators could rewrite the rules. A valid block must still satisfy the consensus rules enforced by full nodes. A pool coordinating a large fraction of hash power can influence the transactions its participants try to include and the timing of candidate blocks. It cannot force validating nodes to accept an invalid coin issuance merely by winning ordinary block races.
The distinction between pool coordination and machine ownership remains important. Miners leaving the closing pool can choose a new template provider while their equipment and economic interests stay distributed. Concentration still deserves attention when many independently owned machines depend on a small number of coordinators for jobs and payouts. Naming the mechanism precisely helps avoid overstatement.
The mempool holds the pending transactions from which a block producer normally selects. A pool can prioritize higher-fee transactions or apply its own policy to valid candidates. A miner using its own job template may choose differently while still respecting consensus. If former customers flow to large pools that offer working job negotiation, collective payout coordination might become more concentrated even as transaction selection becomes less so.
A real test would survey receiving pools on whether job negotiation is live for ordinary customers, measure actual usage, and check whether a miner can choose its own transaction set without losing the payout model it needs. Protocol support is an engineering milestone. Measured customer use is the market-structure result.
What Operators Should Do Before the Final Share
The closing pool can publish the exact accepted-share cutoff and explain how late work and pending rewards are calculated. The notice already supplies the timestamp. It does not yet give the aggregate amount payable across accounts. A miner reconciling personal earnings can compare local share logs with the pool’s records, note any stale-share adjustments, and save the resulting statement before the November 24 archive cutoff.
A replacement provider’s terms should state whether pending rewards sit in custody, when a payout becomes irrevocable, and what happens if the pool itself stops operating. The distinction matters because FPPS may require the pool to pay miners before its own expected blocks appear. Choosing the lowest quoted fee from a provider that cannot meet those payments trades a known charge for a harder-to-quantify claim on the operator.
The exit can finish without visible disruption to the Bitcoin network while still leaving costly cleanup for individual customers. Final balances, tax histories and cloud-product redemptions are account-level matters. Any later review should examine both the network’s hash distribution and whether the people who supplied that hash received what the old pool owed them. The two outcomes are linked by the exit yet neither automatically proves the other.
Key Dates and Signals Worth Watching
- November 10 at 07:00 UTC – endpoints stop accepting shares and the final eligible-work calculation begins
- November 10 at 23:59 UTC – deadline for any required identity verification that supports final settlement
- November 24 at 07:00 UTC – historical account pages become unavailable
- Sustained changes in attributed hash and block shares for the closing pool and its likely recipients
- Public statements from mining firms about new providers, payout methods or template control
I’ve watched enough pool transitions to know the technical change is usually the easy part. The harder work is matching payout reliability, custody comfort and operational fit to the specific economics of each mine. Some operators will move early and sleep better. Others will wait until the last possible hour and discover a configuration error at the worst moment. The machines themselves do not care. The people who pay the power bills do.
Perhaps the most interesting aspect is how little the network itself will notice. Difficulty keeps adjusting. Blocks keep arriving. The coordination layer simply shifts. Whether that shift spreads influence or concentrates it further depends on the choices thousands of independent operators make between now and the cutoff. Those choices are still open.
In the end the story is less about one company’s product review and more about the practical limits of choice in a market where a handful of endpoints already handle the majority of work. Miners who treat the migration as a chance to re-examine fees, templates, custody and fallback plans will come out stronger. Those who treat it as a simple address swap may discover later that the small print mattered more than they thought.
The November 10 deadline is fixed. Everything after that remains fluid. Watch the hash numbers, watch the payout statements, and watch who actually ends up controlling the templates. That is where the real migration story will be written.
