Binance Completes Zero-Knowledge Proof of Reserves

Binance has completed a full zero-knowledge proof of reserves, the exchange said in its fifth recovery update on November 2, marking a significant step in its response to the recent security incident that disrupted withdrawals and shook confidence across the crypto market. The proof covers a snapshot taken at 00:00 UTC on October 31 and allows users to verify that ten major tokens were held on a one-to-one basis at that moment. For an exchange handling billions of dollars in customer assets, that kind of verification matters, because customers cannot see inside its wallets and must otherwise take its assurances on trust. A cryptographic proof does not remove every question, but it gives independent observers a way to check a specific claim rather than simply believing it.

The update arrived as Binance was working to restore normal service in stages, with withdrawals reopening progressively and further snapshots planned in the days ahead. According to the exchange, about 95 percent of the stolen amount was now covered, up from 90 percent on October 31, with the remaining 5 percent consisting of less-liquid tokens that are harder to replace quickly. The next snapshot is scheduled for November 4 and is expected to cover more tokens, while the next zero-knowledge proof is expected to take 40 to 50 hours to compute. The next withdrawal phase was planned for November 3 on a progressive rollout. Together, those steps sketch a recovery that is advancing, but not yet finished, and users are being asked to judge progress in stages rather than waiting for a single all-clear moment.

Binance Proof of Reserves Explained in Plain Terms

A Binance proof of reserves is, at its core, a method for showing that customer balances are backed by real assets held by the exchange. Traditionally, proof of reserves has relied on a Merkle tree, a data structure that lets each user check that their balance was included in a larger total without revealing other users’ balances. Binance’s latest step goes further by adding zero-knowledge technology, specifically zk-SNARKs, which allow the exchange to prove a statement is true without revealing the underlying private data. In this case, the statement is that the assets held match the liabilities owed to customers for the tokens covered, at the snapshot time.

Which Tokens the Zero-Knowledge Proof Covers

The completed proof covers ten tokens that users can verify on a one-to-one basis: Bitcoin, Ethereum, Tether, BNB, Solana, USD Coin, XRP, USD1, RLUSD, and Zcash. Those are among the most widely held assets on the platform, so covering them addresses the balances that affect the largest number of customers. A one-to-one claim means that, at the snapshot moment, the exchange held at least as much of each token as customers were collectively owed in that token. If a token is not on the list, that does not automatically mean it is unbacked, but it does mean this particular proof does not verify it, and users holding other assets should wait for later snapshots.

Binance said the next snapshot on November 4 will cover more tokens, which suggests the list is intended to expand rather than remain fixed at ten. That expansion matters, because a proof that covers only the most liquid or most popular assets leaves questions about the rest of the balance sheet. The exchange has also said the next zero-knowledge proof will take 40 to 50 hours to compute, a reminder that this kind of verification is computationally demanding and cannot be produced instantly on demand. Users should therefore expect a lag between a snapshot date and the publication of its proof, and should not interpret that lag alone as a warning sign. What matters is whether each promised proof arrives, whether it covers the tokens claimed, and whether independent checks confirm the results.

What 95 Percent Coverage Means and What It Does Not

Binance reported that about 95 percent of the stolen amount is now covered, up from 90 percent on October 31. That improvement suggests the exchange has been able to source or recover additional assets over the intervening days, narrowing the shortfall created by the theft. The remaining 5 percent, described as less-liquid tokens, is a reminder that not all crypto assets can be replaced at the same speed. Liquid tokens such as Bitcoin and major stablecoins can be bought or moved relatively quickly, while smaller or thinner markets may require more time, negotiation, or recovery work. For customers, the headline percentage is encouraging, but it is not the same as saying every individual balance is whole.

It is also important to understand what coverage means in this context. Covering the stolen amount generally refers to the exchange making itself whole for the loss, so that customer balances remain backed, rather than each affected user receiving a separate reimbursement. The proof of reserves then checks whether backing exists at a point in time. Those are related but distinct ideas, and neither should be confused with a guarantee that no future incident can occur. Security improvements, withdrawal controls, and ongoing monitoring will matter just as much as the recovery percentage. Readers should therefore treat 95 percent as a progress marker on a continuing process, not as a final verdict, and should watch for the November 4 snapshot and subsequent proof as the next test.

A Snapshot Is Not a Solvency Proof

Perhaps the most important caveat in this story is that a proof of reserves is a snapshot, not a solvency proof and not a picture of the exchange’s current position. The completed proof relates to balances at 00:00 UTC on October 31. Anything that happened after that moment, including withdrawals, deposits, trading, and further recovery work, is not captured by that proof. An exchange could, in theory, be fully backed at the snapshot moment and face different conditions days later, just as it could improve after a weak snapshot. That is why Binance’s plan for repeated snapshots matters: a single proof is a data point, while a series of proofs over time builds a more useful pattern.

The caveat also extends to liabilities beyond customer crypto balances. A proof of reserves typically verifies that crypto assets match crypto liabilities for covered tokens, but it does not by itself audit all corporate debts, off-platform obligations, or operational risks. That limitation does not make the proof worthless; it simply defines what it can and cannot show. Users who understand that boundary are less likely to overreact in either direction, either dismissing a genuine transparency step or treating it as total assurance. The responsible way to read the November 2 update is as evidence about one specific question at one specific time, with further evidence still to come.

How Withdrawals Fit Into the Recovery Timeline

Withdrawals are where recovery promises meet everyday user experience, because customers judge an exchange less by technical announcements than by whether they can access their funds. Binance said the next withdrawal phase was planned for November 3 on a progressive rollout, meaning access would expand gradually rather than switching on all at once for every asset and network. A phased approach is common after a major incident, because it allows the exchange to test systems, manage liquidity, and respond to problems before they affect all users. It can frustrate customers who are waiting, but it is often safer than an immediate full reopening that could strain hot wallets or reveal unresolved issues.

Why Zero-Knowledge Proofs Matter for Crypto Exchanges

Beyond Binance itself, the completion of a zero-knowledge proof of reserves may influence expectations for the wider exchange industry. After several high-profile exchange failures in past years, customers and regulators have increasingly demanded stronger evidence that customer assets are segregated and fully backed. Traditional proof of reserves was a step in that direction, but critics noted its limitations, including the snapshot problem and the difficulty of verifying liabilities. Zero-knowledge methods address some of those criticisms by making verification more rigorous while preserving privacy, and if they become standard practice, they could raise the bar for all large platforms.

That shift will not happen overnight, and it will not solve every trust problem in crypto. Proofs still depend on honest inputs, correct implementation, and repeated publication, and they still leave out parts of a company’s finances. Yet the direction is clear: exchanges that can produce timely, independently verifiable proofs will have an advantage in winning back cautious customers, while those that rely only on statements may face more scepticism. Binance’s November 2 update should therefore be read on two levels: as a specific recovery milestone for one exchange, and as an example of the kind of transparency tool the industry is moving toward. Whether it becomes a lasting standard will depend on how consistently Binance and its competitors publish such proofs, and how seriously users and auditors treat them.

What is a zero-knowledge proof of reserves?

It is a cryptographic method that lets an exchange prove customer balances are backed by assets at a snapshot time, without revealing individual account details. Binance used a Merkle tree combined with zk-SNARKs for its October 31 snapshot.

Which tokens does Binance’s latest proof cover?

Ten tokens are verifiable one-to-one: Bitcoin, Ethereum, USDT, BNB, Solana, USDC, XRP, USD1, RLUSD, and Zcash. More tokens are expected in the November 4 snapshot.

Does this proof mean Binance is fully solvent?

No. It is a snapshot at 00:00 UTC on October 31 for covered tokens, not a full solvency audit or a picture of the current position. Repeated snapshots and proofs are needed for a fuller view.

When is the next proof expected?

The next snapshot is scheduled for November 4, covering more tokens, with the next zero-knowledge proof expected to take 40 to 50 hours to compute.

Source: Binance

Related reading on MM Crypto Analysis Web

• Next Technology Moves to Sell Up to $450 Million in Bitcoin After Binance Hack
• Binance Sees $3.64 Billion in Net Withdrawals as Services Resume After $6.3 Billion Hack
• Spot Bitcoin ETFs Lose $643 Million on October 30 as Futures Leverage Builds

More in Bitcoin on MM Crypto Analysis Web.