Bitget CEO Request for THORChain to refuse service to attacker addresses
BIBIBI
AT A GLANCE
Bitget CEO Gracy Chen requested that THORChain refuse to provide services to attacker addresses associated with the platform security incident.
Article
Bitget CEO：Formal request for THORChain to refuse service to attacker addresses
BlockBeats news,September 26，Bitget CEO Gracy Chen stated in a post that attacker addresses associated with the platform security incident have been made public and are being continuously tracked. Bitget is now formally requesting that THORChain refuse to provide services to these addresses.
Gracy Chen stated: “Decentralization is a design principle and should not become a shield for facilitating the movement of known stolen funds.” She also said that the entire crypto industry is watching how THORChain handles the matter.
Original link https://m.theblockbeats.info/flash/369133
Key points
01
According to BlockBeats news,September 26，Bitget CEO Gracy Chen issued a statement on the matter.
02
Gracy Chen stated that attacker addresses associated with the platform security incident have been made public and are being continuously tracked.
03
Bitget formally requested that THORChain refuse to provide services to these addresses.
04
Gracy Chen said that decentralization should not become a shield for facilitating the movement of known stolen funds.
05
Gracy Chen said that the entire crypto industry is watching how THORChain handles the matter.
AI-assisted interpretation
The following is analysis, separate from reported facts. Verify important claims independently.
The core of this news is that Bitget said attacker addresses associated with its security incident have been made public and are being tracked, and requested that THORChain stop providing services to these addresses. This is a public request made by Bitget; the original text does not state whether THORChain has accepted or implemented it.
Why it matters to readers
The incident concerns whether addresses holding stolen funds can continue using the relevant services, as well as the dispute between the principle of decentralization and preventing the movement of known stolen funds. How THORChain responds could affect external perceptions of its governance and security response practices.
Beginners should distinguish between “Bitget made a request” and “THORChain has already taken action”: the current evidence clearly establishes only the former. Do not conclude on this basis that the relevant addresses have been blocked, and do not make asset-trading decisions based solely on this news.
Risks and unknowns
The original text does not provide a list of attacker addresses.
The original text does not specify the details of the security incident, the amount of losses, or the flow of funds.
The original text does not provide a response from THORChain.
It cannot be confirmed whether THORChain will refuse service or whether this request has already been executed.
The message was relayed by BlockBeats; the specific content of the attached original-text link is not elaborated in the evidence.
Related Developments
Loading event timeline…
Related concepts
Attacker addresses
This term is not in the glossary yet. Browse related concepts in the glossary.
