Key Takeaways
- Binance has fully covered user assets affected by its $6.3 billion October hack.
- The exchange has funded replacements from three company sources: SAFU, futures insurance reserves, and its corporate treasury.
- The completion of asset coverage is a positive step for Binance, but the exchange still needs to generate the proof and provide an asset-by-asset breakdown of the final purchases.
Binance Announces Completion of Asset Coverage
Binance has announced that it has fully covered user assets affected by its $6.3 billion October hack and published a new Proof of Reserves snapshot, with the accompanying zero-knowledge proof still to come.
The coverage of assets affected by the October 29 security incident is complete, according to Binance. Earlier replacement funding included the Secure Asset Fund for Users (SAFU), futures insurance reserves, and the exchange’s corporate treasury.
Background of the Hack
The $6.3 billion hack occurred on October 29, resulting in significant losses for Binance users. The exchange quickly responded by announcing that it would cover the losses using its own funds.
Proof of Reserves Snapshot
The latest snapshot precedes the cryptographic proof needed for users to run independent checks. Previous reserve disclosures and withdrawal figures cover different dates and types of exchange activity.
Binance said in its November 12 announcement that customers would be able to independently verify backing of at least 1:1 once the proof was generated. Its message did not give a completion time for that step or an asset-by-asset breakdown of the final purchases.
“Binance has completed coverage of assets impacted in the security incident,” the exchange wrote, thanking customers for their patience.
Funding Sources
Binance funded replacements from three company sources: the Secure Asset Fund for Users, part of its Futures Insurance Funds, and its corporate treasury.
It had set aside more than $6.34 billion in company funds, with replacement coverage then reaching 90%. The exchange described its futures insurance reserves as company funds, separate from customer assets.
- The Secure Asset Fund for Users (SAFU) was used to restore the emergency reserve to approximately $1 billion.
- Futures insurance reserves were used to cover a portion of the losses.
- The corporate treasury was also used to fund replacements.
Reserve Proof
Binance’s latest reserve proof is still pending. The exchange’s earlier verification rounds followed the same sequence.
As previously reported, the exchange completed reserve verification on November 2 for a snapshot taken at 00:00 UTC on October 31. That round covered ten cryptocurrencies, including Bitcoin, Ethereum, USDT, BNB, Solana, and XRP.
A subsequent snapshot, taken at 00:00 UTC on November 4, expanded coverage to 44 tokens. Binance estimated 50–60 hours to generate its accompanying proof, citing the computing workload.
Methodology
On its reserves page, Binance explains that a Merkle tree lets customers check whether their balances appear in the reported account totals. Its zero-knowledge system checks the balance calculations without publicly revealing individual users’ holdings.
Customers can find their record ID and Merkle leaf through the verification section of their accounts. Selecting a verification date displays the assets covered and the account balances recorded at that snapshot, according to the exchange’s instructions.
Withdrawal Figures
The October disclosures provide a dated comparison. Binance’s reported user USDT holdings fell 7.95% between October 1 and October 31 to 29.48 billion tokens.
Ethereum holdings dropped 3.80% to 3.65 million ETH, while Bitcoin balances rose 0.52% to 692,187 BTC. USDT’s reported reserve coverage moved from 103.88% to 100%, and Bitcoin’s stood at 100.04%.
The figures predate the reopening of withdrawals on November 1 and do not measure departures after customers regained access.
Implications for Readers in India
The Binance hack and subsequent recovery have significant implications for readers in India, who are increasingly interested in cryptocurrency trading. The incident highlights the importance of choosing a reputable exchange and understanding the risks involved in cryptocurrency trading.
Expert Perspective
Experts in the field of cryptocurrency and cybersecurity have praised Binance for its swift response to the hack and its commitment to covering user losses. However, they also emphasize the need for exchanges to prioritize security and implement robust measures to prevent such incidents in the future.
What to Watch Next
As Binance continues to work on generating the accompanying zero-knowledge proof, users can expect further updates on the status of the reserve proof. Additionally, the exchange may provide more information on the asset-by-asset breakdown of the final purchases and the completion of the replenishment of the Secure Asset Fund for Users.
Conclusion
Binance has announced that it has fully covered user assets affected by its $6.3 billion October hack, with a new Proof of Reserves snapshot pending. The exchange has funded replacements from three company sources and is working to generate the accompanying zero-knowledge proof.
The completion of asset coverage is a positive step for Binance, but the exchange still needs to generate the proof and provide an asset-by-asset breakdown of the final purchases.
In the coming weeks and months, it will be essential for Binance to maintain transparency and provide regular updates on its progress. The exchange must also prioritize security and implement measures to prevent similar incidents in the future.
For readers in India, the Binance hack serves as a reminder of the importance of choosing a reputable exchange and understanding the risks involved in cryptocurrency trading. As the cryptocurrency market continues to evolve, it is crucial for users to stay informed and take necessary precautions to protect their assets.
Timeline of Events
Here is a timeline of the key events surrounding the Binance hack:
- October 29: The $6.3 billion hack occurs, resulting in significant losses for Binance users.
- October 31: Binance announces that it will cover the losses using its own funds.
- November 2: Binance completes reserve verification for a snapshot taken at 00:00 UTC on October 31.
- November 4: Binance expands coverage to 44 tokens with a subsequent snapshot.
- November 12: Binance announces that it has fully covered user assets affected by the hack.
Key Takeaways
The Binance hack and subsequent recovery have several key takeaways for users and the broader cryptocurrency community:
- The importance of choosing a reputable exchange and understanding the risks involved in cryptocurrency trading.
- The need for exchanges to prioritize security and implement robust measures to prevent similar incidents in the future.
- The value of transparency and regular updates in maintaining user trust and confidence.
Frequently Asked Questions
What happened to Binance?
Binance was hacked on October 29, resulting in significant losses for users. The exchange has since announced that it has fully covered user assets affected by the hack.
How did Binance cover the losses?
Binance funded replacements from three company sources: the Secure Asset Fund for Users (SAFU), futures insurance reserves, and its corporate treasury.
What is the current status of the reserve proof?
The reserve proof is still pending. Binance is working to generate the accompanying zero-knowledge proof, which will allow users to independently verify the backing of their assets.
