Trade.xyz Plans to Absorb SK Hynix Perp Liquidation Losses After Price Anomaly

Trade.xyz, the operator behind onchain perpetual markets on Hyperliquid, says it will reimburse eligible liquidation losses after a sudden price anomaly affected the platform’s SK Hynix perpetual contract. The incident followed a sharp drop in the contract’s mark price late Monday, after an external trade was relayed and processed through Trade.xyz’s oracle.

In a statement posted on X, Trade.xyz said the SKHYNIX mark price fell from $1,127.90 to $917.25 at 23:01 UTC on Monday. The move, it explained, was triggered after an executed transaction on an external venue was picked up by multiple independent data providers. Trade.xyz did not provide details on the size of the reimbursement pool or how many traders would qualify, saying only that eligibility requirements will be announced soon and distributions are expected in the coming days.

Key takeaways

• Trade.xyz will cover eligible liquidation losses tied to the SKHYNIX mark-price anomaly, with eligibility details and payouts expected shortly.
• The affected mark price moved after an external market execution was processed via the contract’s oracle, not from activity within Hyperliquid’s own order book.
• Hyperliquid data cited in the report shows SK Hynix is one of its most actively traded contracts, with over $1.5 billion in 24-hour volume and nearly $600 million open interest at the time of writing.
• Trade.xyz said its oracle was operating “according to its specification,” but plans to review how prices are formed during extreme market events.
• The firm is considering weighting prices derived from its own order books more heavily going forward.

A liquidation event tied to an external print

The SK Hynix perpetual ranks among Hyperliquid’s most active markets. According to data shown on Hyperliquid earlier this week, the contract recorded more than $1.5 billion in 24-hour volume and maintained close to $600 million in open interest at the time of writing.

Trade.xyz attributed Monday’s dislocation to an executed trade on a separate venue. It said the oracle behind the SKHYNIX contract tracked the price of one SKHX common share in U.S. dollar terms by converting the underlying Korean won price using the prevailing exchange rate, as described in its documentation. That external print then fed into the oracle and contributed to the mark-price jump that determined position valuations and liquidation timing on Hyperliquid.

On Hyperliquid, the mark price is used for margin accounting and for deciding when leveraged positions become liquidatable. As a result, abrupt oracle-driven mark-price movements can translate quickly into forced liquidations—even if the platform’s own trading activity does not appear to mirror the same immediate pricing signal.

Trade.xyz: oracle worked, reimbursement is discretionary

Trade.xyz said its oracle “worked as intended according to its specification,” describing the oracle’s role in transforming an external venue’s execution into a mark price for the perpetual contract. The company acknowledged that traders may be frustrated when liquidation decisions rely on mark prices that change quickly due to external feeds rather than the dynamics of the local order book.

To address the fallout, Trade.xyz characterized the reimbursement as a “one-time discretionary decision.” While the firm did not disclose the total expected reimbursement amount or qualifying criteria in the immediate announcement, it said it would release eligibility requirements soon and make payouts in the coming days.

For traders and market participants, the key question is how “eligible liquidation losses” will be defined—particularly whether the scope will be limited to liquidations directly attributable to the oracle-driven mark-price move, or whether it will include a broader window of positions impacted by the anomaly.

What Trade.xyz says it may change in extreme moves

Beyond the immediate reimbursement plan, Trade.xyz indicated it is reviewing the mechanics of price formation during stress events. Specifically, it said it is considering giving more weight to prices formed on Hyperliquid’s own order books. The rationale is straightforward: if the platform’s internal liquidity and trading activity are “now providing meaningful liquidity and market signals,” then relying solely on an external oracle during unusual conditions may produce outcomes that feel disconnected from where traders are actually transacting.

This shift—more internal weighting versus external-feed dominance—matters for risk management on perp venues. Mark-price sourcing influences liquidation outcomes, and therefore shapes how traders size positions and place risk controls. If Hyperliquid’s internal pricing is considered a more reliable reflection of market consensus during abnormal intervals, it could reduce the likelihood of liquidation cascades driven by outlier oracle updates.

Trade.xyz also placed the anomaly within the larger context of Hyperliquid’s HIP-3 framework, which enables builders to launch perpetual contracts tied to assets with external price feeds. Trade.xyz has been a significant HIP-3 volume contributor, accounting for more than $22 billion of HIP-3’s first $25 billion in cumulative volume, as previously reported by Cointelegraph. It later launched an officially licensed S&P 500 perpetual using S&P Dow Jones Indices data.

Why this episode matters for Hyperliquid’s perp model

Hyperliquid’s architecture gives traders access to highly active perpetual markets, including contracts where mark prices are dependent on external data sources. That design can be efficient when external prints represent fair value—but it also creates a vulnerability when an external venue’s execution, reporting timing, or feed relays cause sharp dislocations that arrive faster than the internal order book can reflect them.

The SK Hynix incident illustrates the trade-off inherent in oracle-based perpetuals: external feeds can improve alignment with offchain reference pricing, but they can also produce sudden mark-price jumps during extreme events. Trade.xyz’s decision to reimburse liquidation losses is an attempt to address user harm after such a jump, while its stated intent to adjust how it weighs internal order books suggests it may seek to make future outcomes less dependent on a single external print.

As eligibility criteria are released and payouts begin, market participants will likely focus on whether reimbursed losses are limited narrowly to the affected mark-price window or extend to positions impacted by broader volatility. Traders should also watch for any subsequent technical or policy updates from Trade.xyz regarding oracle handling and the balance between external reference pricing and Hyperliquid’s own order-book signals.