In Recovery Update #3, we confirmed that the affected assets were replenished using Binance’s own funds, and that all BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD, and ZEC are 100% fully backed. We also took a new Proof of Reserves (PoR) snapshot as of October 31, 2026, at 02:00 (Kyiv time), to provide updated asset data and ensure transparency.
The full zero-knowledge proof for this latest PoR snapshot was completed within our expected timeframe. Binance users who hold any of these ten tokens can independently verify that their Binance balances are backed at least 1:1. Users can do this using the verification tool on our PoR website. Instructions are provided in our guide here.
We plan to take another snapshot covering more tokens on November 4, 2026. After that, we will generate an updated full zero-knowledge proof, which we estimate will take approximately 40 to 50 hours to create due to the significant computational workload.
As stated in Recovery Update #4, Binance has covered approximately 95% of the affected amount. The remaining 5% consists of tokens not included in the top ten listed above. These assets are less liquid, so acquiring them in the required quantities takes longer. We continue to work with industry partners to complete the acquisition of the remaining assets.
We are also working to restore withdrawals for additional networks and assets. The next phase is scheduled for tomorrow and will be rolled out in stages. We will share details as soon as everything is ready.
Our commitment remains unchanged: Binance will bear the financial consequences of the theft, not our users. Thanks to the generated proof, the backed portion of this commitment can now be publicly verified.
November 2, 2026
Frequently Asked Questions About Verifying Proof of Reserves
Binance publishes Proof of Reserves (PoR) so users don't have to simply take our word for it. Anyone can learn more about PoR and how it uses cryptography to prove that users' assets on Binance are backed at least 1:1 here.
Users can learn how to perform the verification in our guide here.
Before you begin: You need to log in to your Binance account and download the verification tool from the PoR website to your computer to perform your own verification.
Security reminder: For your own safety, use only the official Binance website. Do not share your login credentials with anyone or use untrusted devices.
Why is verifying my assets with PoR so complicated?
We understand that verifying PoR can seem technically complex. It is based on cryptography, not on a figure we ask you to trust, and every step is designed to ensure that you don't have to rely solely on Binance's word. To simplify the process, we have published a step-by-step guide here.
Why do I need to download verification files to my computer?
You perform the verification on your own devices so you can be sure that you are running your own checks on your own computer.
The verification tool is open source, and anyone can download and run it. We publish updates in an open GitHub repository, and the code has undergone an independent audit (for example, see the link). This allows the developer community and the general public to review the implementation and ensure transparency.
Are PoR and zero-knowledge proofs reliable?
Yes. Binance's Proof of Reserves uses a Merkle tree system with zk-SNARKs (succinct non-interactive zero-knowledge proofs).
A Merkle tree allows each user to independently verify that their account assets are included in the reserves snapshot.
The zk-SNARK proof confirms that reserves are backed at least 1:1 for the snapshot taken on October 31, 2026, at 00:00 (UTC)—without revealing any individual user's balance.
Taken together, the results are cryptographically verified: you can confirm that your assets are covered and included in the PoR snapshot we published without revealing your balance or the balance of any other user.
Please note: discrepancies may exist between this original English content and any translated versions (which may be generated by AI). In the event of any discrepancies, please refer to the original English version for the most accurate information.
