Horizontal bar chart comparing what Binance says it has covered with company funds (more than $6.34 billion, 12 Nov 2026), what the U.S. Justice Department counts as frozen (more than $2.7 billion on 12 Nov, of which more than $1.2 billion has seizure authorization and is not added on top), and the 18,270.2 BTC still held by the attacker, valued at $1,255.3 million at the NodeWitness closing price of 13 Nov 2026 ($68,710.01).
NodeWitness chart. The frozen bar is the DOJ figure of 12 Nov (more than $2.7 billion); the $1.2 billion authorized for seizure is part of that total, not an extra amount. That total includes, among other freezes, more than $1.5 billion by Tether (2 Nov) and about $1.1 billion by Circle (5 Nov). The 18,270.2 BTC are valued at $68,710.01, the NodeWitness closing price for 13 Nov 2026 (/api/market/metrics).

Binance Says It Has Covered 100% of the $6.34 Billion Hack and Publishes a New Proof of Reserves

On November 12 Binance said it had finished covering the assets hit by the October 29 hack — more than $6.34 billion — and published a new proof of reserves. Coverage is not the same as getting the stolen coins back. The attacker's 18,270 BTC have not moved, and the zero-knowledge proof that would let each user check their own balance is not ready yet.

What Binance says it has covered

Binance has also committed to replenishing SAFU to about $1 billion, so the fund remains an emergency reserve [1]. A very small number of tokens it no longer lists were also affected; the exchange says those will be handled under its delisting process and that users who hold them will be covered [1].

That closes a process Binance itself had left unfinished. Its November 3 initial report said 98% of the affected tokens had been replenished by October 31 and that it was still buying the less liquid remainder, as we described in our piece on the frozen funds and the 18,270 BTC [3][4]. The November 12 statement is the first time it has said that work is complete.

Covering customer balances is not the same as recovering the stolen coins. The announcement does not say how much of the haul has been retrieved, and it does not name an attacker [1]. We traced how the 18,270 BTC left a hot wallet in our October 29 piece.

The new proof of reserves

Binance took the snapshot at 00:00 UTC on November 12 (01:00 in Madrid) and says it covers 198 tokens. The figures are on its proof-of-reserves page [5]. For bitcoin, that page shows:

Item BTC
Net customer balances 687,912.027
On-chain wallet balance 688,283.654
Of which, exchange balance 677,744.009
Of which, third-party custody 10,539.645
Reported ratio 100.05%

Source: Binance proof-of-reserves page, snapshot of November 12, 2026 at 00:00 UTC [5]. The ratio is the one Binance publishes; 688,283.654 / 687,912.027 equals 1.00054, which matches that 100.05%. Exchange balance plus third-party custody adds up to the on-chain wallet figure.

The declared surplus is 371.627 BTC, 0.05% above customer balances. The page itself warns that the excess held in proof-of-reserves addresses is not a measure of Binance's overall own assets [5]. In the same snapshot the exchange reports ratios of 100.02% for ETH, 104.34% for USDT and 100.39% for BNB [5].

What is still missing is the zero-knowledge proof (zk-SNARK). Binance says it will take about 40 to 50 hours to generate because of the computational workload, after which users who hold the affected tokens will be able to check for themselves that their assets are backed at least 1:1 [1][5]. When this piece was written, that proof was still pending. Until it appears, the 1:1 claim is Binance's statement, not a check each customer can run.

What we were able to see on the chain

Binance's proof-of-reserves page also publishes a list of reserve addresses. This time we could not download it: the page returns an automated check against non-interactive requests, and we did not find a public file equivalent to the PR31OCT26_HotCold.csv and PR31OCT26_New_Wallet_Address.csv we retrieved after the October 31 snapshot [6]. Without a current official list, we cannot independently add up the 688,283.654 BTC Binance reports in wallets, either at the snapshot height of 00:00 UTC on November 12 or at the tip now.

There is a further caveat. Of those 688,283.654 BTC, Binance itself assigns 10,539.645 BTC to third-party custody [5]. That slice would not necessarily show up in a sum of the addresses the exchange lists as its own.

What we could check again is the attacker's bitcoin. The 18,270.2 BTC that left Binance's hot wallet on October 29 ended in 19 outputs, the same ones we have followed since our piece on the haul and since withdrawals reopened [3][6]. At block 975,692 (15:34:59 UTC on November 13, 16:34 in Madrid), all 19 large outputs were still unspent. The 19 addresses together held 18,270.20166879 BTC: the difference, about 0.0018 BTC, is dust deposited after the split, as in earlier readings [7]. None had a spend in the mempool.

In other words, Binance may have replaced customer balances with its own funds, and the 18,270 stolen BTC are still where the attacker left them.

Withdrawals are still coming back in phases. The November 12 announcement does not reopen the platform all at once, and it says further updates will follow once they are confirmed [1]. That staged restart, which began with bitcoin on November 1, is the one we described in our piece on the new wallets [6].

What to watch next

The first test is the zero-knowledge proof, due around November 14 if the 40-to-50-hour window Binance gave on the 12th holds. The second is whether the bitcoin address list for this snapshot can be read and summed, and whether that sum is close to the 677,744.009 BTC the exchange attributes to its own wallets. The third is simpler and does not depend on any announcement: if the attacker's 19 outputs move, the chain will show it.

The earlier count of what was frozen, of the 98% Binance said it had already replenished, and of where the 18,270 BTC sit is in our October 30 piece. How the money left is in our October 29 piece. The market pulse is on the market page.

Sources

The type of source is in parentheses.

  1. Binance, Binance Completes Coverage of Assets Impacted in Security Incident; New Proof of Reserves Published, November 12, 2026. Coverage completed, more than $6.34 billion in company funds (SAFU, futures insurance fund and treasury), a commitment to replenish SAFU to about $1 billion, a reserves snapshot at 00:00 UTC on November 12 covering 198 tokens, a zero-knowledge proof in about 40–50 hours, withdrawals reopening in phases, and unsupported tokens. (Primary, company)
  2. Bitcoin Magazine, Binance Says It Has Fully Covered the $6.34 Billion Hack With Company Funds, Micah Zimmerman, November 12, 2026. Reports the announcement, notes that Binance repeated the same message on X, distinguishes coverage from recovery and says the zk proof was still pending. (Secondary, press)
  3. NodeWitness, After the Freezes, Binance Says It Has Replenished 98% of the Assets Hit in Its $6.34 Billion Hack, October 30, 2026, updated November 4, 2026. Initial report of November 3, 98% replenished by October 31, and 18,270.2 BTC in 19 outputs. (Primary, our earlier piece)
  4. Binance, 29 October 2026 Binance Security Incident: Initial Findings and Response Update, November 3, 2026. $6.34 billion affected, $2.85 billion frozen or intercepted, and 98% replenished by October 31, which the exchange said could be checked on its proof-of-reserves page. (Primary, company)
  5. Binance, Proof of Reserves, consulted November 13, 2026. Snapshot of November 12, 2026 at 00:00 UTC: BTC ratio 100.05%, net balances 687,912.027 BTC, on-chain wallet balance 688,283.654 BTC (677,744.009 at the exchange and 10,539.645 in third-party custody); ETH 100.02%, USDT 104.34% and BNB 100.39%. The page warns that excess assets in proof-of-reserves addresses are not a measure of Binance's overall own assets. (Primary, company)
  6. NodeWitness, Binance Reopens Bitcoin Withdrawals From a New Wallet That Paid Out 8,801 BTC in 15 Blocks, November 1, 2026. Address files for the October 31, 2026 snapshot (PR31OCT26_HotCold.csv and PR31OCT26_New_Wallet_Address.csv) and the phased restart. (Primary, our earlier piece)
  7. NodeWitness, our own reading on November 13, 2026: address API (/api/onchain/address) for the attacker's 19 final addresses, and the status of the 19 large UTXOs. Block 975,692 (15:34:59 UTC, 16:34 in Madrid). All 19 large outputs were still unspent; the 19 addresses together held 18,270.20166879 BTC (the difference from the original 18,270.2 BTC is dust deposits). (Primary, chain)

More in Price and market

See all 34 articles in Price and market →

Last updated: November 13, 2026