Stay connected with KayaToday, follow us on Instagram and Facebook for the latest news and reviews delivered straight to you.
One of the persistent promises of onchain perpetual markets is that they remove the human discretion that critics associate with centralised exchanges. Rules are rules, encoded and immutable. Then a single anomalous trade on an external venue crashes a mark price by nearly 19 percent in seconds, and suddenly the platform is announcing a discretionary reimbursement. That tension sits at the heart of what happened to Trade.xyz’s SK Hynix contract on Monday.
Trade.xyz, which operates onchain perpetual markets on the Hyperliquid platform, confirmed it will cover eligible liquidation losses after the SKHYNIX contract’s mark price dropped from $1,127.90 to $917.25 at 23:01 UTC on Monday. The cause, the platform said, was an executed trade on an external market that was picked up and relayed by multiple independent data providers feeding its oracle. Eligibility requirements have not yet been published, and distributions are expected within days. The total payout has not been disclosed.
Why a Korean Chipmaker Has $600 Million in Crypto Open Interest
Before unpacking the mechanics of the anomaly, it is worth pausing on the scale of this market. SK Hynix is a South Korean chipmaker and a major supplier of high-bandwidth memory for AI accelerators, making it one of the most closely watched stocks in the global semiconductor trade. On Wednesday, Hyperliquid data showed the SKHYNIX perpetual contract had generated over $1.5 billion in 24-hour trading volume and held nearly $600 million in open interest. Those are not trivial figures for a crypto-native instrument tracking a foreign equity.
Trade.xyz operates under Hyperliquid’s HIP-3 framework, which allows developers to launch perpetual contracts tied to assets with external price feeds rather than native crypto tokens. The platform has been the dominant force in this segment, accounting for more than $22 billion of HIP-3’s first $25 billion in cumulative volume. It has also launched an officially licensed S&P 500 perpetual using S&P Dow Jones Indices data. The ambition is clear: bring equity and commodity price exposure onchain, with leverage, and settle everything in crypto.
That ambition creates a structural dependency on the quality of external price data, and Monday’s event exposed exactly where that dependency can break.
How One External Print Became a Liquidation Event
Trade.xyz’s oracle for the SK Hynix contract works by tracking the US dollar value of one SKHX common share, converting the underlying Korean won price using the prevailing exchange rate. The platform’s documentation describes this as tracking an external venue used as the primary South Korean pre-market reference.
When an anomalous transaction was executed on that external venue, the oracle picked it up and fed it into the mark price calculation. Because Hyperliquid uses the mark price to value open positions for margin purposes and to determine when leveraged positions should be liquidated, the sudden drop triggered forced closures across accounts that were long the contract with insufficient margin to absorb the move.
Trade.xyz acknowledged the frustration this caused while defending the technical operation of its system. The oracle, it said, had “worked as intended according to its specification.” The problem was not a bug in the oracle logic. It was that the specification itself did not account for the possibility of a single anomalous external print being treated as a reliable price signal and cascading into mass liquidations on a market with hundreds of millions in open interest.
The platform described the reimbursement as a “one-time discretionary decision” and said it would review how prices are formed during extreme market events. It is also considering giving greater weight to prices formed on its own order books, which it noted now provide meaningful liquidity and market signals of their own.
The Deeper Design Problem This Exposes
The incident points to a genuine tension in the design of any perpetual market that tracks external assets. Oracle manipulation and oracle failure are well-documented risks in decentralised finance, and protocols have spent years building defences against them, including time-weighted average prices, multi-source aggregation, and circuit breakers. Trade.xyz used multiple independent data providers, which is standard practice. Yet the anomalous print still reached the mark price because all those providers were drawing from the same underlying external venue.
The proposed fix, weighting the platform’s own order book more heavily, is a reasonable response, but it introduces its own trade-off. A thinly traded internal order book can itself be manipulated, particularly in off-hours when the underlying equity market is closed. The ideal solution is probably a hybrid approach that blends internal and external signals with explicit rules for how to handle outlier prints, but designing those rules robustly is harder than it sounds.
For traders in Malaysia and Singapore who use platforms like Hyperliquid to gain leveraged exposure to global equities without going through traditional brokers, this episode is a useful reminder that the infrastructure underpinning these markets is still maturing. The liquidity is real, the volumes are substantial, and the products are genuinely innovative. But the risk management frameworks are still being written in real time, sometimes in response to events exactly like this one.
Trade.xyz’s willingness to cover losses voluntarily is a positive signal about the platform’s intentions, and its transparency about the oracle mechanism is more than many centralised venues would offer. The harder question is whether a “one-time discretionary decision” is the right long-term answer, or whether the industry needs clearer, pre-committed rules for how onchain perpetual markets handle price anomalies before the next one arrives.
Read More: Crypto Exchanges Are Becoming Stock Brokers, and the Numbers Show Why
