Jupiter Lend Says Liquidity Crunch Is Delaying Withdrawals
- Published
- Updated
- Since then
- 2 new reports
- In
- DeFi
Jupiter Earn said it had no exposure to Binance, held no funds there, and recorded no losses from the recent security incident. The protocol also faced a large backlog of USDC withdrawal claims while its public API showed only a tiny amount immediately available to withdraw.
Key claims & sources
What it means
Depositors holding USDC in the Earn vault cannot pull their funds on demand: the public API showed just 3.35 USDC free against $418.5 million in claims, a gap that widened rather than closed over the following hours. Anyone needing cash now is stuck waiting for borrowers to repay or for the protocol to free up liquidity, while those willing to hold are effectively betting on Jupiter's no-losses claim holding up until utilization eases.
The episode exposes the gap between DeFi lending's promise of redeem-anytime deposits and the reality that utilization-based vaults can freeze almost entirely under stress, no hack required. A protocol can be solvent on paper, as Jupiter insists it is, and still leave users with a sliver of liquidity for a $414 million pool. That tension between stated safety and actual withdrawability is the real test of these products, not just their audit history.
The figure to track is whether Jupiter's available liquidity climbs meaningfully above the single-digit USDC levels seen Friday afternoon, more than nine hours after the crunch warning. A sustained recovery toward matching the $418.5 million in claims would validate the zero-losses message; continued near-zero availability would force Jupiter to explain a concrete timeline or mechanism for unwinding the backlog rather than repeating reassurances.
Market reaction i
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 4.0 years ago | FTX · Phishing incident | $450M |
| 5.9 years ago | OneCoin · Scam incident | $440M |
| 43 days ago | Bitget · Hot Wallet Key Compromised incident | $387M |
| 43 days ago | Bitget · Internal system compromise incident | $351.6M |
| 4.8 years ago | Portal · Signature Verification Flaw incident | $326M |
4280 incidents stored · 22 were as large as this one or larger ($418.5M)