Binance has set aside more than $6.34 billion in company funds to cover losses from the hack, the exchange said. The company said $5 billion of those funds were already held in the same tokens affected by the attack.
Cointelegraph reported that Binance said it had set aside more than $6.34 billion in company funds to cover losses, of which $5 billion was already held in the same tokens affected by the attack.
This line is our short summary of the quote below. The quote is the evidence.
Figures from this statement
- Set aside: $6,340,000,000.00 as of
Other statements from the same source
Cointelegraph reported that Blockaid said it had identified roughly $3.3 billion in suspicious transfers involving Binance-linked wallets across Ethereum, Arbitrum and Avalanche.
Blockchain security firm Blockaid said its team had identified roughly $3.3 billion in suspicious transfers involving Binance-linked wallets across Ethereum, Arbitrum and Avalanche.
Cointelegraph reported that Circle CEO Jeremy Allaire said Circle had frozen more than $800 million in USDC in coordination with law enforcement.
Circle CEO Jeremy Allaire said the company had frozen more than $800 million in USDC in coordination with law enforcement and would continue supporting the investigation.
Cointelegraph reported that Richard Teng said the attacker used a self-destruct mechanism to destroy tools and traces, complicating the investigation.
Teng also disclosed that the attacker used a “self-destruct mechanism” to destroy tools and traces during the breach, complicating the investigation.
Cointelegraph reported that co-CEO Richard Teng said Binance was aiming to resume withdrawals within 40 hours and publish a full proof-of-reserves report by Monday.
Binance is aiming to resume withdrawals within 40 hours and publish a full proof-of-reserves report by Monday, co-CEO Richard Teng [said]
Cointelegraph reported that co-CEO Richard Teng said the attacker used an EIP-7702 delegation to gain execution authority over a hot wallet, and that the delegation did not pass through Binance's normal approval controls.
The attacker used an EIP-7702 delegation to gain execution authority over a hot wallet, Teng said. That delegation “did not pass through our normal approval controls.”