The case puts alleged proceeds from a major crypto hack alongside a striking claim about how some of the funds were spent.
The dispute tests where permissionless access ends when stolen funds move through a protocol, with the recent vault attack underscoring the security stakes.
The cross-chain path converts stolen assets into BTC, making the trail harder to follow as attribution for the roughly $350M hack remains under investigation.
The rejected deposit was refunded to the sender rather than frozen, blocking this route without securing the funds themselves.
The case puts a practical boundary around “permissionless”: NEAR Intents can screen swaps, but the rules for releasing held funds and correcting false flags remain unclear.
Apple said the flaw may have been exploited in sophisticated attacks against specific targets, putting users on older iOS versions in focus.
The reported blocks highlight how transaction-level safeguards can limit the movement of stolen funds, though they do not establish that the money was recovered.
The reserve drop exceeds Bitget's reported customer withdrawals, while investigators say stolen funds are moving through bridges, cross-chain protocols and mixers.
The intervention shows how cross-chain risk controls can target known stolen funds while keeping a permissionless protocol open.
The reopening is a first step, not proof that customer transfers are completing. ETH, USDT and other services remain on a phased schedule.
The response adds approval layers and resets credentials, but the affected third-party security functions will remain disabled until remediation is complete.
Two small test transfers triggered no alerts before the attacker exploited a third-party security product's zero-day to issue fraudulent withdrawals.
Past post-halving recoveries offer a scenario, not a forecast; ETF flows, interest rates and AI investment add variables absent from earlier cycles.
The breach shifts scrutiny from initial access to incident response: Bitget’s own systems flagged unauthorized transfers before the largest losses began.
The alleged laundering trail overlaps with funds from a separate Kelp DAO exploit, while ZachXBT says more data is forthcoming.
The upgrade gives users more control over bridge verification, but Chainlink's separate Risk Management Network no longer provides a second check.
The dispute pits Bitget’s effort to recover stolen funds against THORChain’s refusal to selectively block addresses, while cross-chain swaps keep the attacker’s activity visible.
The exchange says the pause was a security measure, not a sign of insufficient user assets, and that losses were covered by its Protection Fund.
The CEO said private keys were not compromised, but attackers reached wallet backends and bypassed withdrawal risk controls.
The restart restores access for users, but the $388 million incident keeps exchange security and confidence in centralized platforms in focus.
Crypto News
WuBlockchain
CoinDesk
CoinTelegraph
CryptoSlate
TheBlock
WatcherGuru