Independent record. Not associated with, endorsed by or operated by Binance. This site is read-only: there is nothing to sign in to, pay for or connect.
An independent record of the October 2026 Binance hack
Newest first. The raw hash is the SHA-256 of the stored copy exactly as fetched. We keep the copy privately and publish its hash. The text hash is of the text extracted from it, which is what is compared between captures.
| Captured (UTC) | Fetched via | HTTP | Raw sha256 | Text sha256 | Text changed |
|---|---|---|---|---|---|
| http | 200 | fb54a098858000d45acb5e5be5db7f265a2d7cd72b461aec8cf060e4a11d8995 | 4af35c432514cd942f41553c3dd63ca7dcbf3caed16d593be42ef98852bd97fd | No |
No text changes detected between captures of this source.
As noted in Recovery Update #4, Binance has covered approximately 95% of the impacted amount. The outstanding 5% consists of tokens not included in the top ten listed above. These assets are less liquid, and take longer to source at the required scale.
We are also working to resume withdrawals for additional networks and assets. The next phase is planned for tomorrow — this will be a progressive rollout and we will share the details once ready.
The full zero-knowledge proof for this latest PoR snapshot has been completed within our estimated timeframe. Binance users holding any of these ten tokens can independently verify that their balances on Binance are backed at a minimum of 1:1.
We plan to take another snapshot with coverage for more tokens on 2026-11-04. We will then generate an updated full zero-knowledge proof, which we estimate will take approximately 40 to 50 hours to complete due to the computational workload.