Binance Hack Losses: What Its $6.34B Claim Means
Binance says it reserved $6.34 billion after a record hack. Learn what matching-token coverage and proof of reserves can—and cannot—confirm.

Binance's $6.34 Billion Hack Coverage Claim, Explained
Binance says it has set aside more than $6.34 billion in company funds to cover losses from a reported $6.3 billion hack. The exchange says $5 billion of that amount is held in the same tokens that were stolen, and that those holdings will show up in its next proof-of-reserves report. Binance also says roughly $3 billion in affected assets has been frozen - but it adds that those funds are not included in the $6.34 billion figure.
Those numbers may sound reassuring, but they don't answer every question customers, counterparties, or regulators should ask. A reserve claim is not the same thing as an independently verified recovery plan. And that distinction matters: matching tokens may help replace customer balances, while frozen assets, available company funds, and a proof-of-reserves snapshot each point to different realities.
Here's what Binance said, how to think about the numbers, what a proof-of-reserves report could actually show, and where the gaps still are. The goal isn't to treat the company's statement as proof - or to wave it away. It's to give you a practical way to evaluate the claim once more evidence comes out.
What did Binance say it set aside?
Binance says it earmarked more than $6.34 billion in company funds to cover losses from the hack. A spokesperson said $5 billion of that amount was held in the exact token assets needed to replace the stolen assets. The exchange didn't say when it acquired those tokens or name the wallets holding them, citing security concerns.
The exchange says the holdings will be included in its next proof-of-reserves report. It also says it provides weekly reports on company funds to the Financial Services Regulatory Authority, the regulator of Abu Dhabi Global Market in the United Arab Emirates. Binance says that reporting requirement was already in place before the incident.
The reported theft was approximately $6.3 billion, described by a source account as the largest cryptocurrency theft on record. Blockchain intelligence firm TRM Labs said funds had been drained from Binance wallets across 10 blockchains and attributed the attack to the North Korean hacking group TraderTraitor. Binance, meanwhile, had not confirmed which tokens it still needed to acquire, when any further purchases would be completed, or how much of the stolen crypto had been recovered.
The figures are not interchangeable
To understand Binance's coverage claim, you have to keep four numbers separate:
- About $6.3 billion: the reported value of the theft.
- More than $6.34 billion: company funds Binance says it set aside to cover losses.
- $5 billion: the portion Binance says is held in matching token assets.
- About $3 billion: affected assets Binance says were frozen with help from blockchain partners; these are excluded from its company-fund total.
It doesn't follow automatically that you should add the frozen assets to the company reserve and call the result "what's available." Frozen assets may not be under Binance's control, may not be recoverable, and may not ultimately be returned. Binance explicitly excluded them from its stated reserve figure.
There's also a basic difference between saying you've set assets aside and showing that those assets are actually available, unencumbered, and sufficient. The first is about intent and holdings. The second is about evidence.
What does holding matching tokens mean?
"Matching-token" coverage means holding the same types of tokens that were stolen. If an exchange loses a quantity of a particular token, holding that token can let it replace the balance without immediately having to buy that asset on the open market. That's different from holding only an equivalent dollar value in Bitcoin, cash, or something else.
This distinction can matter when markets are stressed. If the reserve has to be converted into a less liquid token after an incident, buying could move prices or take time. If the required token is already in custody, the exchange can reduce that execution risk. It can also make accounting for customer balances more straightforward: the exchange has the token quantity needed to restore the relevant balances rather than relying on a dollar-value approximation.
But "matching" doesn't mean Binance has necessarily recovered the exact coins that were stolen. It means Binance says it holds tokens of the same kinds. It also doesn't, by itself, prove the assets are freely available for reimbursement. A serious assessment still has to consider ownership, control, custody, any encumbrances, and the value of each token at the relevant time.
Why token-by-token coverage matters
A single headline number can hide important differences between assets. A reserve worth $5 billion in total doesn't tell you whether the reserve contains the right quantities of each token affected by the theft. If one stolen token is under-covered and another is overrepresented, the dollar total might look fine while specific replacement needs still aren't met.
Token prices can also move quickly. A dollar valuation is a snapshot, not a permanent guarantee. For volatile or thinly traded assets, the gap between a reserve's stated value and what can actually be used may widen under market pressure. A useful disclosure would show quantities by token, how each token was valued, and the date and time of measurement - not just one aggregated number.
What the claim could mean for customers
If the assets are truly held by Binance, available for that purpose, and sufficient to cover affected balances, the company may be able to absorb the loss without requiring customers to eat it directly. That's an important distinction from scenarios where users' balances are reduced because the exchange can't replace what was lost.
Still, customers should separate coverage capacity from confirmed repayment. Binance's statement describes funds it says are set aside to cover losses. It doesn't automatically specify how customers will be made whole, whether certain accounts are treated differently, or when the exchange will finish the process. Those details need separate confirmation.
Can proof of reserves verify the coverage?
A proof-of-reserves report could provide useful evidence - especially if it identifies the relevant token balances and shows Binance controls the wallets holding those assets. Binance says the matching holdings will appear in its next report. That gives customers and outside analysts something concrete to evaluate, rather than leaving the claim as just a statement.
Still, proof of reserves comes with a defined scope. A report that shows balances at specific addresses doesn't necessarily establish the exchange's full financial position. If the goal is to assess whether Binance can cover losses, readers also need to know what liabilities it has, whether assets are pledged or restricted, and whether the funds are actually earmarked and available for the claimed purpose.
In practice, assets without liabilities are only half the story. A reserve report can show that an exchange controls certain crypto assets, but it doesn't automatically prove that those assets exceed customer claims or other obligations. And it doesn't automatically confirm that the assets were set aside specifically for hack losses unless the reporting scope addresses that point.
What independent verification would need to show
For this particular claim, a more informative report would help verify at least four things:
- Token quantities: what amount Binance holds for each token affected, not just the total dollar value.
- Control: evidence that Binance controls the relevant wallets or custodial accounts.
- Availability: whether the assets are unencumbered and can be used to cover losses.
- Reconciliation: how the holdings line up with the loss amounts and the liabilities they're intended to cover.
The independent-verification question is already in motion. CertiK told Cointelegraph it needed more information from Binance before it could assess whether the claimed $5 billion in matching tokens could be verified on-chain. Nansen, another blockchain analytics company, said it couldn't verify what funds Binance had available beyond its emergency fund or where the remaining coverage would come from.
That doesn't prove Binance lacks the assets. It's a limit on what those firms said they could confirm based on information available at the time. The distinction matters: an unverified claim isn't automatically false, but it shouldn't be treated as independently established.
Why earlier estimates differed
CertiK CEO Ronghui Gu previously estimated that roughly $3 billion in frozen assets, combined with Binance's approximately $1.17 billion emergency fund, could cover about 66% of the reported loss. That estimate implied a potential gap of about $2.1 billion, or roughly 1.3% of Binance's reported $165 billion in exchange reserves.
Those inputs aren't the same as Binance's later $6.34 billion claim. Gu's estimate treated the frozen assets as part of the calculation, while Binance's company-fund total excluded them. Binance's claim also includes assets beyond the $5 billion in matching tokens. Without a detailed reconciliation, the numbers shouldn't be treated as a direct, like-for-like comparison.
What should customers and regulators watch next?
The next proof-of-reserves report is an important checkpoint, but it's not the only one. Customers should look for evidence that ties the reported assets to the specific loss, not just a large reserve total. Regulators and analysts also need to see whether company reporting, customer liabilities, and the status of frozen assets are presented clearly enough to distinguish genuinely available coverage from assets that may not be usable.
A practical checklist for the next disclosure
When Binance publishes its report, look for answers to these questions:
- Are the affected tokens listed individually? A total value alone can't show whether token-by-token needs are covered.
- Are quantities and valuation dates disclosed? That helps readers understand how the aggregate figure was calculated and how sensitive it is to price changes.
- Can wallet control be checked? Security concerns may justify withholding addresses, but the report should still explain how independent verification works.
- Are restrictions or third-party claims disclosed? A token balance isn't useful loss coverage if it's pledged, locked, or otherwise unavailable.
- Are customer liabilities and the coverage amount reconciled? Readers need to see how assets map to the obligations they're intended to cover.
- Is the frozen $3 billion tracked separately? Frozen assets shouldn't be presented as recovered or available unless the disclosures support that conclusion.
Binance says the Financial Services Regulatory Authority receives weekly reports on company funds. That's relevant context, but it doesn't replace public clarity about what the next reserve report covers. Regulators can receive information that doesn't appear in public snapshots, and the existence of a reporting requirement doesn't automatically verify the specific hack-coverage claim.
Binance's other stated sources of support
Binance's founders also pointed to revenue and existing investments. Changpeng Zhao said Binance's SpaceX holdings - linked to a $500 million investment associated with Elon Musk's Twitter takeover - were worth more than $1 billion. Co-founder Yi He said Binance's annual revenue was sufficient to cover the losses and that Binance didn't need to sell its SpaceX stake. Zhao also said Gulf, Binance's partner in Thailand, offered financial support.
That context can matter, but it doesn't replace a breakdown of what assets were set aside for the incident. Revenue is income over time; a reserve is a pool of assets at a point in time. Investments may be valued on paper without being liquid or immediately available. A partner's offer also isn't the same thing as funds that have already been transferred. Each source should be assessed on its own terms - not combined as if they all translate into the same kind of coverage.
The core operational question remains simple: what assets can Binance use, in what quantities, and when? Public reporting that answers that directly would be more helpful than a list of headline valuations.
Conclusion
Binance's $6.34 billion figure is a serious coverage claim, and the stated $5 billion in matching tokens could make replacing stolen assets easier - if the holdings are available and sufficient. But those numbers don't settle the question on their own. The frozen assets are separate, outside firms said they couldn't verify the matching-token claim with the information they had at the time, and the exchange hadn't disclosed a token-by-token reconciliation.
The next report should be judged by evidence, not by the size of the headline number: token quantities, control, availability, and how the assets line up against the losses. For customers, that's the clearest way to tell the difference between a reassuring statement and a position you can actually verify.