NEAR Defends Blocking Bitget Hack Funds, Says Permissionless ‘Doesn’t Mean Neutral’
After the September 24 Bitget hack, several cross-chain services and other protocols moved to block or freeze related transfers, while some attempted transfers still slipped through or landed on the wrong network. Bitget later reopened withdrawals, and its reported asset balance remained above $6.7 billion after the incident.
What this rests on
What it means
Each sentence links inside to the piece that supports it.
Users moving assets across NEAR Intents and Chainflip are seeing more transfers stopped, frozen, or returned than before, and that changes what is immediately reachable through those routes. Bitget users also saw withdrawals reopen after the hack, while the exchange said it still held more than $6.7 billion in assets after the incident.
In practice, cross-chain swap routes are now being used with more active screening than before, and some flows linked to the hack have been blocked before completion. That does not change the fact that some funds still moved through the swap system and some transfers still landed on the wrong network or in the wrong channel.
Market reaction
How the story was built
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.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 2 months ago | Nesa incident | $50M |
| 1.6 years ago | Infini incident | $50M |
| 2.0 years ago | Radiant Capital incident | $50M |
| 5.9 years ago | Saffron Finance · Contract vulnerability incident | $50M |
| 8.7 years ago | Blockchain.info · Phishing attack incident | $50M |
4197 incidents stored · 125 were as large as this one or larger ($50M)
What could happen next
What the prediction markets currently price as likely. This is context, not a forecast of ours: there is money on it, and that is all we show.