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.
Michael Saylor posts against BIP 110, saying it will restrict the current use of valid transactions under consensus rules
Deep Tide TechFlow news: On July 19, Michael Saylor published an article titled “110 Reasons BIP 110 Is a Bad Idea,” opposing Bitcoin proposal BIP 110. He said that BIP 110 would add seven consensus constraints within about 1 year via a soft fork, including restrictions on scriptPubKey, OP_RETURN, witness data, Taproot annex, control blocks, and some Tapscript usages, and it would adopt a modified BIP 9 deployment mechanism.
Saylor believes the proposal is not fixing clear consensus issues such as inflation, double-spending, or signature verification, but instead tries to address controversy over the intended use of valid paid transactions at the consensus layer. He said it could compress future upgrade space, increase activation-coordination risk, and set a precedent for excluding specific uses by consensus rules.