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
Recently, many people have been discussing liquidation of leverage, but often it's not that your direction is wrong; it's that the oracle price feed is lagging behind. The on-chain matching/DEX prices have already jumped, but the oracle is still using the previous round of data, and the risk control module calculates margin based on the old price: it doesn't alert you when you need to top up, but it liquidates you first when it should not, or vice versa. Someone arbitrages and drains the pool before you realize. To put it simply, during liquidation, what matters is the "price recognized by others." So now, before opening a position, I check what oracle the project uses, its update frequency, abnormal fallback rules, and whether the team has permission to manually change the feed source. On Layer 2, they compare TPS and fees every day, but I care more about not treating oracle feed delays and cross-chain message queuing as "normal fluctuations"... Anyway, when something goes wrong, the blame is ultimately pushed onto the users.