Binance's Extra Proof-of-Reserves Check Shows Bitcoin Holdings Up 0.35%

Binance's Nov. 12 proof-of-reserves snapshot recorded user Bitcoin holdings of roughly 687,900 BTC, an increase of 2,388 coins, or 0.35%, since the exchange's previous snapshot on Nov. 4. The company published the figures as an additional reserve check outside its usual monthly schedule, following an Oct. 29 security incident that involved approximately $6.34 billion in crypto assets.

The timing matters more than the percentages. Binance does not normally publish reserve data twice within a single month; the Nov. 12 release exists because the October breach damaged confidence in the exchange's solvency posture. Binance stated that it has fully replenished the affected assets. That claim is the company's own, and the snapshot itself does not independently verify the reserve side of the balance sheet against the liabilities it reports.

What do the numbers actually show?

The snapshot is a point-in-time count of what users hold on the exchange, not an audited reconciliation of assets against obligations. By that measure, the changes since Nov. 4 are modest across the board:

• Bitcoin (BTC): about 687,900 BTC, up 2,388 coins, or 0.35%
• Ether (ETH): 3.48 million ETH, up 1.04%
• BNB: 42.95 million BNB, up 1.03%
• Tether (USDT): 24.3 billion tokens, down 928 million, or 3.68%

The Nov. 4 snapshot had placed user USDT balances at 25.227 billion tokens. A decline of 928 million tokens in eight days is the one materially large movement in the dataset. To put the figure in frame, the outflow equals roughly 3.7% of the stablecoin balance Binance reported at the start of the month, and it dwarfs the coin-denominated shifts in BTC, ETH and BNB, which all moved by about one percentage point or less.

Why did Binance run an extra check?

The Oct. 29 hack is the stated reason. Binance said the incident involved approximately $6.34 billion in crypto assets, a figure large enough to rank among the largest exploits on record if confirmed. The company's response has two visible components: replenishment of the affected assets, which Binance says is complete, and this out-of-schedule reserve publication, which is designed to demonstrate that user balances have not contracted.

The data lends partial support to that argument. Bitcoin, Ether and BNB holdings all rose slightly between Nov. 4 and Nov. 12, which is inconsistent with a mass withdrawal event on the order of billions of dollars in those assets. The USDT decline is the exception, and the snapshot alone cannot distinguish between users withdrawing stablecoins, internal transfers, or other movements. Binance did not explain the USDT outflow in the release.

What the snapshot also does not say deserves weight. Proof-of-reserves reports in this format show liabilities; they do not, on their face, prove that matching assets exist, are unencumbered, or are recoverable in a stress scenario. The market has no independent attestation of the Nov. 12 figures in the published material. Readers should treat the numbers as exchange-reported data rather than third-party verification. In plain words: users did not flee Bitcoin balances, but nobody outside Binance has checked the vault.

What happens next?

The Nov. 12 release sits outside the normal cadence, so the next scheduled monthly snapshot will carry the real informational load. If USDT balances stabilize and coin holdings hold steady, the October incident's operational damage will look contained; if the stablecoin decline extends into December, questions about deposit flight will sharpen regardless of what Binance asserts.