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
was surprised reading layerzero's post-mortem yesterday, which blamed kelp for picking the "wrong" dvn configuration.
1-of-1 is the default layerzero config. it's in their docs, it's in their github, and ~47% of integrators on layerzero run with this config today.
which means, by layerzero's own framing, they've shipped 40% of their customers with what they now call a "wrong" setup.
that's clearly a shipped-default problem.
at the end of the day, the primary responsibility sits with layerzero. especially when they didn’t catch anything themselves and were only alerted by kelp. pushing blame downstream in that context doesn’t really make sense, this is first a failure at the default and monitoring level on lz’s side.