Bitget-Linked Wallet Moves $6.3 Million Into Bitcoin After Reported THORChain Freeze Rejection
Key Takeaways
- •Reports circulating in crypto communities describe a wallet labeled as Bitget-linked moving roughly $6.3 million in assets into Bitcoin.
- •An alleged request to freeze the funds through the decentralized cross-chain protocol THORChain was reportedly rejected before the transfer occurred.
- •The wallet address, transaction hash, and the identity of the wallet's controller have not been independently verified, leaving the core claims unsubstantiated.
- •THORChain's architecture, in which pooled assets are secured by independent node operators, provides no central administrator with the power to halt transfers on request.
- •The report arrives after Bitget restored Bitcoin withdrawals following a September 24 security incident at the exchange.

A wallet reportedly linked to cryptocurrency exchange Bitget moved an estimated $6.3 million into Bitcoin after an alleged request to freeze the funds through the cross-chain protocol THORChain was rejected, according to accounts circulating in crypto communities. The sequence of events remains unconfirmed: the wallet address, the transaction hash, and the identity of whoever controls the wallet have not been independently verified.
What Is Reported About the Transfer
Reports describe a wallet labeled as Bitget-linked moving roughly $6.3 million worth of assets into Bitcoin, with the timing said to follow a failed attempt to block the funds from moving.
The meaning of the label is central to the story. A “Bitget-linked” tag does not by itself prove that Bitget owns or authorized the movement. On-chain labels are frequently applied by blockchain analytics firms based on historical transaction patterns rather than confirmed ownership. No transaction hash, block explorer link, or official statement has been included in the reporting available at the time of writing to independently verify the transfer.
Without a verified transaction record on a Bitcoin block explorer such as Mempool.space, both the $6.3 million figure and the wallet's connection to Bitget remain unconfirmed claims. The story is still developing, and readers should treat all specific figures as reported rather than established.
One piece of context is relevant: Bitget restored Bitcoin withdrawals following a September 24 security incident, which adds background to reports of unusual wallet activity linked to the exchange during this period.
The Reported THORChain Freeze Request
The reported sequence includes a claim that someone asked THORChain to freeze the funds before they moved. THORChain is a decentralized cross-chain liquidity protocol, meaning it allows users to swap assets across different blockchains without a central authority holding the funds. Because the protocol is designed to operate without a central gatekeeper, freeze requests of this kind face significant practical and structural obstacles. Its pooled assets are secured collectively by the independent node operators who run the network, so there is no single administrator with the power to halt a transfer on request. That architecture marks a sharp contrast with centralized venues, where exchanges and stablecoin issuers can block transfers on accounts or addresses under their control — a mechanism that has featured in past industry security incidents.
According to reports linking the two events, the freeze request was rejected. No statement from THORChain node operators, no governance vote, and no official protocol communication has been cited to confirm the nature or the outcome of that request.
It is not confirmed why the request was rejected, who made it, or through what mechanism it was submitted. Interpreting the rejection as proof of any specific intent or wrongdoing on anyone's part would go beyond what the available evidence supports.
Open Questions for Crypto Holders
The reported events leave several questions unanswered: Who controls the wallet? Was the transfer connected to the September 24 security incident at Bitget? And what actually happened with the freeze request?
For cryptocurrency holders, the reported story underscores two points. First, on-chain movements are visible to everyone, but interpreting them correctly requires verified data rather than labels alone — a wallet tagged as exchange-linked by a third-party service is not the same as a confirmed exchange wallet. Second, decentralized protocols like THORChain are built specifically to resist centralized intervention, including freeze requests. That resilience is a design feature rather than a flaw, but it means disputes over funds in such systems play out differently than in traditional finance.
As the story develops, the key items to watch are an independently verified transaction ID on a Bitcoin block explorer, a statement from Bitget clarifying whether the wallet is affiliated with the exchange, and any on-chain record of the reported THORChain interaction. Until those pieces are confirmed, the reported $6.3 million transfer and the freeze rejection remain claims that have not been independently substantiated.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.