Binance said on November 4, 2026, that it had replenished approximately 98% of the token assets affected by its October security breach, up from the 95% figure it reported earlier in the recovery. The cryptocurrency exchange also expanded its latest proof-of-reserves snapshot from 10 tokens to 44, but the accompanying zero-knowledge verification was not yet complete at the time of the announcement.
In its seventh official security recovery update, Binance said it had allocated more than the value needed to cover the losses from its own resources. The company attributed the remaining roughly 2% to less-liquid assets that it is seeking to acquire through market purchases and over-the-counter transactions.
Exchange reports progress on replacing affected assets
The new figure is an update to the exchange’s recovery plan, not an independent determination that every affected token or customer withdrawal has returned to normal. Binance said acquiring the final tokens could take longer because low liquidity may limit how quickly replacement purchases can be executed.
Its earlier update described approximately 95% replenishment as withdrawal services reopened in phases. BlockBriefing previously covered the planned phased restart across 15 networks and subsequent changes to withdrawal availability. The latest statement provides a higher replenishment estimate, while continuing to acknowledge outstanding restoration work.
The exchange said the necessary funds were set aside from its own resources rather than being charged to customers. Those statements describe Binance’s funding commitment and current internal accounting; they should not be interpreted as an independently audited guarantee of every liability or a finding that the underlying security weaknesses have been fully resolved.
Proof-of-reserves snapshot now includes 44 tokens
Binance reported taking the new snapshot at 00:00 UTC on November 4, expanding coverage from the 10 tokens in the preceding snapshot. A snapshot records balances at a specified point in time, so it does not necessarily describe how assets move or how withdrawals are processed before and after that timestamp.
Crucially, Binance estimated that producing the complete zero-knowledge proof would require another 50 to 60 hours because of the computational workload. Consequently, its announcement of an expanded snapshot did not mean the corresponding cryptographic verification had already finished. Users should check the exchange’s proof-of-reserves portal for the subsequently available proofs and verification instructions.
Proof-of-reserves checks may demonstrate whether specified customer balances are represented in a published balance dataset and whether declared assets meet that dataset’s stated backing threshold. Their scope still matters: a snapshot does not by itself establish operational security, prove the absence of every undisclosed liability or substitute for a comprehensive financial audit.
Withdrawal recovery and security questions remain
Binance said it would continue buying the remaining affected assets, reopening withdrawals in stages and strengthening safeguards. The announcement did not provide a firm date for complete restoration across every token and network.
Customers tracking the incident should distinguish the percentage of replacement assets from actual withdrawal functionality. Restored backing for an asset does not automatically mean its blockchain deposit and withdrawal routes are available to every user.
BlockBriefing has separately reported the earlier 10-token reserve-verification milestone. The next material developments will be completion of the expanded zero-knowledge proof, updated asset replacement figures and verified progress in restoring restricted services.
At present, the 98% figure and expanded coverage are claims made in Binance’s own November 4 update. The unfinished verification and remaining withdrawal restrictions warrant continued scrutiny rather than a conclusion that the incident is fully closed.
