Binance completes zero-knowledge proof-of-reserves after October hack, reports 95% replenishment

3 min

TL;DR: Binance said on November 2 it completed a zero-knowledge proof-of-reserves for an October 31 snapshot after its late-October security incident. Proof of reserves is not a full financial audit, a loss guarantee or evidence that all stolen assets have been returned.

What the primary source establishes

Binance reported completion of a zero-knowledge proof-of-reserves for ten major assets on an October 31 snapshot: Bitcoin, Ether, USDT, BNB, Solana, USDC, XRP and several dollar tokens. The company said its affected asset replenishment reached about 95% at the time of the update. The dated original disclosure anchors the figures and scope.

A proof-of-reserves test shows whether exchange-controlled assets cover included customer balances under the stated method and date. Zero-knowledge techniques can prove this without revealing every account balance. The test does not assess other corporate liabilities, future cash flows, operational security or the completeness of all entities in a corporate group.

Why this matters beyond the headline

A new snapshot provides a dated checkpoint and enables comparisons if disclosures remain consistent. A positive result on October 31 does not certify later withdrawals or prevent a future attack. A sound assessment combines reserve data, functioning withdrawals and deposits, incident disclosure and independent scrutiny.

Security incidents produce overlapping timelines: containment, investigation, recovery and return to reliable service. A traced wallet is not automatically frozen. A frozen balance is not automatically returned. Reopened withdrawals do not equal a completed security audit. Distinguishing these helps judge progress.

What the announcement does not prove

Proof of reserves is not a full audit, a guarantee against losses or confirmation that all stolen assets have been recovered. The 95% replenishment refers to affected asset coverage, not a uniform ratio for each token. Liquidity and availability can vary by asset even when the aggregate recovery appears strong.

Operational controls are most important under stress. Security updates should state the affected systems, which customers can act, the evidence behind recovery figures and remaining uncertainties. Clear scope reduces false reassurance and unwarranted alarm and supports later accountability.

What to watch next

Binance said another snapshot would follow on November 4 and that the related proof process could take about 40 to 50 hours. Key checks: published scope, proof methodology and any changes in customer liabilities. Separate withdrawal updates will show whether on-chain and internal reserves translate into reliable customer access.

This article was written by the News Desk and edited by Samuel Rae.