Binance says it has replaced the customer assets lost in its security incident and reopened withdrawals on 87 networks this week. The exchange aims to restore the remaining networks and assets by the end of next week, leaving some customers waiting despite its completed-coverage announcement.
The announcement, signed Nov. 13, accompanies a reserve snapshot covering 198 tokens. For customers, the next question is whether covered balances can be verified and moved off the exchange.
In its Nov. 4 update, Binance put replenishment at approximately 98%, with purchases of less-liquid tokens still continuing. The latest notice says that replacement process is complete.
Related Company Binance Global crypto exchange
CryptoSlate's earlier coverage of the sourcing delays described the difficulty of acquiring thinly traded tokens alongside progressive withdrawal reopening. The new announcement changes that reported coverage position while retaining the phased withdrawal rollout.
Binances wider snapshot, a separate verification step
Binance says the new snapshot was taken at 00:00 UTC on Nov. 12 and spans 198 tokens, compared with 44 in the Nov. 4 snapshot. The earlier snapshot was taken at 08:00 UTC+8, equivalent to 00:00 UTC.
The expanded snapshot covers more tokens, but does not establish whether each asset and network is available for withdrawal.
The latest notice says the snapshot is available on its proof-of-reserves website. It separately estimates approximately 40 to 50 hours to generate the full zero-knowledge proof, after which affected holders would be able to verify minimum one-for-one backing.
A published snapshot and an available verification result therefore describe different stages. The announcement does not confirm that proof generation is complete. The notice gives no starting point for the estimate, leaving current proof availability unestablished here.
The earlier 44-token round carried a different estimate of 50 to 60 hours. Both notices separate taking a snapshot from producing its full proof. For affected holders, verification would address backing at the specified snapshot, while access to funds remains an operational question.
Covered assets still need a route out
Binance reports coverage complete. Verifying dated backing and withdrawing balances remain separate customer tests.
Binance's coverage assurance branches into two separate customer checks: reserve verification and withdrawal access. Connectors show questions, not transfers of funds.BINANCE SAYS · NOV. 13Affected assets are covered
Verify dated backingProof availability unverifiedWithdraw balancesStill reopening in phases
- Each customer outcome needs its own evidence.
One company coverage assurance leads to separate backing and withdrawal checks.BINANCE SAYS · NOV. 13Affected assetsare covered
Verify dated backingProof availabilityunverifiedWithdraw balancesStill reopening in phasesEach needs its own evidence.
How the reserve snapshot widenedHow the reserve snapshot widenedNov. 4 snapshotNov. 12 snapshot
Binance reported 44 tokens in this earlier snapshot.
44tokens in the snapshotNov. 4, 2026, 00:00 UTCOne dot = one token.
44tokensNov. 4, 2026, 00:00 UTCOne dot = one token in the snapshot.
Binance reports 198 tokens in the newer snapshot.
198tokens in the snapshotNov. 12, 2026, 00:00 UTCOne dot = one token.
198tokensNov. 12, 2026, 00:00 UTCOne dot = one token in the snapshot.
The wider reserve snapshot addresses more tokens; access still depends on withdrawal availability.
Binance's statements are attributed assurances. Current full-proof availability and individual withdrawal routes are unverified. Dots count tokens at snapshot times, not reserve value or withdrawal routes.
Sources and evidence
Sources
- Binance completion announcement, signed Nov. 13
- Binance recovery update, Nov. 4
- Reported statement Binance says it has completed coverage of assets affected by the security incident, in an announcement signed November 13, 2026. [1]
- Reported statement Binance says its November 12, 2026, 00:00 UTC reserve snapshot covers 198 tokens and is available on its PoR website; the same announcement makes users' minimum 1:1 verification conditional on generation of the full zero-knowledge proof, estimated at approximately 40 to 50 hours. [1]
- Reported statement Binance's November 4 update said its snapshot at November 4 00:00 UTC covered 44 tokens, compared with ten previously, and estimated 50 to 60 hours for that round's complete proof. [2]
- Reported statement Binance says withdrawals continue reopening in phases and promises further confirmed updates; the completion notice does not announce universal withdrawal restoration. [1]
Supporting facts
Method
Source-bound comparison of Binance's two notices. Each dot represents one token in the stated reserve snapshot; dots encode token counts only, not balances, value or withdrawal routes. Branch connectors separate customer checks and do not depict a movement of funds.
Scope
Binance's statements are attributed assurances. Current full-proof availability and individual withdrawal routes are unverified. Dots count tokens at snapshot times, not reserve value or withdrawal routes.
Infographic by CryptoSlate
In its Nov. 14 recovery update, Binance said withdrawals had reopened on 87 networks this week. It aims to reopen all remaining networks and assets by the end of next week, while warning that rollout traffic could cause delays or longer processing times.
Customers moving covered balances off Binance still need to check the withdrawal page for their chosen asset and network. The reopening announcement is not a guarantee that every route is available or every transfer will process immediately.
A small number of affected tokens that Binance no longer supports will be covered through its delisting process. The notice does not specify how or when those holders will be compensated.
SAFU restoration remains a commitment
Binance says it committed more than $6 billion in company funds, drawing on corporate treasury, partial deployment of its Secure Asset Fund for Users and a portion of Futures insurance resources above its stated risk-management requirement.
It separately commits to returning SAFU to approximately $1 billion. The announcement does not report that restoration as complete.
Replacing affected customer assets and restoring an emergency reserve serve different purposes. The first addresses losses from this incident; the second concerns the resources available for future emergencies. The announcement provides no allocation breakdown among the three funding sources, and the fund-restoration pledge remains distinct from its completed-coverage assurance.
Binance's announcement changes the reported coverage position. The next practical milestones for customers are accessible verification for their covered assets, confirmed withdrawal availability and delivery of the remaining fund-restoration commitment.