Hashrate Index put the pool at about 26 exahashes per second at the end of 2025 and CoinDesk's data put it at about 9.2 in October, a fall of about 65%. Binance has published no figure of its own and gave no reason beyond a review of its products.
Binance Pool found one Bitcoin block in the week to Monday morning and none in the preceding 24 hours, according to mempool.space data reported by CoinDesk. That was one of roughly 925 blocks mined across the network over the period, about 0.11% of the total. Binance switches the pool off at 07:00 UTC on Tuesday, November 10, the cutoff it set out in a notice published on October 13.
That notice carried no hashrate figure, and the trackers that publish estimates could not be opened at source at the time. Two readings are now on the record, from different providers and different months. Hashrate Index, cited by Decrypt, put Binance Pool at about 26 exahashes per second at the end of 2025, roughly 2.3% of the Bitcoin network and ninth among pools by size. CoinDesk's own data put the pool at about 9.2 exahashes per second in October 2026. Those two inputs give a decline of about 65% across roughly ten months, the figure CoinDesk reports. The pool opened in April 2020.
A single week of block discovery is a weak measure of what remains. CoinDesk makes that point itself: block finding fluctuates randomly, so a seven-day count cannot establish how much hashrate is still connected to a pool. The pool's most recent block was height 974,743, mined at 01:15 UTC on November 6 with 1,353 transactions and about 3.134 BTC in rewards including fees, on the same mempool.space data. More than three days had passed without another by the time CoinDesk published early on Monday.
Shares and hashrate submitted after 07:00 UTC on Tuesday are not accepted, processed or credited, The Block reported when the notice appeared, and the Stratum endpoints, the pool API, and the email and Telegram alerts that tell an operator a machine has stopped hashing go with it. Pool Savings, Cloud Mining and the Bitcoin Transaction Accelerator close at the same moment. Decrypt reported that accounts owed money must finish identity verification by 23:59 UTC that day, and that the pool's pages stay readable until 07:00 UTC on November 24.
None of that takes computing power out of Bitcoin. A pool is where shares are counted and rewards are split, so a closure relocates the accounting and leaves the machines to be repointed somewhere else. CoinDesk named Foundry USA, AntPool and F2Pool as pools that already find a substantial share of blocks and could absorb what leaves Binance. No published data yet shows any of them doing so. For scale, MiningPool reported in October that network hashrate had climbed back above one zettahash as difficulty rose 5.9%. A zettahash is a thousand exahashes per second.
Binance has published nothing about the pool beyond the decision itself. Its notice cited an ongoing review of its products and services. The company has given no hashrate estimate of its own, no revenue or cost figure, and no account of why a service running for more than six years is being retired now. Both numbers in circulation are third-party estimates, and neither provider has published a November reading.
Decrypt cited Hashrate Index's description of Binance Pool as the last survivor of the period when exchanges moved into mining alongside their trading businesses. Other operators have been trimming mining-adjacent lines for different reasons. MiningPool reported on Saturday that IREN will still be mining bitcoin in 2027 despite a December target for leaving self-mining, and IREN is redirecting power toward AI tenants rather than withdrawing from the business. Binance is closing a service line whose earnings it never disclosed and keeping the exchange around it.
For anyone still connected, the deadlines are the practical part. Hashrate has to move before 07:00 UTC on Tuesday, Pool Savings positions have to be cleared by the same moment, identity verification has to be finished by 23:59 UTC that day where a balance is outstanding, and records have to be exported before November 24. How much hashrate actually moves is not something Binance will publish. It will only be visible as a change in the block share of whichever pools receive it.
