.jpg)
Trade.xyz has confirmed it will compensate traders whose positions were forcibly liquidated during the SK Hynix pricing anomaly that briefly rattled its perpetual futures market on Hyperliquid — though key details about who qualifies and how much will be paid remain unresolved.
What the Company Confirmed
The mark price for the SKHYNIX contract fell from $1,127.90 to $917.25 — an 18.7% drop — at 23:01 UTC on July 27, triggering a wave of forced closures among leveraged long positions. Trade.xyz has now said it will cover eligible liquidation losses tied to that anomaly, but the company was careful to frame the move as a one-time, discretionary decision rather than a standing policy for future disruptions. As of now, Trade.xyz hasn't disclosed the total payout amount, the exact eligibility formula, or a firm distribution date — only that criteria will be released soon, with payments expected to follow within days.
What Actually Triggered the Crash
The chain of events traces back to South Korea's NextTrade (NXT) exchange, where a single SK Hynix share traded at 1.272 million won as the pre-market session opened on July 28 — nearly 30% below the prior close of 1.816 million won, hitting the daily lower price limit. The stock recovered to the 1.7 million won range within about two minutes as more orders came in.
Korean market reports pointed to a likely order error compounded by thin pre-market liquidity. Unlike the Korea Exchange's regular session, which opens through a call-auction process, NXT's pre-market uses continuous matching — meaning a single trade was enough to briefly set an executable market price before deeper liquidity arrived to correct it.
Notably, SK Hynix's official Seoul close later that day came in at 1.55 million won, down a still-steep 14.65% — a real, verified decline, but far less severe than the outlier print that triggered the on-chain liquidations.
You Might like this also : Two Companies, One Name: Why "Polymarket" Now Means Two Completely Different Platforms
Trade.xyz Says Its Oracle Did Exactly What It Was Built to Do
In an official statement, Trade.xyz explained that multiple independent data providers relayed the executed NXT trade, and its oracle — which was actively tracking that external venue as a primary pricing source — behaved exactly according to its published design, even though the underlying price didn't reflect deep or durable market conditions.
That distinction matters technically: Trade.xyz operates the SK Hynix market under Hyperliquid's HIP-3 framework, which lets independent deployers supply their own oracle and mark-price data while Hyperliquid provides the shared order book, margin system, and liquidation engine. In other words, the flaw sat in Trade.xyz's price-sourcing methodology — not in Hyperliquid's core infrastructure. As with the earlier reporting on this incident, there's no indication of any blockchain or smart-contract compromise; the system simply processed a bad real-world price exactly as intended.
How Big Were the Losses?
On-chain tracker Lookonchain estimated that more than $80 million in SKHX positions were liquidated during the anomaly, citing one trader whose 2,026-token, $2.08 million long position was wiped out entirely, resulting in a $260,000 loss. Trade.xyz has not confirmed this figure or indicated what its total reimbursement liability might be, so the estimate should be treated as unofficial until the company releases verified numbers.
What Comes Next
Trade.xyz says it's now accelerating a review of how external exchange prices feed into its system, with plans to lean more heavily on its own order-book pricing going forward, which it says has since developed deeper liquidity and a more reliable market signal.
Separately, NXT itself is preparing a structural fix: according to Korean market reporting, the exchange plans to introduce a new volatility safeguard by September that would automatically switch trading into a two-minute call auction following a sharp price move — directly addressing the kind of thin-liquidity, continuous-matching gap that allowed this incident to happen in the first place.
For now, traders affected by the liquidations are waiting on two things: Trade.xyz's formal eligibility criteria, and a more detailed incident report explaining exactly what oracle changes will follow.
