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
IPO Access
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
Wu reported that Bitcoin Core issued a statement revealing that the new -privatebroadcast feature introduced in version 31.0 has a privacy vulnerability. Under certain network conditions, it may cause the transaction initiator's IP address to be disclosed to receiving nodes. The fix will be included in version 31.1.
This vulnerability occurs when private broadcast supports BIP324 v2 transmission on IPv4 or IPv6 nodes. If the v2 handshake fails, Bitcoin Core will retry with v1, but this reconnection will not go through the Tor proxy and will connect directly via IPv4 or IPv6 to the peer.
Affected are Bitcoin Core 31.0 nodes that have enabled -privatebroadcast, broadcast transactions via sendrawtransaction RPC, and can directly establish outbound IPv4/IPv6 connections. Wallet RPC, onion, and I2P node connections are not affected.
Bitcoin Core recommends that relevant users disable -privatebroadcast, disable v2 transmission, or route outbound IPv4/IPv6 traffic through Tor before upgrading to version 31.1.