Binance Publishes Zero-Knowledge Reserve Proof for BTC, ETH and 8 Other Tokens After Hack
- Published
- Updated
- Since then
- 1 new report
- In
- Exchanges
Binance said it completed a zero-knowledge proof-of-reserves check for a snapshot taken on Oct. 31 and made the results available on Nov. 2. The proof covers 10 assets, including BTC, ETH, BNB, USDT and XRP, and Binance said holders of those tokens can verify that their balances are backed at least 1:1.
Key claims & sources
What it means
Binance is one of the largest crypto exchanges, and proof-of-reserves snapshots are a recurring way for centralized platforms to show that customer balances are matched by on-chain holdings. The Oct. 31 snapshot and the Nov. 2 publication sit in that wider practice, with Binance using a zero-knowledge method to let users verify balances without exposing more data than needed. The mention of the late-October security incident gives this update a post-incident setting rather than a routine disclosure.
For traders and token holders on Binance, the immediate practical change is access to a verification step for the listed assets, including BTC, ETH, USDT and XRP. That does not turn the exchange into a fully audited institution, and it does not erase the need for users to think separately about custody, withdrawals and counterparty exposure. The update also shows how exchanges try to reassure users after security events without making stronger promises than a reserves snapshot can support.
The bigger issue is the gap between reserve verification and a true financial audit. Crypto exchanges can publish reserves data while still leaving open questions about liabilities, operational risk and what happened to assets in a security incident. Binance’s use of zero-knowledge proofs shows how the industry keeps pushing for privacy-preserving transparency, while still stopping short of the kind of disclosure that would settle every concern.
What remains open is how the Oct. 31 snapshot relates to Binance’s broader balance sheet and to the late-October security incident. The proof tells users that balances for the 10 named tokens were backed at least 1:1 at that snapshot, but it does not answer whether any losses were absorbed elsewhere or how long the verification will remain current. Further disclosures from Binance would be needed to settle those points.
Market reaction i
The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| 1 days ago | Loopscale Lending · Unknown incident | no figure in dollars |
| 1 days ago | TENDRIL · Swap Logic Flaw incident | $550k |
| 1 days ago | $TENDRIL · Smart contract vulnerability incident | $555k |
| 3 days ago | InsurancePool/CoreVault · Flash loan attack incident | $112.3k |
| 4 days ago | Solana MEV Bot King · Hot wallet key compromise incident | $856k |
4280 incidents stored