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).
Binance said in Recovery Update #3 that the full zero-knowledge proof takes approximately 40 to 50 hours to generate and was estimated to be ready by Tuesday 2026-11-03 UTC.
This line is our short summary of the quote below. The quote is the evidence.
Other claims from the same source
Binance said in Recovery Update #3 that it is committing to replenishing the SAFU fund to approximately US$1 billion.
Binance is committing to replenishing the SAFU to return the fund size to approximately US$1 billion.
Binance said in Recovery Update #3 that it remained on track to reopen withdrawals on Sunday 2026-11-01.
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 said in Recovery Update #3 that the replenishment employed a partial deployment of its SAFU fund, a portion of its Futures insurance fund, and its own corporate treasury.
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.
Binance said in Recovery Update #3 that BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC are fully backed 100%.
All BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD, and ZEC are fully backed 100%.
Binance said in Recovery Update #3 that the amount of the hacked loss it had covered was now up to 90%, up from approximately 80% in the previous update.
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%.