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
The third time someone asked, "It's all written on the chain, how can there still be errors," I just want to laugh... What you see as "on-chain" is often just the perspective from the node/RPC you're connected to. Nodes sync slowly, RPC rate limits act up, indexers are still filling in historical data, so the same transaction might be seen early by some and late by others, even appearing inconsistent in status. This is even more obvious when monitoring the mempool, like waiting for a bus: you think the bus hasn't arrived, but actually the bus stop screen is frozen.
Recently, comparing RWA and U.S. Treasury yields to on-chain yield products, I also find it quite surreal. Honestly, don’t just look at the yield screenshots; first consider where the data comes from, how much delay there is, and whether it’s being selectively displayed. I personally prefer to check multiple sources, even if it’s less frequent, so I won’t be led astray by those jumping the queue or delayed data.