Futures
Access hundreds of perpetual contracts
CFD
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
CFD
Stock CFD Derivatives
US Stocks
Access real US stocks and ETFs
HK Stocks
Trade quality Hong Kong-listed stocks
Korean Stocks
SK Hynix
Real Korean stocks and top assets
Stock Futures
High leverage, 24/7 trading
Tokenized Stocks
Backed by real stock assets
IPO Access
Unlock full access to global stock IPOs
GUSD
3.8%
Mint GUSD for Treasury RWA yields
Stocks Activities
Trade Popular Stocks and Unlock Generous Airdrops
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
Promotions
AI
Gate AI
Your all-in-one conversational AI partner
Gate AI Bot
Use Gate AI directly in your social App
GateClaw
Gate Blue Lobster, ready to go
Gate for AI Agent
AI infrastructure, Gate MCP, Skills, and CLI
Gate Skills Hub
10K+ Skills
From office tasks to trading, the all-in-one skill hub makes AI even more useful.
Holds like a potted plant 🌱
I’ve been asked several times recently—how to judge whether a project is reliable, looking at GitHub, audit reports, upgrading multisigs, and so on. To be honest, when I first started, I was also completely confused. Anyway, now I’ve gradually come up with a few of my own dumb little methods.
First, GitHub—don’t just look at the star count. Click in and check the commit history from the past few months. If it’s all minor tweaks or there’s been no activity for a long time, then it’s basically the potted plant that forgot to be watered. As for audit reports, I usually look at the name of the audit team and the report date. If it’s too old, I skip it, because by then the code has usually gone through several rounds of changes. For upgrading multisigs, I focus on the number of signers and who they are. If all the signers are people from the project team, then it’s almost the same as not having extra multisig at all.
Recently, on-chain data tools have been questioned for lagging behind or even being able to mislead people. I think that’s pretty normal. Tools are dead; people are alive. The key is still to have your own judgment. Anyway, I’ve developed a habit now: whenever I see an interesting on-chain action or an upgrade announcement, I screenshot and save it first. If things end up going wrong later, at least I’ll have something to compare against. 🌿