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 saw the project "upgraded multi-signature again and added an audit," and a bunch of people in the group started automatically adding trust scores.
My own simple method is: first check GitHub to see if the commits are maintained by someone long-term, not those who haven't touched it for half a year and only rush to update the README right before the exam;
then look at the audit report, focusing not on how fancy the cover page is, but whether the issue list has follow-ups marked as "fixed/unfixed," preferably matching the code changes.
Don't just look at "3/5 is very safe" for multi-signature; check who the signers are, whether they are the same group of people using different accounts, because in truth, opaque multi-signature setups are only slightly more respectable than single signatures.
Recently, hardware wallets are out of stock, and phishing links are everywhere.
It's during times like these that it becomes clear: everyone talks about security seriously, but in practice, people are quite casual about it...
I'll first review all authorizations and bookmarks to avoid waking up later and having to patch up.