Binance's proof of reserves lands Nov 2: what it can prove, and what it can't

Binance says it will publish proof-of-reserves results by November 2, following the October 30 hot wallet breach. Before that report lands, it is worth knowing what you are looking at — because "proof of reserves" proves less than the name suggests, and the gaps matter more than the headline.

Start with what it is. In the typical setup, an exchange takes a snapshot of customer balances and publishes a cryptographic commitment to them — usually a Merkle tree, where each user's balance is a leaf and the published root lets any user verify their own balance was included. An auditor then checks that the assets the exchange shows control of are at least equal to those liabilities, at that snapshot moment. That is the whole mechanism: assets versus a defined set of liabilities, frozen at one point in time.

Here is what such a report can actually prove. First, that at snapshot time, the exchange held at least the stated amount in the stated assets. Second, if you check your own leaf, that your balance was included in the liability set — you are not being quietly left out of the count. Those two things are genuinely useful, and they are more than the public had before the report.

Here is what it cannot prove, and this is the part most coverage skips. One: completeness of liabilities. If some obligations are left out of the tree — off-books debts, liabilities held in entities outside the snapshot — the math still checks out, because the check only covers what was included. Two: ownership and encumbrance of assets. Assets shown in a snapshot might be borrowed for the occasion or pledged elsewhere; a snapshot does not show what those assets were doing the day before or will do the day after. Three: anything after the snapshot. Funds can move the next day, so a clean snapshot is a point-in-time claim, not an ongoing guarantee. Four: general solvency. A proof of reserves does not cover every kind of obligation, nor does it say anything about whether the assets could actually be liquidated fast enough in a bank run.

So when the November 2 report lands, read it with four questions. Who attested it — an independent auditor, or self-attestation? Does the liability set plausibly cover all account types, or only a convenient subset? Does the snapshot reflect the post-breach state, after the $6.34 billion cover Binance says it reserved, rather than a pre-breach picture? And is the asset breakdown given by token, so the cover can be compared against what was actually stolen, rather than presented as one lump sum?

One more thing to pair with the report: the phased withdrawal resumption itself, planned within about 34 hours of the incident. A snapshot is a claim; withdrawals actually processing is evidence. If both line up — a credible report plus money moving out normally — that is a much stronger signal than either alone.

Proof of reserves is a useful check. It is not a verdict. Treat it as one input, and keep watching the thing it cannot show you: what happens the day after the snapshot.