News
Stay up to date on the latest crypto trends with our expert, in-depth coverage.
Banks Ramp Up Stablecoin Lobbying Before May 14 Senate Vote
Bitcoininfonews·2026/05/10 19:18
Black Swan Capitalist States What Will Soon Trigger XRP Repricing
TimesTabloid·2026/05/10 19:09
XRP Rich List Update: Fresh Amount You Need to Join Top 10% Holders
TimesTabloid·2026/05/10 19:06
Colombia urges Glencore to discuss Cerrejon coal mine closure with local authorities
Mining.com·2026/05/10 19:06
Trump Revives Fort Knox Audit Push, Wants to Knock on the Vault Door
BeInCrypto·2026/05/10 18:54
Cardano struggles at $0.27 as investors watch $0.30 level
Cointurk·2026/05/10 18:51
CoreWeave Inc. (CRWV) Daily Swing Trading Plan
TradingView·2026/05/10 18:45
Trading Plan (Daily Time Frame)
TradingView·2026/05/10 18:45
SOUN - US Long
TradingView·2026/05/10 18:45
Flash
15:46
After closing its position, whale pension-usdt.eth opens a new 3x leveraged ETH short.Whale pension-usdt.eth, after closing its Ethereum short position, has once again opened a 3x leveraged ETH short, holding 871.3249 ETH, valued at approximately 1.5 million US dollars.
15:44
In the past 24 hours, the entire network has seen $180 million in liquidations, with the majority being from a significant short position liquidation.BlockBeats News, June 20th, according to Coinglass data, the total liquidation in the past 24 hours was $180 million, with long liquidations amounting to $57.18 million and short liquidations amounting to $123 million.
15:43
Axelar Network responds to security incident, vulnerability originated from third-party token contractAxelar Network stated in its announcement that neither Axelar Network nor the IBC protocol was attacked, and the affected token smart contract was not developed, deployed, or maintained by Axelar Network. The exploited contract was a forked version of CW20-ICS20, where the developers removed two core security checks, resulting in an "infinite minting" vulnerability. This fork altered the original contract's trust model and had not undergone a security audit. Axelar Network emphasized that this incident was not due to any inherent logic flaws or problems with the IBC protocol, but instead stemmed from security risks introduced by third-party contract modifications.