Trade.xyz to reimburse SKHYNIX perp liquidations after 19% mark-price anomaly
The platform called the payout a one-time discretionary decision after an external executed trade flowed into its oracle.
Trade.xyz said it will reimburse eligible traders liquidated on its SK Hynix perpetual after the contract’s mark price dropped nearly 19% in a single print. The move spotlights how oracle-fed mark prices can become the liquidation trigger on Hyperliquid HIP-3 markets even when the oracle behaves as specified.
Key Takeaways
- Trade.xyz committed to covering eligible liquidation losses tied to a price anomaly in its SK Hynix perpetual contract.
- The SKHYNIX mark price fell from $1,127.90 to $917.25 at 23:01 UTC on Monday, a near-19% drop that triggered liquidations.
- An executed transaction on an external market was relayed by multiple independent data providers into the oracle, and Trade.xyz said the oracle “worked as intended according to its specification.”
- Eligibility criteria and the total reimbursement amount remain undisclosed, with rules expected soon and distributions expected in the coming days.
A 19% Mark-Price Shock Triggers SKHYNIX Perp Liquidations
Trade.xyz said it will reimburse eligible traders liquidated in its SK Hynix perpetual after a sharp mark-price move hit the contract at 23:01 UTC on Monday. The mark price printed down from $1,127.90 to $917.25, nearly a 19% drop.
For perp traders, the detail that matters is not the last trade on a venue’s order book. It is the mark price used for margining. On Hyperliquid, the mark price is used to value positions for margin purposes and to determine when leveraged positions should be liquidated. That makes any abrupt mark-price deviation a direct liquidation vector, even if the move is brief.
How an External Executed Trade Flowed Through Data Providers Into the Oracle
Trade.xyz attributed the move to an executed transaction on an external market rather than activity on its own order book. It said that print was relayed by multiple independent data providers into the oracle feeding the SKHYNIX market.
The platform’s documentation describes the SK Hynix oracle as tracking the US dollar value of one SKHX common share by converting the underlying Korean won price using the prevailing exchange rate. In this incident, Trade.xyz said the external print fed into the oracle and contributed to the mark-price move.
Trade.xyz also framed the episode as a case where the system behaved as designed, stating the oracle “worked as intended according to its specification.” The second-order effect is the uncomfortable one for traders: even when an oracle follows spec, a single externally sourced executed trade can still propagate through data providers into the reference price that governs liquidations.
Why This Matters on Hyperliquid: Mark Price as the Liquidation Trigger
Trade.xyz operates under Hyperliquid’s HIP-3 framework, which allows builders to launch perpetual contracts tied to assets that rely on external price feeds. Trade.xyz said it accounted for more than $22 billion of HIP-3’s first $25 billion in cumulative volume and later launched an officially licensed S&P 500 perpetual using S&P Dow Jones Indices data.
The SK Hynix perp is also not a thin side market. Hyperliquid data showed over $1.5 billion in 24-hour volume and nearly $600 million in open interest at the time of writing reference. In a high-volume, high-OI contract, mark-price integrity is market structure, not UX. A one-off oracle-driven liquidation cascade in one of the most active HIP-3 perps becomes a test case for how robust price formation is when the feed is forced to ingest an extreme print.
Signals From the Aftermath: Eligibility Rules, Payout Timing, and Any Price-Formation Changes
Trade.xyz described the reimbursement as a “one-time discretionary decision,” not a standing guarantee. It did not disclose how many traders will qualify or the total amount it expects to distribute. Eligibility requirements are expected “soon,” and distributions are expected in the coming days.
The platform said it will review how prices are formed during extreme market events. It is considering giving more weight to prices formed on Hyperliquid’s own order books, arguing those books now provide meaningful liquidity and market signals.
Traders will be watching for the concrete details that determine whether this is a contained clean-up or a structural mitigation: the eligibility cutoffs (time window, position types, and any margin or leverage constraints), confirmation of distributions and total payout size, and any disclosed changes to oracle inputs or weighting. The other live signal is whether additional sharp mark-price deviations recur in SKHYNIX or spill into other HIP-3 perps during periods of elevated open interest.
The Real Risk Signal Is Oracle-Driven Liquidations in High-OI HIP-3 Perps
I don’t read the reimbursement as proof the oracle “failed.” Trade.xyz explicitly said it behaved to spec. The risk signal is that a single executed trade from an external venue can still traverse multiple data providers and land directly on the mark price that governs liquidation, which is a different problem than bad fills on a local order book.
The threshold that matters is whether Trade.xyz publishes tight eligibility rules and follows through with distributions, then pairs that with a real change in extreme-event price formation. If that mitigation shows up and holds under high open interest, the setup starts to look structural rather than narrative-driven, and it would matter because it reduces the probability that one external print can liquidate size across HIP-3 perps.
