Futures
Access hundreds of perpetual contracts
TradFi
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 30+ AI models, with 0% extra fees
I just learned about the Dango incident — it sounds scary at first glance, but in reality, everything ended well. It turns out that some hacker found a vulnerability in the insurance fund logic and was able to withdraw about 410,000 USDC. But the most interesting part is that the remaining 1.49 million stayed in place thanks to bridge limits, and users were not harmed at all.
What’s next? The hacker returned all the money and even received a bug bounty reward. The team called him a white hat, and now everyone is saying it was just an ordinary pentest that went sideways. No users lost anything — all funds were protected, and compensation is guaranteed.
Currently, Dango is working on additional security measures to prevent this from happening again. The protocol will soon be back online, although the rewards program has been temporarily postponed. Honestly, when you see stories like this, it’s nice to know that at least this time no one was hurt and the team reacted quickly. I wonder how many more similar vulnerabilities are waiting for their moment in other protocols?