The JELLY episode and mutualised risk

It happened again.

When Hyperliquid’s liquidation engine couldn’t close the JELLY position, someone had to cover $13.5 million. Do you know who that was?

When a position is too large to liquidate in the open market, auto-deleveraging fires. The position passes to the platform’s own liquidity pool automatically. The pool absorbs the loss. That pool is funded by traders who deposited capital into it. They are now covering a position they did not individually agree to take on. They may not have even known about Jelly. That is mutualised risk. That is ADL. Impossible to price.

Any institutional risk committee asks three questions before committing capital to a clearing venue.

Who covers when something goes wrong.

How do you know they have the capital to cover it.

Who owns the residual risk if they don’t.

In traditional clearing, every one of those questions has a contractual answer, a defined default waterfall, regulated capital adequacy, legal enforceability.

In an ADL based model, the answers are: the pool, if it’s deep enough, and whoever the platform decides absorbs the remainder.

Hyperliquid’s validator set voted to delist the market and settle positions at $0.0095. The Hyper Foundation stepped in to make unaffected users whole. That matters. But there is no rulebook that required them to do it. No regulator that enforced it. It was a commercial decision.

That is not a clearing house. That is a platform choosing to absorb a loss it was not contractually obligated to cover.

The three questions still don’t have contractual answers. Every institution that understands this builds accordingly.

#DerivativesClearing #CryptoInfrastructure #RiskManagement #MarketStructure #InstitutionalCrypto

This first appeared on LinkedIn on 31 March 2026. If you want to comment or discuss, that’s the place.