News Wallets and security Markets and data

Binance expands withdrawals, reports 98% asset replenishment

Binance announced another stage of withdrawal reopening on 5 November 2026 following the security incident on 29 October. A day earlier, the exchange said it had replenished approximately 98% of the affected amount and expanded its proof-of-reserves snapshot to 44 tokens. Access remains gradual: a token appearing on a reopening list does not mean it can immediately be withdrawn on every network.

Checked on 5 November 2026.

Partly open navy vault with orange coin discs passing through a small checkpoint
Illustration: staged withdrawal access, operational checks and asset backing.

The latest rollout was scheduled to begin at 04:00 UTC on 5 November, or 06:00 in Israel. That is the announced starting point, rather than confirmation that every listed asset-network pair is operational. The announcement concerns an international platform. It does not establish an Israeli compensation scheme or special rights for customers in Israel.

Which withdrawals are reopening

The Binance withdrawal announcement (Opens in a new tab) includes UNI, AAVE and PAXG on Ethereum; AERO, VIRTUAL and MORPHO on Base; and selected assets on BSC, TRON, Polygon and Sui. Each asset-network combination is subject to security and readiness checks. Deposit services remain open, according to the company.

The list alone cannot establish availability for a particular transaction. The same token can be enabled on one network while remaining suspended on another. Binance directs customers to its withdrawal screen and network-status page and says heavy traffic may cause delays. A request being accepted by the exchange also differs from a transaction being broadcast and confirmed on a blockchain.

This extends the reopening that began on 1 November and broadened on 3 November. Our coverage of the Binance hot-wallet hack explains the original incident. The present update concerns access and asset backing; it does not establish that the investigation is finished or every security risk has been removed.

Funding a replacement is different from obtaining the token

On 4 November, Binance said it had allocated more than the funds required to cover the losses from its own resources and had replenished approximately 98% of the affected amount. It was still acquiring the remainder through market and over-the-counter purchases, describing those tokens as less liquid and harder to obtain at the required scale.

Two steps are involved: setting aside money and acquiring the particular asset in which a customer's balance is denominated. A commitment to finance the loss does not by itself show that every token is already in a wallet ready for withdrawal. Completing a purchase also does not replace the security checks needed to reopen that withdrawal route.

The company was still reporting approximately 95% replenishment on 2 November. That figure has therefore been superseded in its latest progress announcement reviewed here. Both percentages are Binance's account of its recovery work, rather than findings from an independent financial audit conducted by this publication.

What the reserves evidence can establish

The newer snapshot was taken at 00:00 UTC on 4 November and covers 44 tokens, up from 10. Binance estimated that the complete zero-knowledge proof would take 50 to 60 hours to generate. An estimated processing time is not a completion announcement: publishing a snapshot and delivering its fully verifiable proof are separate stages.

Binance said on 2 November that the proof for the 31 October snapshot had been completed. Its coverage included BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC. The mechanism is intended to let customers check that their own balances are included without disclosing other customers' account balances to them.

Proof of reserves compares assets and customer balances within a defined scope at a particular moment. It does not necessarily establish all corporate liabilities, the quality of internal controls or resilience under every future scenario. The investor advocate's office at US audit watchdog PCAOB has previously explained that such reports are not equivalent to financial-statement audits.

Net outflows need a time window

The Block reported on 2 November, citing DeFiLlama, approximately $3.29 billion in net outflows over a 24-hour window. That should not be relabelled as the amount withdrawn on the first day of reopening. A rolling window changes continuously, so figures from different reporting dates cannot automatically be combined.

Net outflows measure outgoing funds minus incoming funds under the provider's methodology. They are not necessarily a loss, and they do not explain customers' motives. Internal transfers and changes in wallet attribution also matter when interpreting blockchain data. Comparisons require a common time basis and a consistent definition of which addresses belong to the exchange.

What users in Israel can check and record

Customers can reach announcements through an app or website they open independently, preserve their transaction history and record the asset, network, time and transaction identifier where one exists. A destination address should be checked with the recipient. An address published as a company reserve wallet is not a customer's personal deposit address.

A payment supposedly needed to accelerate a withdrawal, an unsolicited compensation link or a request for recovery words is not part of verifying reserves. The warning signs in suspicious crypto messages are particularly relevant while people wait for services to return. For a specific transaction, the useful information is the current status of that asset and network in the account, together with the applicable service terms and the records retained.

Correction and clarification

Found an error? Contact the editors

Share article Back to top