Hyperliquid Explains $57 Million Sk Hynix Perp Liquidations After Oracle Anomaly

What Happened

The trigger came from NXT, a South Korean alternative stock venue that launched in March 2025. It trades from 8 a.m. to 8 p.m. local time. Korea Exchange, the main market, runs only from 9 a.m. to 3.30 p.m.

“Hyperliquid is a permissionless blockchain. Different teams can deploy and operate markets on Hyperliquid, using it as the infrastructure layer… The XYZ team is investigating the situation and will share any update once they have a conclusion,” wrote iliensinc is the pseudonymous co-founder and core developer of Hyperliquid.

Market Context

Hyperliquid’s SK Hynix perpetual contract, xyz:SKHYNIX, fell 17.9% on Tuesday after a bad price print in Seoul. Around $57.4 million in long positions was liquidated across 960 accounts.

Hyperliquid neither deployed nor operated that market. Trade.xyz did, under a framework called HIP-3. That distinction decides who controlled the price feed, and who can be punished for it.

Those extra hours are thin. An abnormal pre-market order there valued one SK Hynix share at 1,272,000 won. Hyperliquid traders reported that figure, which neither firm has confirmed.

SK Hynix had closed the prior session at 1,785,000 won, Yahoo Finance data shows. The print therefore implied a 28.7% collapse. Korean trading halted.

The contract’s oracle pulls prices from outside venues while those venues are open, per Trade.xyz documentation. It converts won into dollars at the prevailing exchange rate. The bad print became the reference.

Context made it plausible. SK Hynix was already inside an AI memory stock selloff, and the wider Korean market crash had cut the KOSPI 8% that morning.

The contract dropped far less than the underlying print. That was designed, not lucky. Trade.xyz caps how far a mark price can travel using what it calls discovery bounds.

Read plainly, the guardrail held. It absorbed close to 11 percentage points of a corrupted price. It also allowed a 19% slide, which clears leveraged longs comfortably.

On-chain analysis published by the account MarketsAlpha counted 960 long accounts closed and about $17.3 million in realized losses. The backstop then auto-deleveraged profitable shorts, booking roughly $10.8 million across 100 accounts. Neither Hyperliquid nor Trade.xyz has confirmed those figures.

Why Hyperliquid Says the SK Hynix Perp is not its Market

HIP-3 operators push the mark price, the oracle, and external price inputs themselves. Hyperliquid supplies just one of the three components that set the mark.

Validators do hold a lever. HIP-3 rules require deployers to keep 500,000 HYPE staked, worth about $27.4 million at Tuesday’s price. A stake-weighted validator vote can burn it.

A threshold also works against review. Validators examine cross-margin assets automatically when the external price moves more than 50% from the start of day. Tuesday’s move fell well short.

Why It Matters

What Caused the SK Hynix Perp Crash on Hyperliquid

Why the Perp Fell 17.9% and Not 28.7%

Details

The published specification gives xyz:SKHYNIX a 10% instantaneous bound and one permitted reset. Compounding those sets a hard floor 19% below the session reference. The reported 17.9% move stops just inside that floor.

One design choice widened the blast radius. xyz:SKHYNIX runs on cross margin, while the Samsung and Hyundai perps on the same venue are isolated. Cross margin lets one losing position draw on collateral supporting others.

A Hyperliquid team member posting as iliensinc answered frustrated traders in the project’s Discord. The argument was structural rather than defensive.

The example given was blunt. Say the onchain median of last trade, best bid and best ask sits at 100. If the operator pushes 150 and 151, the mark becomes 150. The operator’s numbers win.

Can Trade.xyz be Slashed, and Would Traders be Repaid?

Two clauses point at this incident. Slashing does not separate malicious conduct from incompetent conduct. It also covers a deployer that faithfully follows a poorly designed contract spec.

The harder clause is for traders. Slashed stake is burned rather than distributed to affected users. Even a full penalty would return nothing to the 960 liquidated accounts.