Binance Reopens Withdrawals, Starting With Bitcoin

Binance said at 06:20 UTC on 1 November that the Bitcoin network had opened for withdrawals, the first route back after crypto withdrawals were frozen during the 29 October attack.

https://x.com/binance/status/2116777408074600621 > Update: First batch network now opened in phase one of withdrawals is $BTC bitcoin network > > — Binance (@binance), 1 Nov 2026

Bitcoin came back first. Ether, USDT and USDC on Ethereum, and BNB, USDT and USDC on BNB Smart Chain, followed at 07:49 UTC.

https://x.com/binance/status/2116799757507305516 > Withdrawal Update > > Withdrawals have now been restored for the following assets and networks: > > - Ethereum Network: USDC, USDT, ETH > - BNB Smart Chain (BSC): USDC, USDT, BNB > > We will continue to restore additional assets and networks in phases following the completion of our security checks. Further updates will be shared through official Binance channels. > > — Binance (@binance), 1 Nov 2026

Three doors out of fifteen

Phase one names fifteen networks, ranked by what customers withdrew most in the week before the attack.

By 08:20 UTC, three had withdrawals switched on: Bitcoin, Ethereum and BNB Smart Chain.

The other twelve, from Tron and Solana to Sui, were still closed.

Deposits were paused with withdrawals at the start. Binance's notices at 00:13 and 01:36 UTC on 30 October said "all deposits and withdrawals are temporarily suspended". By 04:36 UTC it said deposits "remain unaffected and continue to operate as normal", and it has repeated that in every update since. Its support desk told users that peer-to-peer trades and fiat withdrawals "remain available where supported", which depends on the local payment rails.

Binance blames traffic, not account caps

Binance attributes the delays to traffic rather than to limits on accounts. It warned that users "may experience temporary delays or longer processing times due to traffic volume", and that a withdrawal which fails can be retried shortly. Its support desk went further, telling one user a delay was "most likely due to temporary congestion from high traffic volume rather than any issue with your account or a service block". No per-user cap has been announced. There is no way yet to check the explanation from outside, and opening three of fifteen networks at once is itself a way of holding demand back, so read "traffic" as Binance's account rather than a measured one.

What paid for the reopen

Binance says it has replaced 95% of the stolen amount with its own money, from 90% on 31 October. The figure is the exchange's own, published in its fourth recovery update. Reuters reported the same number.

Binance's own coverage of the hack loss, 80% to 95%

Covered share of the ~$6.3B Binance says was taken, as the exchange reported it in Updates #2, #3 and #4. Grey is the part it says is still outstanding. Binance's estimates, not audited totals. Data as of 04:11 UTC, 1 Nov 2026. Source: Binance.

Ten assets are described as fully backed, from BTC and ETH down to ZEC, meaning Binance says every customer coin in those is there. The other tokens are the part still being bought.

Covered is not the same as recovered. Binance bought replacement tokens so that balances were whole again; it has not taken the money back from the attacker. About $3 billion is frozen on-chain, Binance says, and recovering that is a separate process.

The money came from three places, per Binance:

The SAFU share became visible on-chain. At 14:51 UTC on 31 October, 7,499 BTC left the fund's published address in a single transfer. The address held about 15,000 BTC before the draw, so the split is visible on-chain.

Whale Alert, which tracks large transactions, put the value at about $581 million at the time. Binance confirmed at 16:15 UTC that the transfer was complete.

Yi He said half the coins at that address were spent and half kept. Roughly 7,500 BTC still sits there as of 08:20 UTC.

Binance has promised to refill SAFU to about $1 billion. That is a target, not a completed transfer.

What is still limited

The last 5% is the slow part. Binance says the remainder is tokens outside the top ten, too illiquid to buy quickly "at the required scale", so it is still working through market and over-the-counter purchases.

The withdrawal list is unfinished too. Every network past the first few is waiting on security checks, and Binance has not said when the next phase opens or what it will contain.

Proof of reserves is the third open item. Binance took a fresh snapshot at 00:00 UTC on 31 October and posted it. The full zero-knowledge proof, the part that lets a customer check their own balance is counted, is expected by 3 November. Until then the coverage figures rest on Binance's word.

The exchange now processes all withdrawals from newly generated wallets, and has listed those addresses on its reserves page.

Separately, Binance Pool is still due to close on 10 November, a decision announced in October that Binance has not tied to this incident.

The chronology of the theft, from the first transfers to the FBI's attribution, is in our timeline of the Binance hack.