Bitget's operations are gradually recovering after the hacking incident, and the size of its protection fund has risen to $309 million. This is the latest development in the platform's handling of risks related to the security incident, and an important point for users to watch regarding fund safety and compensation arrangements. Previously disclosed public information showed that the incident involved $388 million in user losses. Other reports on the same incident have been merged and deduplicated, with current information focused on three aspects: operational recovery, protection fund coverage, and compensation progress.
From the sequence of events, the hacking incident occurred and user losses were disclosed first, followed by the latest developments of gradual operational recovery and an increase in the protection fund size. The current information does not change the previously stated loss amount, nor does it provide a final compensation conclusion. The above user loss figure is an earlier disclosed fact, while the protection fund size is the latest data. Whether there will be further updates remains to be seen.
In terms of key data, the publicly disclosed scale of user losses in this incident is $388 million. This amount had already been confirmed in prior information and continues to stand as a key fact in the latest developments. In contrast, the newly disclosed protection fund size is $309 million. The two amounts correspond respectively to the user losses caused by the incident and the latest size of the platform's protection fund. At present, there is no information explaining the specific coverage relationship between the two, the compensation ratio, or the funding gap. Public information also does not explain the source of the protection fund's growth, its composition, or whether it includes platform proprietary funds, insurance, or other external funds.
Regarding operational recovery, public information only shows that Bitget's operations are gradually recovering, without mentioning the specific scope, timing, or business lines involved. This development, together with the adjustment in the protection fund size, forms two current priorities in risk handling, indicating that the platform is advancing business recovery and fund protection in parallel. However, 'gradual recovery' remains a qualitative description, and there is no further explanation as to whether users can normally use the relevant businesses or whether some functions remain restricted.
Fund safety and compensation progress have drawn significant user attention in this incident. Public information does not provide the completion ratio of compensation, a specific timetable, or a coverage list, so it cannot be confirmed whether compensation has been completed, nor can the subsequent funding gap be calculated. What can be confirmed is that the protection fund size has risen and operations are gradually recovering. Apart from that, specific arrangements involving user funds have not been made public, and the market still needs to wait for further disclosure from the platform.
Other reports on the same incident have been merged and deduplicated, and the relevant information is presented in a consolidated manner in this update after deduplication. The information after merging and deduplication is concentrated in three dimensions: operational recovery, protection fund coverage, and compensation progress. It does not add compensation details or final handling results. This means that the publicly available information currently available remains limited, with the main facts concentrated in four areas: the occurrence of the incident, the loss amount, the fund size, and the recovery status.
Going forward, areas to watch include whether the protection fund size continues to be adjusted, whether compensation arrangements are further disclosed, whether operational recovery remains stable, and updates on information related to user fund safety. The public materials do not provide a specific timetable or explain the final coverage relationship between the protection fund and user losses, so observations should currently be based on disclosed facts. This article is based only on the provided materials for factual review and does not constitute any investment advice.
