Cc9f267dcNews eventClaimThe Bank of Russia granted self-regulatory status to the NAUFOR for digital financial asset and crypto platform operatorsAgreeDisagree
Cc9f267dcNews eventClaimCryptocurrency exchange KuCoin announced the immediate termination of all products, services, and features for users in Russia and BelarusAgreeDisagree
Cc9f267dcNews eventClaimCryptocurrency exchange MEXC announced its withdrawal from serving users in Russia and BelarusAgreeDisagree
Cc9f267dcClaimLlamaRisk reported on October 30, 2026, that the Aave position of the hacker behind the $6.3 billion Binance exploit remained overcollateralized with $59.9 million in assets against $43.8 million in debtAgreeDisagree
Cc9f267dcClaimKuCoin stated that affected customers in Russia and Belarus will receive notifications detailing deadlines and instructions to close positions and withdraw assets, while unnotified accounts require no actionAgreeDisagree
Cc9f267dcClaimDuring Aave's freeze triggered by the Binance hack starting October 29, 2026, blocked deposits and ongoing supplier withdrawals drove utilization in major stablecoin pools to 92–100%AgreeDisagree
Cc9f267dcClaimA Bitget cryptocurrency exploit in September 2026 resulted in a loss of $387 millionAgreeDisagree
Cc9f267dcClaimElliptic reported that attackers divided 18,270 stolen Bitcoin from the Binance hack on October 29, 2026 across 19 addresses, holding approximately 1,000 BTC in most addressesAgreeDisagree
Cc9f267dcClaimChainalysis reported on October 30, 2026, that attackers in the $6.3 billion Binance hack on October 29, 2026 used automated wallet loops and dense transaction networks across hundreds of interconnected addresses to circulate stolen assetsAgreeDisagree
Cc9f267dcClaimChainalysis reported that Russia received $376.3 billion in cryptocurrency transactions between July 2024 and June 2025, exceeding Britain's $273.2 billion over the same timeframeAgreeDisagree
Cc9f267dcClaimAave set a zero loan-to-value ratio on V3 and zero collateral factor on V4 for nine assets including USDT, USDC, USDT0, POL, WAVAX, sAVAX, XAUt, PAXG, and OP, following the Binance hackAgreeDisagree
Cc9f267dcClaimAttackers in the Binance breach on October 29, 2026 converted approximately 434 million USDT into 160,451 ETH on Uniswap, 1inch, and request-for-quote systems at prices 12% to 26% worse than market rates, according to EllipticAgreeDisagree
Cc9f267dcClaimKuCoin did not publicly disclose the specific sanctions measures behind its decision to exit Russia and Belarus, the number of affected user accounts, or the total trading volume involved in its exitAgreeDisagree
Cc9f267dcClaimElliptic reported that attackers in the Binance hack on October 29, 2026 converted approximately $786 million in stolen stablecoins into Ethereum and Tron before asset freezes took effectAgreeDisagree
Cc9f267dcClaimInvestigators identified a laundering pattern on the Tron blockchain where numerous wallets received exactly 1 TRX before receiving and forwarding additional funds in the $6.3 billion Binance breach on October 29, 2026AgreeDisagree
Cc9f267dcClaimAttackers in the Binance breach on October 29, 2026 exchanged approximately 234 million USDT for 638 million TRX on SunSwap and sold $48 million in RLUSD stablecoins alongside approximately 150 other stolen tokens, according to EllipticAgreeDisagree
Cc9f267dcClaimAs of October 30, 2026, none of the 18,270 stolen Bitcoin divided across 19 addresses in the Binance hack on October 29, 2026 had reached an identified exchange or trading service, according to EllipticAgreeDisagree
Cc9f267dcClaimAave's zero collateral restrictions imposed after the $6.3 billion Binance hack prevent restricted assets from backing new loans while allowing existing V3 positions to retain their health scores and liquidation thresholdsAgreeDisagree
Cc9f267dcClaimLlamaRisk reduced Slope2 borrowing-rate parameters on Aave to flatten the upper interest-rate curve and protect borrowers from escalating rates during deposits blocked by the Binance hackAgreeDisagree
Cc9f267dcClaimBinance promised to cover user losses from the Binance hack using its SAFU reserve and corporate funds, according to its October 30, 2026 statementAgreeDisagree