Trade.xyz announced on July 27 it will compensate users liquidated during an abnormal price event in its SK Hynix perpetual futures market, following a price drop from $1,127.90 to $917.25 at approximately 23:01 UTC—an 18.7% decline within seconds. The incident was triggered by a single SK Hynix share trade on South Korea's NextTrade pre-market at 1.272 million won, nearly 30% below the previous session's close of 1.816 million won, which was relayed through the platform's oracle system. The event highlights ongoing challenges in oracle design for tokenized equity perpetuals operating under Hyperliquid's HIP-3 framework, where third-party deployers define pricing methodology while the protocol provides infrastructure.
The sharp price move triggered widespread liquidations of leveraged long positions before prices quickly recovered. Trade.xyz stated the price originated from an executed trade on NextTrade that was relayed by multiple independent market-data providers and incorporated into the platform's oracle as specified. Although the oracle behaved according to its design, the company recognized the resulting liquidations were unacceptable from a user-experience perspective and decided to reimburse affected traders as a one-time discretionary measure.
Blockchain analytics firm Lookonchain estimated that more than $80 million worth of SKHYNIX long positions were liquidated during the event. One example involved a trader whose 2,026-contract long position, valued at about $2.08 million, was fully liquidated, resulting in an estimated loss of $260,000.
Trade.xyz Announces Pending Compensation Eligibility Criteria
Trade.xyz stated it will cover liquidation losses "attributable to this anomaly" but has not yet published precise eligibility criteria. The company has not disclosed the expected compensation amount, how affected accounts will be identified, whether users must submit claims, or how partial liquidations will be handled. Detailed eligibility rules will be released shortly, with distributions expected within the coming days. The platform stressed the reimbursement should not be interpreted as a guarantee of compensation for similar market events in the future.
Hyperliquid HIP-3 Framework and Planned Oracle Review
Trade.xyz operates the SK Hynix market under Hyperliquid's HIP-3 framework, where third-party deployers are responsible for defining oracle methodology and mark-price calculations, while Hyperliquid provides the matching engine, margin system and liquidation infrastructure. Hyperliquid clarified that the SK Hynix market is independently operated by Trade.xyz and that the protocol itself was not compromised.
In response to the incident, Trade.xyz stated it will accelerate a review of its pricing methodology. Planned changes include reassessing reliance on external trading venues and giving greater weight to prices derived from its own order book, which the company believes now provides deeper liquidity and more reliable price discovery during periods of market stress.
FAQ
What caused the SK Hynix price anomaly on Trade.xyz on July 27?
A single SK Hynix share traded on South Korea's NextTrade pre-market at 1.272 million won, nearly 30% below the previous session's close of 1.816 million won. This price was relayed by multiple independent market-data providers and incorporated into Trade.xyz's oracle, causing the SKHYNIX perpetual contract mark price to fall from $1,127.90 to $917.25 at approximately 23:01 UTC on July 27.
How much were traders liquidated during the SK Hynix incident?
Blockchain analytics firm Lookonchain estimated that more than $80 million worth of SKHYNIX long positions were liquidated during the event. One example involved a trader whose 2,026-contract long position, valued at about $2.08 million, was fully liquidated with an estimated loss of $260,000.
When will Trade.xyz release compensation eligibility details?
Trade.xyz stated detailed eligibility rules will be released shortly, with distributions expected within the coming days. The company has not yet disclosed how affected accounts will be identified or whether users must submit claims.
