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, people keep saying, "All on-chain data is public, so how can you still get it wrong?" I think the premise needs to be clarified: which on-chain data are you seeing? If the node/RPC you're using is queuing, rate-limited, or simply using a cache from a certain provider, your "latest" data might already be several seconds or even minutes behind; plus, indexers need to parse and store data, which can slow things down further during congestion. To put it simply, the timestamps I see for the same transaction on different browsers or different RPCs can be inconsistent—don't be too superstitious about "what I see = just happened on the chain." Recently, new L1/L2 projects are incentivizing to boost TVL, and I understand the complaints from old users about mining, selling, and dumping… I also envy new miners who are quick and have near real-time info. Anyway, when I look at on-chain data now, I first consider the data source and latency, then draw conclusions; otherwise, I might be influenced by the "late-arriving on-chain" narratives.