Coinbase confirmed it was not affected by the $6.34 billion hot wallet hack at Binance and disclosed that 99% of its customer assets are held in cold storage, addressing market concerns over centralized exchange security.
According to a crypto.news report, Coinbase has confirmed that it was not affected by the $6.34 billion hot wallet hack at Binance and disclosed that 99% of its customer assets are held in cold storage. The incident is regarded by the market as a major security event, and Coinbase's public statement, which covers both customer asset segregation and its cold storage ratio, directly responds to market concerns about the security of centralized exchanges. As of the publication of the report, the confirmed amount involved in the incident was $6.34 billion, and Coinbase's disclosure focused on its own lack of exposure and on how customer assets are held. The report did not specify a publication time.
The incident involves two centralized trading platforms: a hack of Binance's hot wallet involving $6.34 billion, and Coinbase's confirmation regarding the impact of the incident, together with its disclosure of customer asset segregation and its cold storage ratio. The two key figures are $6.34 billion and 99%. The former is the amount involved in the Binance incident, while the latter is the share of customer assets that Coinbase says is held in cold storage. Public information confirms that Coinbase was not affected by the incident and that 99% of customer assets are held in cold storage. However, the original report did not provide Coinbase's total customer assets, how the remaining assets are held, or the specific legal or technical structure of its asset segregation, nor did it provide the technical path, scope of impact or handling progress of the Binance incident. Judgments about the impact of the incident should therefore remain at the level of confirmed facts, and Coinbase's disclosure should not be extrapolated to other platforms.
The disclosure comes against a backdrop of market concerns about the security of centralized exchanges. Given the $6.34 billion involved, the Binance hot wallet incident has high market impact and user attention. After major hacking incidents, whether customer assets are segregated and what proportion is held in cold storage become direct ways for outsiders to observe a platform's security arrangements. Coinbase responded to market concerns with two pieces of information, namely that it was unaffected and that 99% of customer assets are in cold storage, pointing to two levels: first, separating itself from the risk of the Binance hot wallet incident; second, providing the proportion of customer assets in storage. Based on the information disclosed, this response is a public statement at the platform level and does not constitute a conclusion about the security of the industry as a whole. The scope of public information is limited to Coinbase alone and does not include relevant data from other exchanges.
In terms of how the disclosure is framed, Coinbase's response centers on two sets of information. The first is risk separation: it explicitly states that it was not affected by Binance's $6.34 billion hot wallet hack. The second is asset storage: 99% of customer assets are held in cold storage, with customer asset segregation also mentioned. The original report did not further explain the institutional arrangements to which "customer asset segregation" refers, nor did it explain the statistical basis for the cold storage ratio or how the remaining assets are held. Therefore, what can currently be verified is only the data publicly provided by Coinbase, not its underlying custody mechanism.
In security incidents at centralized exchanges, customer asset segregation and cold storage ratios attract attention because they form a set of indicators through which platforms publicly explain their customer asset arrangements. By mentioning both customer asset segregation and the cold storage ratio, Coinbase allows outsiders to identify two levels of information at the factual level: first, whether the platform distinguishes customer assets from its own operational risks; second, what proportion of customer assets is held in cold storage. The public information explicitly gives the 99% figure, but the original report did not elaborate on the institutional arrangements for asset segregation, the specific operation of cold storage or the storage status of the remaining 1%. What can be confirmed is the content of Coinbase's disclosure itself; the custody structure or security mechanisms not provided in the original report cannot be added. The response provides verifiable data at the platform level, not an overall conclusion about the security level of centralized exchanges.
Regarding the incident, the original report did not provide technical details of the Binance incident, the scope of impact, or asset recovery and handling arrangements. Beyond Coinbase's statements that it was unaffected and that 99% of customer assets are in cold storage, the original report also did not provide the specific arrangements for customer asset segregation, the storage status of the remaining 1% of assets, or whether further statements will be made. Because of these gaps, outsiders can currently only compare the public statements of the two platforms and cannot obtain a complete picture of the incident.
Three areas warrant follow-up: whether Binance provides more information on its subsequent handling of the incident; whether Coinbase provides additional disclosure on the calculation basis for customer asset segregation and the cold storage ratio; and whether information disclosure for security incidents at centralized exchanges will develop clearer public standards. These points are all based on disclosed facts and do not constitute judgments about the outcome of the incident or market trends. This information comes from a crypto.news report, which did not specify a publication time; apart from that report, this material did not provide information from other official or authoritative channels.
