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
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
Recently, I've been reviewing several cross-chain bridge incident retrospectives. To put it simply, a bridge is just "I lock the funds here first, and you send me a shadow on your side," and who has the final say in the middle is very critical. Multi-signature may sound centralized, but are the signers from the same group? Do they have cold wallets? Can permissions be temporarily added... these details are more important than "a few signatures." Oracles are the same; if the source of price feeds or messages is skewed, by the time you see on-chain confirmation, it's already too late.
Many people complain that "waiting for confirmation" is slow, but those few minutes are actually a gamble: gambling that multi-signature isn't colluded, gambling that the oracle isn't hijacked, gambling that the gatekeepers of the bridge won't change the rules behind the scenes. Recently, with the news of increased taxes and compliance, deposit and withdrawal sentiments have become more sensitive. The more urgent the cross, the easier it is to overlook these issues... Anyway, my first reaction when seeing a new bridge isn't APY, but to check permissions and fund paths first. If it takes a bit longer, so be it.