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 | 3a7d30300c6f9d227c44694d4fceafa5ff8f7d3b176c5c02f0e11c3570be4094 | d2e33415dbeb80ee1a75a865d9ee12d295020291b44840e9f363c34b79b0d8b9 | No |
No text changes detected between captures of this source.
we have taken a new Proof of Reserve (PoR) snapshot at 2026-10-31 00:00 (UTC), and this has already been updated on the PoR website.
A partial deployment of the Secure Asset Fund for Users (SAFU). This is expected to happen over the next 24 hours; users can view the updated balance here.
A portion of our Futures insurance fund. The remaining balance of the Futures insurance fund is a regulatory requirement.
The full zero-knowledge proof takes approximately 40 to 50 hours to generate due to the computational workload
The SAFU fund is held and managed by Nest Clearing and Custody Limited, a Recognized Clearing House regulated by the Abu Dhabi Global Market (ADGM) Financial Services Regulatory Authority.
so users holding any of these ten tokens can independently verify that their assets are at a minimum 1:1 backed once the full proof is generated, estimated to be by Tuesday, 2026-11-03 (UTC).
The outstanding 10% consists of tokens outside the top ten listed above.
Our last update explained that Binance had set aside more than $6.34B in company funds to cover hacked losses, and we had already covered approximately 80% of the impacted amount of the hacked loss at that time. That covered amount is now up to 90%.
All BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD, and ZEC are fully backed 100%.
The replenishment employed: - A partial deployment of the Secure Asset Fund for Users (SAFU). This is expected to happen over the next 24 hours; users can view the updated balance here. - A portion of our Futures insurance fund. The remaining balance of the Futures insurance fund is a regulatory requirement. Users can check the updated balance of the fund here. - Binance's own corporate treasury.
The full zero-knowledge proof takes approximately 40 to 50 hours to generate due to the computational workload, so users holding any of these ten tokens can independently verify that their assets are at a minimum 1:1 backed once the full proof is generated, estimated to be by Tuesday, 2026-11-03 (UTC).
We remain on track to reopen withdrawals within our previously stated timeframe (on Sunday, 2026-11-01) and will provide a further update as soon as details are confirmed.
Binance is committing to replenishing the SAFU to return the fund size to approximately US$1 billion.
SAFU is an emergency reserve fund established by Binance in July 2018 to protect user assets in extreme cases, such as security breaches or platform-level incidents. Binance allocated a percentage of trading fees to grow the fund to a substantial level over time. The SAFU fund is held and managed by Nest Clearing and Custody Limited, a Recognized Clearing House regulated by the Abu Dhabi Global Market (ADGM) Financial Services Regulatory Authority. A portion of the funds serves as capital reserves as part of Binance regulatory obligations in the ADGM.
The Futures Insurance Funds remain above the coverage level required under Binance’s established risk-management framework, helping ensure the fund remains available to support users during extreme market conditions. We monitor fund size continuously against historical stress scenarios reflecting extreme but plausible market conditions, and top it up when required. Due to volatility, no exchange can completely avoid auto-deleveraging, but we always strive to keep occurrences to a minimum. Will Binance replenish the Futures Insurance Funds? The funds are maintained above their required size. When the balance falls below the level our framework requires, Binance tops them up from company funds, as we have done previously. What was released was excess above that level, which is why it could be reallocated without affecting coverage.