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
I almost screwed up just now: when copying the address, I added an extra space, and the wallet kept failing to send out. I thought it was a contract issue blocking me. I went to check the "on-chain" records, but there was nothing on the browser, and I felt a chill... Later, I switched to a different RPC, and immediately saw the pending status. Actually, the transaction was sent early; it was just that the node/indexer I was using was slow, and the delayed display scared me quite a bit.
So basically, what you see as "on-chain" is often a view provided by "a certain node + a certain indexing service," not an all-seeing perspective. L2s are now constantly arguing about TPS, fees, and subsidies—it's lively—but if you really start using them, issues like RPC stability, whether the index can keep up, and how to handle occasional rollbacks are more real experience pitfalls than online debates. Anyway, I’ve now gotten used to: before and after key operations, at least switch between two RPCs/browsers to verify, then check the raw transaction hash on-chain. Don’t be fooled into thinking "no display = no transaction"—that’s a misleading impression.