Trade
Basic
Futures
Futures
Hundreds of contracts settled in USDT or BTC
Options
HOT
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Futures Kickoff
Get prepared for your futures trading
Futures Events
Participate in events to win generous rewards
Demo Trading
Use virtual funds to experience risk-free trading
Earn
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Launchpad
Be early to the next big token project
Alpha Points
NEW
Trade on-chain assets and enjoy airdrop rewards!
Futures Points
NEW
Earn futures points and claim airdrop rewards
Investment
Simple Earn
Earn interests with idle tokens
Auto-Invest
Auto-invest on a regular basis
Dual Investment
Buy low and sell high to take profits from price fluctuations
Soft Staking
Earn rewards with flexible staking
Crypto Loan
0 Fees
Pledge one crypto to borrow another
Lending Center
One-stop lending hub
VIP Wealth Hub
Customized wealth management empowers your assets growth
Private Wealth Management
Customized asset management to grow your digital assets
Quant Fund
Top asset management team helps you profit without hassle
Staking
Stake cryptos to earn in PoS products
Smart Leverage
NEW
No forced liquidation before maturity, worry-free leveraged gains
GUSD Minting
Use USDT/USDC to mint GUSD for treasury-level yields
More
Trending Topics
View More25.54K Popularity
34.13K Popularity
23.38K Popularity
7.47K Popularity
6.12K Popularity
Pin
An interesting PR in Bitcoin Core has attracted attention: developers are submitting patches for version v29 to fix a known vulnerability CVE-2025-46598.
The question is—why patch old versions?
The root cause lies in a major change in v30: proposal #32406 removed the 80-byte limit on the OP_RETURN opcode. This change altered the default data storage policy, causing behavioral differences between versions.
Some node operators are still using v29. If they do not apply this security patch, they face potential risks. This involves a classic technical dilemma—how to balance advancing innovation with maintaining backward compatibility.