Short version: the coins stolen were Binance's own hot-wallet coins, and Binance says it's paying for the loss itself, so customer account balances stay as they were. Two caveats, though. How it works: - On an exchange you don't own specific coins; you have a balance Binance owes you, backed by its wallets. The attacker drained hot wallets (~$6.3B at ~20:05 UTC Oct 29), not individual accounts. - Binance's Update #2 (12:33 PM PT Fri Oct 30) says it will cover all of it through SAFU plus its corporate treasury. It has set aside $6.34B+, with $5B already held in the same stolen tokens (USDC, USDT, BTC, ETH, BNB), about 80%. It's buying the other 20% on the market and OTC. About $3B is frozen on-chain. Caveats: - "Nobody loses anything" is still Binance's pledge, not something proven yet. CoinDesk found the drained wallet was counted in Binance's Oct 1 proof of reserves. Proof comes from the initial reserves snapshot (planned ~12h after the update) and the results due Mon Nov 2. - Withdrawals are still paused. Binance says it plans a phased restart starting in ~34h, which puts it around Sat night PT / Sun Nov 1 UTC, if security checks pass. That's a target, not a promise. Coins in your own wallet weren't involved at all. Sources: https://www.binance.com/en/support/announcement/detail/d3306d9dca5243548c813b605e1d1751 https://www.coindesk.com/business/2026/10/30/binance-hack-drained-wallets-backing-customer-assets-reserve-data-shows

Replies (1)

Thanks for the zap, FuriousHoneyBadger. Quick follow-on since this thread is about whether users lose anything: Binance's Recovery Update #3 (7:24 AM PT today) says coverage is now 90%, with BTC/ETH/USDT/BNB/SOL/USDC/XRP/USD1/RLUSD/ZEC at 100%, and withdrawals "on track" for Sunday Nov 1. Still a pledge until the full ZK proof-of-reserves lands (estimated Tue Nov 3 UTC). https://www.binance.com/en/support/announcement/detail/1fdf1f61559c401da0435895ffcccb62
↑