Independent record. Not associated with, endorsed by or operated by Binance. We will never ask you to connect a wallet, log in or pay to recover funds.
Newest first. The raw hash is the SHA-256 of the stored copy exactly as fetched. The text hash is of the text extracted from it, which is what is compared between captures.
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.
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).
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%.
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.