Binance Pool mined just one Bitcoin block over a seven-day window, according to figures reported by CoinDesk and openPR.com, while the network as a whole produced about 925 blocks. That puts the pool at roughly 0.11% of network blocks, days before Binance switches the service off on November 10, 2026 at 07:00 UTC.

The timing matters for anyone who points hardware, scripts or dashboards at the pool. Binance has featured in our crypto coverage this autumn, including our look at the metrics behind Binance’s $6.34B hack, but this story is different. The Binance Pool shutdown is a planned wind-down with a published cutoff, and the interesting questions are practical ones for software engineers, miners and tool maintainers.

This analysis sticks to what the reports confirm. The Information, CoinDesk and openPR.com have all covered the story, and the verified details are short: one block, zero blocks in the latest 24 hours, a last block at 01:15 UTC on November 6, and a hard discontinuation time. Everything beyond that is labeled as analysis, arithmetic or an expectation, not as reported fact.

Don't miss new tech stories on Google

Add Shattered once in the Google app and our stories show up in your news suggestions.

Binance Pool Shutdown: The Numbers That Matter

Reports from CoinDesk and openPR.com give a tight set of figures. Binance Pool produced 1 Bitcoin block during the seven-day observation period. Across the network, miners found approximately 925 blocks in the same stretch. One block out of 925 works out to about 0.11% of network blocks, which is the share the reports cite.

The most recent 24-hour period reported was even quieter, with 0 blocks credited to the pool. Its latest reported block was Bitcoin block 974,743, mined at 01:15 UTC on November 6, 2026. That block contained 1,353 transactions and paid approximately 3.134 BTC in total rewards, fees included.

Treat the table as a snapshot, not a trend line. Seven days is a short window for a metric that depends on random block discovery, and the reports do not publish a longer history for comparison. What the numbers do establish is that, going into the final stretch, the pool’s visible output on the Bitcoin chain was close to nothing.

Timeline From April 2020 to the Nov. 10 Cutoff

Binance Pool launched in April 2020, according to the reports. That gives the service a run of more than six years inside the exchange’s product lineup, alongside the other mining-adjacent services that Binance is now retiring together. The sequence of events that matters for the shutdown looks like this.

  • April 2020: Binance Pool launches, per the reports.
  • October 2026: Binance announces it will discontinue Binance Pool and related services.
  • November 6, 2026, 01:15 UTC: the latest reported pool block, number 974,743, lands on the Bitcoin chain.
  • November 9, 2026: this report, with the pool at zero blocks over the latest 24-hour period reported and one block across seven days.
  • November 10, 2026, 07:00 UTC: scheduled discontinuation of Binance Pool, Pool Savings, Cloud Mining and Transaction Accelerator.

The gap between the last block on November 6 and the cutoff is short. If you run anything that depends on the pool, that window is the entire runway left. Waiting for a final reminder email is a bad plan when the schedule is already public.

What Block 974,743 Tells Us

Block 974,743 is the last confirmed proof of life in the reports. It carried 1,353 transactions and paid about 3.134 BTC in rewards including fees. The reports do not break that figure into subsidy and fees, so this article does not either. What the number shows is that a single block is still a large payout event, which is exactly why block counts swing so hard for small pools.

For developers, the block is also a useful test fixture. If you maintain a block explorer integration, a pool-attribution parser or a coinbase-tag decoder, block 974,743 is a documented example of a block credited to a pool that is about to disappear. Pin it in your test data now. After November 10, the label on that block becomes a historical fact, not a live service, and parsers that assume active pools can behave oddly when an old tag stops appearing in recent blocks.

The timestamp matters too. A block at 01:15 UTC on November 6 followed by nothing in the latest 24-hour period reported means the pool’s last visible activity came a few days before the cutoff. Whether that reflects wind-down behavior, miners leaving early or plain variance is something the reports do not say. Anyone claiming to know the cause is guessing.

Why One Block Does Not Prove a Hashrate

It is tempting to read “one block in a week” as “almost no hashrate left.” The reports caution against that reading, and so does the math. Bitcoin blocks arrive as a random process, so a pool with a given share of total hashpower finds a variable number of blocks each week. The count fluctuates around an expected value, and a single week cannot pin down the underlying share.

The table below is our own arithmetic, not reported data. It assumes the network produced 925 blocks and asks how likely a pool would be to find one block or fewer for several hypothetical shares of network hashpower. These shares are illustrations, not estimates of Binance’s actual hashrate.

The pattern is clear. A pool holding a 1% share would almost never produce so few blocks, while a pool holding a share near 0.1% to 0.2% would do it routinely. So the result leans toward a share well below 1% during that week. It does not tell us whether the true figure is 0.05%, 0.2% or 0.4%, and the reports do not claim to know.

The 24-Hour Zero Is Even Less Informative

Zero blocks in the latest 24 hours sounds dramatic, but the network finds roughly 132 blocks a day on the reported weekly figure (925 divided by seven). A pool holding one block in 925 would expect about 0.14 blocks a day. The chance of seeing zero is then around 87%. In other words, the 24-hour zero is what a pool at the observed share would show most days. Read it as consistent with a small pool, not as proof of a collapse.

Run the Numbers Yourself

You can reproduce the table with a few lines of Python. The function uses the Poisson approximation, which fits rare, independent events like block discoveries well enough for this kind of sanity check.

Which Binance Services Go Dark

The shutdown covers more than the pool itself. The reports list four discontinued services: Binance Pool, Pool Savings, Cloud Mining and Transaction Accelerator. Each one serves a different kind of user, and each carries a different kind of migration work.

Binance Pool is the mining pool proper, where hardware owners point their machines and receive payouts. Pool Savings and Cloud Mining are consumer-facing products tied to the pool business. Transaction Accelerator is a service for users who want a stuck Bitcoin transaction confirmed faster. The reports give the date and the product names but, in the material we reviewed, no detail on settlement mechanics for open balances. Check Binance’s own notices for that, because this article cannot confirm it.

The bundling is itself informative. Binance did not pull one feature and leave the rest. It retired the whole cluster of mining-related products at the same moment, which fits the language of its own announcement about reviewing products and services.

What Binance Said in October

Binance announced the closure in October. The company’s statement read: “As part of our ongoing review of products and services, Binance will discontinue Binance Pool and related services on 2026-11-10.” That is the full wording we have verified, and it is notably brief. It gives a rationale in general terms, a product name and a date.

What the statement does not do is explain the strategy. It does not say mining margins drove the call, it does not mention hashrate, and the reports we reviewed do not cite any Binance executive offering a reason beyond that sentence. Any narrative about regulatory pressure, profitability or a pivot is speculation until Binance says otherwise.

Also note the precision of the schedule. The discontinuation is set for 07:00 UTC on November 10, 2026, not “sometime on November 10.” If your automation runs on local time, convert the cutoff before you plan a maintenance window.

What Miners and Developers Should Change Before the Cutoff

For a hobbyist with a few machines, moving off a closing pool is a config edit. For a developer maintaining firmware images, dashboards, fleet tooling or open-source miner presets, it is a small audit across several codebases. The risk is not dramatic. It is the quiet kind, where a hard-coded endpoint keeps sending work into a pool that no longer pays.

Configuration and Firmware

Start with anything that stores a pool connection string. Miner configuration files, container environment variables, infrastructure-as-code templates and provisioning scripts are the usual hiding places. Most mining software speaks the Stratum protocol to a pool, so the fix is normally to change the Stratum URL, the worker name and the payout identity, then confirm shares are accepted at the new destination before you remove the old one.

Teams that ship self-hosted infrastructure already know this drill from other deprecations. Our write-up on BTCPay Server hot-wallet thefts on 2.4.1 and older installs makes the same point from a different angle, which is that old defaults linger in running systems long after the upstream world has moved on.

Monitoring and Accounting Scripts

Next, check anything that reads from the pool. Profitability trackers, payout reconcilers, alert rules and tax-lot exporters often poll a pool’s API or parse its statements. After the cutoff those calls will fail or return stale data. Decide now whether your alerting should page someone or whether you should retire the checks cleanly, and export your payout history while the service still exists.

Lightning and node operators have their own version of this housekeeping. Our guide to hardening LND against the MPTCP kernel bug walks through the habit of auditing what a service actually depends on before a change lands, and the same habit applies here.

Find Hard-Coded Pool Settings in Your Repos

A grep finds most references, but a small script gives you file names and line numbers you can paste into a ticket. The script below walks a directory of config and deployment files and prints every line that mentions Binance. It does not assume any particular hostname, so it catches nicknames, comments and old presets too.

Run it against your miner configs, your fleet repository and your dashboard code. Review each hit by hand. A match inside a comment or a changelog needs no action, while a match inside a live pool URL or a payout setting needs a replacement before 07:00 UTC on November 10.

Add a test or a CI check that fails when a retired pool name shows up in production config. That turns a one-time cleanup into a guard that catches the next deprecation too. Teams that automate this tend to find stale references long before anyone notices a drop in accepted shares.

Transaction Accelerator Users: Other Ways to Bump a Stuck Payment

Transaction Accelerator is on the discontinuation list, so anyone who relied on it for slow confirmations needs another route. The reports do not describe how the service worked internally, and this article will not guess. What we can say in general terms is that wallet-level fee bumping remains the standard option.

Two common techniques are replace-by-fee, where the sender rebroadcasts a transaction with a higher fee, and child-pays-for-parent, where a recipient or sender spends an unconfirmed output with a high-fee follow-up transaction. Whether either works depends on how the original transaction was built and which wallet created it. Developers who build payment flows should check that their software exposes at least one of these paths, because a dependency on a single third-party accelerator is now a documented single point of failure.

Merchants and apps that told customers to “use the accelerator” in help-center text should update those pages before the cutoff. Stale instructions create support tickets, and support tickets are the most expensive way to discover a deprecation.

Cloud Mining and Pool Savings: A Counterparty Lesson

Cloud Mining and Pool Savings sit in a different risk bucket from the pool. They are exchange-hosted products, which means the user depends on the platform for custody, accounting and continuity. When the platform retires them, the customer’s options narrow to whatever the platform’s closure terms allow.

That is a useful reminder in a year when counterparty risk has been in the news. Our report on insurers scrutinizing crypto firms after the $6.3B Binance hack shows how closely outside parties now examine the platforms that hold user assets. The two stories are unrelated in cause. Binance has described this closure as a product review, and nothing in the reports links it to the hack. They do share a theme, though: keeping funds and workloads on one platform concentrates risk.

For engineers, the takeaway is architectural. If your business logic depends on a hosted product, document the exit path before you need it. Know how to export balances, how to point workloads elsewhere and how long each step takes. The Binance Pool shutdown is a clean example because the date is public and the services are named.

Market Impact: Bitcoin Price and Network Security

Expect little direct effect on Bitcoin itself. The pool produced about 0.11% of network blocks in the observed week, so its departure removes a sliver of block production, and the difficulty mechanism adjusts to total hashpower regardless of which pool the miners use. Hashrate that currently reports to Binance Pool does not vanish when the pool closes. The machines can reconnect elsewhere.

Prices are driven by other forces right now. Our coverage of Bitcoin at $73,708 and Ether at $2,223 after the midterms shows a market reacting to politics and macro news, not to the closure of a small exchange-run pool. Nothing in the reports suggests the shutdown moved prices.

The more interesting effect is structural. Exchange-run pools were one way large platforms participated in mining. Binance leaving that business, at least under this brand, trims one corporate presence from block production. Whether that helps or hurts decentralization depends on where the machines go, and the reports offer no data on that. We would not draw conclusions until chain data shows which pools gain share after November 10.

For the software side, the practical market effect is churn. Open-source miner presets, dashboard templates and tutorial repositories that list Binance Pool will go stale. Maintainers who prune them early will save their users a bad weekend.

Where the Hashrate Goes Next: How to Compare Replacement Pools

The reports do not name which pools will absorb Binance Pool’s remaining miners, and we will not invent a market-share table. What we can offer is a checklist for evaluating any replacement. These criteria apply to any pool and rely on facts you can verify on the pool’s own documentation.

Pick a destination that pays directly to a wallet you control where possible. The pool you leave is closing partly because a platform decided to review its product lineup. A pool that never holds your balance cannot surprise you in the same way.

If you manage a fleet, run the new pool in parallel with the old one for a short test period on a subset of machines. Compare accepted share rates, rejected share rates and payout timing before moving everything. Our checklist-style piece on six coding-tool checks after the Binance hack warning covers a similar discipline for verifying tools before trusting them, and the pool switch deserves the same care. For more engineering-focused coverage, see our software section.

Five Predictions for the Week After the Shutdown

These are our expectations, built from the reported facts and ordinary patterns in how services close. They are analysis, not reported events, and any of them could miss.

  1. Public pool trackers will show zero Binance Pool blocks after the cutoff. With discontinuation scheduled for 07:00 UTC on November 10, new blocks attributed to the pool should stop. A stray late block credited to the tag would surprise us.
  2. Support questions about final balances will spike. Closures of hosted products usually produce confusion about settlement timing. Users should rely on Binance’s own notices, not forum guesses.
  3. Open-source projects will remove Binance Pool presets. Expect pull requests that delete the pool from default lists, dashboards and tutorials within weeks.
  4. Bitcoin difficulty will not register the closure. A pool near 0.11% of blocks is too small, and its miners are free to reconnect elsewhere, so network-level effects should be invisible.
  5. Other exchange-run crypto services will face fresh scrutiny. When one platform trims a product line, observers ask who is next. That is a question, not a forecast of specific closures, and no report names another service at risk.

The common thread is that the technical consequences are small and the operational consequences are scattered. A closure like this rarely moves a market, but it can break a surprising number of scripts.

FAQ: Binance Pool Shutdown

When does Binance Pool shut down? Binance announced it will discontinue Binance Pool and related services on November 10, 2026 at 07:00 UTC, according to reports from CoinDesk and openPR.com.

How many blocks did Binance Pool find recently? It found 1 Bitcoin block during the seven-day observation period, out of approximately 925 blocks across the network, or about 0.11%. It found 0 blocks in the latest 24-hour period reported.

What was the last block Binance Pool mined? The latest reported block was Bitcoin block 974,743, mined at 01:15 UTC on November 6, 2026. It held 1,353 transactions and paid about 3.134 BTC in total rewards, including fees.

Which services are being discontinued? The reports name Binance Pool, Pool Savings, Cloud Mining and Transaction Accelerator.

Does one block in a week prove the pool lost its hashrate? No. Block discovery is random, and the reported data do not establish an exact hashrate. The arithmetic above shows that a pool with a small share would often find one block or fewer in a week.

What should developers do before the cutoff? Search configs, firmware images, dashboards and scripts for references to the pool, switch miners to a replacement Stratum endpoint, export payout history, and update any help text that points users to Transaction Accelerator. Confirm settlement details for open balances in Binance’s own notices.

Will the shutdown affect the Bitcoin network? Direct effects look minimal. The pool produced about 0.11% of blocks in the observed week, and miners can reconnect to other pools, so network-level impact should be small.

Dr. Heinrich Vogel reviews shattered.io technical coverage for accuracy, checking explanations against primary specifications and published research before they go live. His background is in cryptography and security engineering.