Uneasy Money: Is Jupiter Incompetent or Evil? And Is Hyperliquid's ADL Flawed? - Ep. 976

What It Covers

Jupiter's lending protocol faces scrutiny over misleading isolated collateral claims, Hyperliquid's auto-deleveraging algorithm draws criticism, Lighter's zero-fee model hides costs in latency spreads, and Farcaster pivots from social network to wallet after failing to break Twitter's network effects.

Key Questions Answered

• •Isolated Lending Pools: Jupiter claimed zero contagion risk between lending pools, but users could borrow from one pool and deposit in another, creating cross-contamination risk. Multicoin framed this as either incompetence or deliberate misrepresentation, though organizational communication breakdowns at large teams likely explain the disconnect between engineering and marketing messaging.
• •Lending Protocol Economics: Lending protocols operate on thin margins of approximately 20 basis points on deposits, making them far less profitable than swap businesses which can earn multiple percentage points per trade. Jupiter likely generates 50-100x more revenue from swaps than lending, suggesting their lending expansion serves user retention rather than direct revenue generation.
• •Zero-Fee Trading Tradeoffs: Lighter's zero-fee tier imposes 200-300 millisecond latency, creating worse execution prices than fee-based alternatives. This latency filters out sophisticated traders, leaving only uninformed retail flow for market makers to trade against profitably. Only retail traders would accept poor latency for zero fees, making them definitionally uninformed and easier to extract value from.
• •Token Launch Timing: Launching tokens too early creates infinite downside for founders, as communities judge success by all-time-high prices rather than seed valuations. Synthetix raised at 8 million dollars, now trades at 200 million, but reached 5 billion at peak, making the team appear unsuccessful despite 20x returns. Delaying tokenization until product-market fit exists protects founder reputation and focus.
• •Senior Engineering Value: Hiring expensive senior engineers with 15 years experience in release management or DevSecOps provides immediate infrastructure improvements that junior crypto-native engineers cannot deliver. Senior engineers quietly fix architectural problems without criticism, understanding why suboptimal decisions were made initially, whereas junior engineers get frustrated by existing technical debt and organizational choices.