Futures
Access hundreds of perpetual contracts
TradFi
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
Launchpad
Be early to the next big token project
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
Jan3 CEO criticizes Coinbase CEO for interfering in Bitcoin technical decisions: lacks a deep understanding of the issues, suggests Brian "fix himself first"
Mars Finance news: On April 5, Jan3 CEO Samson Mow posted a message criticizing Coinbase CEO Brian Armstrong for again interfering with Bitcoin’s technical decision-making. Samson pointed out that the problems Brian Armstrong exposed 10 years ago in the block size war still haven’t been addressed. He said Armstrong lacks humility and a deep understanding of the issue—setting the agenda, action plan, and timeline first instead of analyzing trade-offs. Coinbase’s own address reuse problem has made its wallet infrastructure vulnerable to quantum attacks, and during trading peaks it also frequently went down. Samson advised Brian to “first fix himself.” Samson believes that the threat from quantum computers has not yet actually existed, and that it is not expected to appear within 10–20 years. Therefore, Coinbase should not rush to switch from ECDSA/Schnorr to post-quantum signatures; instead, it should “the later the better” to avoid even greater risk. Samson listed three major drawbacks of a hasty anti-quantum upgrade in detail as follows: First, it could expose Bitcoin today to attacks from traditional computers. Second, post-quantum signatures are 10–125 times larger, which would significantly reduce throughput and could trigger a “Block Size War 2.0.” Third, it could become a Trojan horse by introducing RNG or cryptographic backdoors.