News
Stay up to date on the latest crypto trends with our expert, in-depth coverage.

Bitcoin miner CleanSpark's Q2 losses swell after losing $224 million on BTC holdings
The Block·2026/05/11 21:06
STRC Linked TVL on Pendle Reaches $318 Million as Yield Strategies Expand
BlockchainReporter·2026/05/11 21:00
Copper price shrugs off Middle East uncertainty to near record high
Mining.com·2026/05/11 20:45
MID hold
TradingView·2026/05/11 20:45
Bitcoin eyes $92,000 as MVRV cross signals new rally
Cointurk·2026/05/11 20:42
Payward charter targets federal crypto bank status
Crypto.News·2026/05/11 20:42
Silver Price Analysis: Tests $86.00 as rally gains momentum
FXStreet·2026/05/11 20:39
Gold Candle acquires Pan American Silver’s Larder property in the Abitibi
Mining.com·2026/05/11 20:30
Tokenized Gold Trading Volume Explodes as RWA Market Tops $19 Billion
Coinpedia·2026/05/11 20:30
CLARITY Act Could Hand Crypto Control to Wall Street – Warns Mark Yusko
Coinpedia·2026/05/11 20:30
Flash
14:35
Indian Enforcement Directorate raids multiple companies in BangaloreThe Indian Enforcement Directorate conducted raids on several companies in Bangalore, involving crypto-related transfers exceeding 260 million US dollars. (Cointelegraph)
14:22
Hyperliquid completes USDH-denominated market settlement on HyperCoreHyperliquid announced that markets denominated in USDH on HyperCore have completed settlement. Users need to handle their remaining USDH assets, including converting USDH to USDC on the HyperCore spot order book and HyperEVM, withdrawing USDH from Borrow/Lend products, and repaying borrowed USDH by purchasing the USDH/USDC trading pair.
14:03
SlowMist’s Cosine Questions the LABUBU “Theft” Incident on BNB Chain: Key Parameters Appear to Have Been Abnormally ModifiedAccording to Odaily, SlowMist founder Cosine analyzed that there are suspicious aspects to the approximately $1.1 million capital loss incident that occurred in the OLPC / LABUBU liquidity pool on BNB Chain. The theft was caused by a severe imbalance in the OLPC/LABUBU trading pair, and the reason for the imbalance was an "exploit" in OLPC that was taken advantage of. In the _update function, under certain conditions, it was possible to burn OLPC in the amount of value * decimalsValue. Normally, decimalsValue is 1, but about 46 days before the attack, the owner changed it to an extremely large value: 7326680472586200649. A few days later, the OLPC owner renounced ownership, making the owner address the zero address. Today, the attacker took advantage of this excessive decimalsValue to trigger a Pair reserve burn, allowing them to obtain a large amount of LABUBU with a small amount of OLPC. The attacker ultimately exchanged 1.115 million USDT at a low cost. The suspicious point lies in the setting of decimalsValue—why would the OLPC owner set it to such a massive value?