why don't we see tweets like
"had you bought $btc puts at 79k, you'd have made $20m"
"had you bought $eth calls at $1,600, you'd have made $5m"
we see these kinds of tweets for stocks all the time, especially when options are approaching expiry and a relatively small position turns into an absurd amount of money
but in crypto, traders overwhelmingly gravitate towards perps. options never really found its place in crypto
i think there's a massive opportunity for a perp dex to change this
make options so simple that even degens understand them and start trading it like memecoins. make asymmetric bets accessible (classic degen moves) and turn genius options executions into viral moments
imagine a $5k options position turning into $4m and everyone on crypto twitter talking about it
we only see such gains for memecoins
that would be a magnet for degens and i would love if some perp dex can make it happen
i wonder what moat hyperliquid has other than first mover advantage that people still trade on it despite of high fees?
ui experience is incredible but is it enough to command such high fees?
or is it trust on hyperliquid? that jeff from hyperliquid is genius and their money is safe on hyperliquid
i have couple of friends who have very low entries on $hype ( under $10 ) and they refuse to take profits. infact one keeps adding more
truly remarkable what hyperliquid has achieved π€―
@zachxbt sad part is they won't fix this
cause fixing this means admitting that they made a mistake in first place and that can't happen π
only solution is pressurising them to make a team of qualified and competent blockchain experts which handles such cases
recovery of funds is priority lol
priority should be security and preventing the exploits
for that you need to have a bug bounty program and that too not peanuts but atleast $1 million ( especially for critical vulnerability )
so security researchers have an incentive to spend time testing your platform, finding vulnerabilities and reporting them before malicious actors can exploit them
this vulnerability ( reuse of nonce can leak api key ) is nothing genius and it could've been easily found by bug bounty program
'if you've found a vulnerability, please respond to us responsibly' approach doesn't work
what it means is ' we are fine getting hacked for millions but we won't offer anything for your contribution if you help us strengthen our platform'
hoping huge bug bounty program becomes new standard where people actually compete to report critical bugs for huge rewards to prevent future hacks
@Lighter_xyz@vnovakovski
reading everywhere that lighter got hacked or exploited which is not true
this is not a fault of perp dex. ofcourse with safety measures it could've been prevented
but what's surprising is that user's api keys got compromised ( user's fault ) and it resulted in platform token dumping 20%
in this case, it's $LIT
now imagine a hypothetical scenario
1. i short perp dex token heavily from wallet 1 with high leverage
2. i leak api keys of my 'wallet 2' or claim it was compromised π
3. from a new wallet, i use those api keys to extract funds
4. news leaks that perp dex platform was exploited
5. perp dex token dumps 20% while my funds are still with me
6. i close my shorts π€
not saying this is what happened but this is how it can be manipulated
> @Lighter_xyz didn't get hacked, there are bigger wallets that would have been drained if so
> Abraxas' Lighter API keys got compromised
> a builder didn't get hacked. there would be more compromised keys that would have been drained the same way
> the Abraxas servers were likely not compromised because there are other less clean ways to drain accounts on trade-only keys (wash trading) and it hasn't happened
which makes me believe that Abraxas had the 2 Lighter API keys (stored in browser, chat logs, saved, etc) on an employee's computer, which was compromised
exchanges should NOT have transfer permissions on API keys (without explicit consent). @HyperliquidX and most other perp DEXs limit API keys to trading only, but even then, @binance and all the other CEXs allow for very granular permissions including:
> IP addresses
> individual actions
> instrument whitelists
perp DEXs should follow suit, there is no reason not to