Edition and source dates
This November 2 edition covers selected developments from November 1–2, with October 31 background explicitly labeled. It is a weekend catch-up, not an exhaustive rolling 24-hour digest. Related announcements are treated as one recovery event.
What changed today
Binance's November 2 recovery update says the zero-knowledge proof for its October 31, 00:00 UTC reserves snapshot is complete and users holding the ten covered tokens can verify their balances using its tool. It also announces a broader snapshot planned for November 4 and a further withdrawal rollout planned for November 3. These are provider statements and future plans, not CryptoTrades verification of reserves or completed withdrawals. Binance update #5
The source displays November 2 at 12:45 without an explicit timezone in the retrieved publication label. The snapshot time, by contrast, explicitly uses UTC. Those timestamps describe different things: publication of the update and observation of the reported reserves.
Evidence: Binance update #5
Withdrawal access remains a separate question
The preceding November 1 announcement set out phased withdrawal restoration, with availability dependent on the asset/network combination and checks. A planned reopening window does not establish that a particular withdrawal will complete. CryptoTrades has not logged into a customer account or tested a withdrawal. November 1 announcement
Why it matters: balance inclusion, the scope of a reserves report and operational access to assets answer different questions. A cryptographic verification announcement should not be read as an unrestricted safety endorsement. SEC staff's educational bulletin explains why proof-of-reserves reports are not equivalent to financial-statement audits and may leave liabilities outside their scope. That general warning is not a finding about this particular snapshot. Investor.gov bulletin
Evidence: November 1 announcement · Investor.gov bulletin
Background, not a new November 2 incident
In an October 31 notice, the FBI attributed theft of more than $6 billion from Binance on or about October 29 to North Korea. That is the agency's attribution; CryptoTrades has not performed independent forensic analysis. FBI notice
Evidence: FBI notice
What remains unverified
We did not run the reserves verifier, validate its cryptography or inspect underlying assets and liabilities. We did not independently confirm the provider's replenishment claims, account-level withdrawal access or the completion of planned future steps. This briefing does not repeat secondary estimates of net outflows because their underlying dataset was not checked.
For a reusable reading checklist, see proof-of-reserves limitations. Report a correction with the public source and page title through Contact; do not send account records or credentials.
Sources & method
- Binance update #5
Primary documentation checked November 2, 2026. Provider claims retain the scope and limitations described above. Checked 2026-11-02.
- November 1 announcement
Primary documentation checked November 2, 2026. Provider claims retain the scope and limitations described above. Checked 2026-11-02.
- Investor.gov bulletin
Primary documentation checked November 2, 2026. Provider claims retain the scope and limitations described above. Checked 2026-11-02.
- FBI notice
Primary documentation checked November 2, 2026. Provider claims retain the scope and limitations described above. Checked 2026-11-02.
Continue learning
Found an error? Contact the editorial team with the page and supporting source. Never send private account information.