What Binance confirmed on 14 November
Binance says withdrawals reopened during the week for 87 networks, including major routes such as Cardano, Avalanche, Cosmos, Litecoin, Near, Starknet, ZKsync Era and several Ethereum-compatible networks. The list refers to networks, not a guarantee that every token on each network is immediately available.
The exchange says it aims to restore all remaining networks and assets by the end of next week. That is a target, not a completed milestone. Binance warns that heavy traffic may cause temporary delays and tells users to verify their chosen asset-network pair on its status page.
How this changes the breach recovery picture
The 14 November notice is a meaningful operational step after the 29 October incident. Binance previously said it committed more than $6.34bn from SAFU, excess futures-insurance resources and its corporate treasury to cover affected assets, and published a 198-token reserve snapshot dated 12 November.
Those are different questions: asset coverage addresses the economic hole; proof of reserves addresses a point-in-time backing claim; reopening withdrawals addresses whether users can move funds. Progress in one does not automatically complete the others.
Practical implications
- Check the exact token and network inside the official Binance app immediately before submitting a withdrawal.
- Do not assume a restored network means every wrapped or bridged version is available.
- Use a small test transfer when practical, and verify the receiving network and memo requirements.
- If a route fails, do not trust a support account that asks for a seed phrase, private key or “safe address.”
- Keep transaction records while services are still being restored.
What remains unknown
Binance has not published a final independent technical audit of the breach. Its preliminary account describes compromised credentials and a malicious workload, but the full privilege chain and every failed control remain open. The exchange also has not declared the entire withdrawal restoration complete.
Its reserve snapshot remains a point-in-time exercise. It does not by itself audit all corporate liabilities, related-party exposures or movements between snapshots.
What to watch next
- A notice that all remaining asset-network routes have reopened.
- Evidence that the promised zero-knowledge proof is available for the 12 November snapshot.
- Confirmation that SAFU has returned to approximately $1bn.
- A final post-incident report and independent security review.
Sources you can open
01This version adds Binance’s 87-network withdrawal restoration list and its target for remaining routes. Claims from Binance remain attributed; no final independent incident audit has been published.