CoinBatmi

News · Crypto, Auto-Generated

THORChain rejects Bitget's demand to block hacker addresses

By CoinBatmi Newsroom · · 4 min read

Bitget froze XRP withdrawals as 27 million stolen tokens moved. THORChain is pushing back on the exchange's demand that it block the same hacker addresses.

An exchange asked a decentralized trading network to shut the doors on addresses holding stolen money. The network said no.

The Defiant reported that THORChain is pushing back on Bitget's demand that it block those hacker addresses, and the refusal landed in the same stretch as CryptoSlate's report that Bitget froze XRP withdrawals while 27 million stolen tokens moved.

Put those two reports next to each other and you get one problem seen from both ends. Bitget can lock an account because Bitget holds the coins. THORChain says no because it doesn't hold them the same way, and that difference is the whole story.

Freezing an account and filtering a pool are two different jobs

A typical exchange account is a line in a ledger. The exchange owns the wallets, decides who can withdraw, and can stop a withdrawal mid-flight. That's what a freeze is, and it works instantly because the exchange is the counterparty.

THORChain doesn't run on accounts. Swaps go through liquidity pools, and the assets sit in vaults controlled by the network's own node operators rather than by a company's balance sheet.

A "freeze" there would mean the network agreeing to refuse certain addresses as a matter of policy, which is a much heavier thing to ask of a system built to route value without an operator in the middle. That's why Bitget's request landed where it did. A CEX freeze covers the exchange's own holdings.

It says nothing about an address that has already moved value onto a pool.

27 million tokens moved while withdrawals stopped

The timing is the part worth sitting with. CryptoSlate reported that Bitgent froze XRP withdrawals as 27 million stolen tokens moved. Both halves of that sentence describe the same hours from two directions: coins leaving one set of hands, coins coming off the platform for everyone else.

Nobody quoted a recovery figure. Nobody said the tokens were traced to a specific wallet. What is on the record is a freeze, a number, and a refusal from the network that some of that value may have crossed.

If THORChain holds the route those tokens took, its no is the part that keeps the trail cold.

$75 million in a week is the number to beat

The flows tell a different story this week. CoinPotato reported that XRP ETFs attracted $75 million in a week, and that Solana fund products hit a new 2026 high in the same window.

That's the mechanism of an ETF in plain terms: money goes in through a fund, the fund buys the coin, and buying shows up as demand.

Seventy-five million dollars of that in seven days is not a rounding error in a market this size, and Solana setting a 2026 high alongside it says the appetite wasn't limited to one token. A freeze on withdrawals at a single exchange and $75 million of inflows through listed funds are the same seven days.

The freeze limits who can pull coins out of one platform. The ETF money is new demand that doesn't care about the platform at all.

Brandt is trading the chart

Peter Brandt, the longtime bitcoin analyst, said XRP's charts alone give him reason to make a bet, news.bitcoin.com reported. His case is a chart read. He didn't need a story about adoption, revenue, or regulation to justify the position; the price structure was the argument.

That's a different kind of statement from the freeze dispute, and it moves on a different clock. One of them is about whether a protocol will block an address. The other is about a shape in a chart.

Both are about the same coin this week. So the figure that settles the ETF half is simple. CoinPotato's $75 million is a weekly total, and it resets every seven days.

If next week lands under it, the buying was an event. If it holds or beats it, the inflows were a bid that arrived early.

Research and market information only — not financial advice.