A restart announcement, not an all-clear

Binance announced on 1 November 2026 that it was preparing a phased restart of withdrawals after a security incident on 30 October. Its fourth recovery update scheduled an initial window that day and listed supported asset-and-network combinations. Reporting on 2 November, CryptoGov has verified the announcement, not the successful completion of every customer withdrawal.

ADGM’s FSRA separately acknowledged the incident in a statement dated 30 October, referring to unauthorised asset withdrawals and confirming engagement with Binance. The regulator’s statement supplies independent confirmation of the incident and supervisory attention. It does not certify the company’s recovery figures or declare the investigation complete.

What remains a company statement

Binance says it is replenishing affected assets and will absorb the financial impact rather than pass it to users. Those assurances are attributed to the company. CryptoGov has not independently reconciled customer liabilities, reserve holdings and recovery transactions, and does not present the company’s statements as an independent audit.

The published rollout differentiates network-and-asset pairs instead of promising simultaneous access to every balance. It also warns of possible processing delays. For readers following the event, the distinction matters: an announcement about restarting a service is evidence of a recovery plan, while actual availability is a separate operational fact that can change.

The investigation is still consequential

The company says it plans a post-incident report after the investigation. That report, any additional regulator statement and verifiable changes in service availability would constitute material follow-ups. Repeating the same restart announcement under several headlines would not add a new event to the record.

CryptoGov’s interpretation is that the recovery story has at least three distinct tests: restoring access, accounting for assets and explaining the failure. Progress on one does not establish completion of the others. This distinction avoids converting an operational milestone into a claim about the cause of the incident or the safety of every remaining system.

The confirmed news is therefore bounded: the incident has been acknowledged by the regulator, and Binance has published a phased restart plan. Customers should consult the current official network-status information for a particular route rather than assume this dated report guarantees availability. No alleged attacker, final loss estimate or technical cause is asserted here without a completed evidentiary basis.

Photograph and attribution

Richard Teng speaking at Binance Blockchain Week in Istanbul in November 2023; archival photograph. Photograph: Binance. Reused under Creative Commons; the exact licence and Wikimedia Commons source are linked below. No new image alteration by CryptoGov; existing crop where indicated. Gabriel Nicolaev — CyGuru.

Go deeper on CryptoGov

Sources & verification

Researched and published by CryptoGov Editorial Desk. Source publication and effective dates are explained in the article where relevant.