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
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.
GateRouter
Smartly choose from 40+ AI models, with 0% extra fees
many such cases. i was just working on getting a more accurate realized/estimate of slippage when the my execution engine is filling positions and CC assumed i was calculating it wrong.
i was pretty sure i didnt because i reconcile this data points manually quite often. i had to go into hyperliquid ide and get a bunch of execution prices to dump into the prompt for him to find that i was doing it right.
two things that come from this:
> never assume what CC says is right off the bat. verify the code, i know its boring, but in important tasks, do it.
> document these little quirks. after this is done, im going to dump this into the execution engine architecture md file, so it never forgets about it.
AI code gets a rep for slop and its true. you still have to be the person checking if the code makes sense and matches your desired output.