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
F2Pool Co-founder Wang Chun: BTC Protocol Upgrade Should Not Include "Political Compromises"
BlockBeats message, April 4, F2Pool co-founder Wang Chun said in a post on the X platform that the Bitcoin protocol upgrade should not involve similar conduct to that of American politicians using a “package bill” to force through “some provisions that must pass but are unpopular,” and this is also an important reason for his opposition to BIP-110 and BIP-54.
In response to whether he has encountered any problems with any remediation procedures that use BIP-54, Wang Chun added that the “Timewarp” problem has been around for a long time and offers miners no significant advantage, because it is not possible to predict who will mine the next block. Its only practical use is to disrupt certain altcoins. Since it provides virtually no practical benefits to Bitcoin miners, there is no urgent need to modify it. In addition, block validation efficiency has been significantly improved by libsecp256k1 and hardware upgrades, so there is no need for protocol-layer adjustments. As for “forging already confirmed transactions,” it fundamentally depends on exploiting a broken double SHA256 collision; if it were to work, it would mean that Bitcoin Core security has been compromised.
Wang Chun added that none of the issues mentioned above are sufficient to drive protocol changes. At present, only the “duplicate transactions” problem has some remediation value, and it may be the only change (or one of very few changes) worth implementing.