Binance Says Hack Losses Are Covered, but Its USDT Reserve Gap Needs Checking

Binance says it has covered every asset affected by its Oct. 29 hack. The catch is that customers can't check that claim for themselves yet, and that gap matters more than the headline suggests. Exchange hacks rarely end with a clean accounting, so the real question isn't only whether the money is there. It's whether anyone outside the company can see it.

On Nov. 12, the exchange posted on X that it had "completed coverage of assets impacted in the security incident" and published a new Proof of Reserves snapshot. Yi He reposted the statement with one word: "100%." That's a confident message, but the verification tools haven't caught up. Here's the thing: a reserve claim is only as good as the mechanism that lets outsiders test it, and that mechanism is still in progress. Binance says that "once the zero-knowledge proof is generated," users will be able to confirm their assets are backed "at a minimum of 1:1." A zero-knowledge proof lets each customer confirm their balance is counted in the reserve total without exposing anyone else's data.

Zero-knowledge proofs are a real technique, and they're worth understanding even if you'll never run the math yourself. The core idea is that an exchange can prove a total without revealing the individual balances behind it. Similar systems typically pair that cryptography with some form of published wallet data, so outside observers can check that the reserves exist onchain. Binance's version hasn't shipped its proof yet, which makes the design promising but untested in this specific case.

What the Reserve Page Shows

As of Nov. 13, Binance's Proof of Reserves page listed reserve ratios of 100.05% for bitcoin, 100.02% for ether and 104.34% for USDT, Tether's dollar-pegged stablecoin. Each ratio compares Binance's onchain wallet balance against what the page labels net account balances. A ratio above 100% means the wallets hold more than customers are owed on paper, and a ratio below it would be the warning sign everyone watches for. Those three numbers look reassuring at first glance, but a surplus only means something if the definitions underneath it hold up.

The USDT figure is the one to watch. By my calculation from the page's own numbers, Binance's onchain USDT sits about 1.06 billion tokens above net customer balances. That onchain total includes roughly 306.7 million USDT held by third-party custodians (and this is the part most people overlook). Those custodial holdings count toward the total, which means the surplus depends partly on balances Binance doesn't directly control. I'd call that the number that deserves a closer look before the headline percentage does.

Replenished From Binance's Own Funds

The hack involved digital assets Binance valued at about $6.34 billion. In an earlier update, the exchange confirmed that for the 10 tokens in its Oct. 31 snapshot, "the affected assets were replenished using Binance's own funds." Its Nov. 2 recovery update put the covered share at about 95% of the impacted amount and said Binance would absorb the loss rather than pass it to users. That update also came with the zero-knowledge proof for the Oct. 31 snapshot.

Absorbing a loss sounds simple, but it's a real balance-sheet decision, and it's the strongest part of the company's pitch. It's more meaningful than a reserve ratio, because it commits the exchange's own money rather than just describing what's sitting in its wallets. Still, the numbers don't line up neatly. The Nov. 2 update said 95%, and the Nov. 12 post said "completed coverage." The source doesn't explain the difference, and that's the kind of gap a careful reader should flag rather than smooth over.

Binance's incident report said about $2.85 billion of the stolen assets had been frozen or intercepted, a figure it describes as subject to verification. That's a bit under half of the $6.34 billion valued total, so the frozen-or-intercepted number carries a lot of weight in the recovery story. Frozen funds and recovered funds aren't the same thing, and the distinction matters if you're trying to work out what was actually returned.

Timing and the Verification Gap

Timing is the open question. The Nov. 12 post didn't say when the next proof will be ready. The Nov. 2 update estimated that proof for the Nov. 4 snapshot would take 40 to 50 hours to generate. Forty to fifty hours is a long wait when the claim is already 100%, and it's a long wait when the company presumably knows exactly what it holds. Proofs like this are computationally heavy, so long generation windows are a general feature of the category rather than a red flag on their own. Still, the delay is what keeps the claim unverifiable for now.

Until the proof is published, the 100% claim rests on Binance's word, and the USDT surplus on the reserve page is where scrutiny will land first. That's the honest read. Nothing in the source suggests a shortfall, but nothing in it proves a surplus either. Mechanically, the claim checks out on paper. Verifiably, it doesn't yet. Not yet.

What This Means for Customers and the Industry

If you're a Binance user, the useful distinction is between the post and the proof. The post tells you what the company says its position is, while the proof lets you check it yourself. Those are different things, and exchange statements of this kind usually arrive faster than the verification does. Reading a reserve page takes some skill, and most customers won't do it, which means the ratio is mostly a signal for journalists and analysts rather than for everyday account holders. If you're in this space professionally, that's where your attention belongs.

For the wider industry, this episode tests a pattern more than it tests one company. Reserve attestations have become a common trust signal across crypto exchanges, and the gap between announcement and verifiable data is exactly where that signal gets weaker. I'd argue the platforms that publish proofs on a predictable schedule will earn more credibility than the ones that announce 100% and ask for patience. Whether Binance's next snapshot lands cleanly will say far more than any reposted word.