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, project teams have been posting a bunch of GitHub links, audit reports, and claims that "upgrades are controlled by multi-signature," which makes newcomers feel more at ease. But honestly, these three can also be faked. My simple approach: first, check if the GitHub is "alive," look at the submission frequency, whether issues get responses, and if key changes are just temporarily inserted; don't just look at the cover logo of the audit, review the conclusions and scope—many audits only cover a small part, and the upgrade logic isn't included; as for multi-signature, don't just listen to "a few signatures are safe," check who the signers are, whether they are public, if there are timelocks/delays, and whether a single click can upgrade and change rules. Recently, the testnet incentives and points systems are heating up again, and everyone is guessing whether the mainnet will issue tokens... I actually want to understand first: if they change the contract, do I have time to react? Anyway, I treat simple things as traps; a phrase like "it's audited, so it's safe" basically means nothing.