THORChain co-founder says acting against Bitget hacker was possible but difficult
- Published
- Updated
THORChain’s validator structure and trading controls left no quick wallet-specific shutdown for the Bitget-linked funds, and some actions needed two-thirds validator approval. Chad Barraford later said he would bring the idea of refunding some fee income tied to the stolen funds to the protocol’s Treasury.
Key claims & sources
What it means
Users and traders on THORChain are the ones most likely to notice the validator limits first, because the network cannot use a pause aimed at just one wallet and some responses need two-thirds approval. That means the practical window for acting on the Bitget-linked funds is shaped by the time it takes validators to coordinate, not by a single operator’s decision.
In practice, the network’s normal routing and swap activity can keep operating unless a broader pause or a high-threshold vote is reached. The later Treasury discussion adds a separate path: part of the developer fund’s income from those swaps could be sent back, but that is only a matter Barraford said he would bring up.
Market reaction i
Bitget Token barely moved in the 4 hours after the first headline, after a flat 2 hours before.
47 prices, one every 30 minutes
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| 2 days ago | B18 TimeBank · Unknown incident | $404.5k |
| 3 days ago | MORE Markets · Unknown incident | $308k |
| 3 days ago | Lighter incident | $10.4M |
| 3 days ago | Optimizely (OPTIMJACK) · Supply Chain Attack incident | $2.3k |
| 4 days ago | Luxor Commander · Unknown incident | no figure in dollars |
4332 incidents stored