Futures
Access hundreds of perpetual contracts
CFD
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Pre-IPOs
Unlock full access to global stock IPOs
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
Promotions
AI
Gate AI
Your all-in-one conversational AI partner
Gate AI Bot
Use Gate AI directly in your social App
GateClaw
Gate Blue Lobster, ready to go
Gate for AI Agent
AI infrastructure, Gate MCP, Skills, and CLI
Gate Skills Hub
10K+ Skills
From office tasks to trading, the all-in-one skill hub makes AI even more useful.
GateRouter
Smartly choose from 40+ AI models, with 0% extra fees
Aave resumes WETH lending; the transfer of 30,000 ETH raises controversy involving a North Korean hacker
Techub News reports that, according to crypto.news, Aave has restored the WETH lending function affected by the Kelp DAO April vulnerability incident. Previously, the attacker exploited a LayerZero bridge vulnerability, using unsupported rsETH as collateral to borrow a large amount of WETH. Currently, the transfer of frozen assets totaling 30,765 Ethereum (approximately $71 million) has been approved by the court, but related legal disputes are ongoing.
A judge at the Manhattan Federal Court has approved the transfer of funds from the Arbitrum Security Council wallet to an address controlled by Aave LLC. A law firm representing victims’ families of terrorism claims that these assets are connected to North Korea’s Lazarus Group, but the court has not officially confirmed this attribution.
Aave founder Stani Kulechov stated that recovered assets should belong to the affected users rather than the attacker.