A single erroneous trade in SK Hynix stock before the market opened triggered a cascade of liquidations worth nearly $60 million in the crypto world.
It’s hard to believe that one abnormal sale of a single share became the trigger that crushed nearly a thousand long-position traders on-chain.
On the morning of July 28, Nextrade, a South Korean alternative exchange, opened pre-market trading with extremely thin liquidity. An unusually low-priced sell order, far from the market price, was executed. Seconds later, this distorted price was blindly captured and transmitted by a third-party oracle used by the decentralized derivatives platform Hyperliquid. Within moments, the on-chain SK Hynix perpetual contract plummeted by 20%, wiping out 960 long-position accounts before they could react.
According to data from on-chain analytics account MarketsAlpha, 960 long positions were liquidated, involving a total position size of approximately $57.4 million, with actual losses of around $17.3 million.
However, what is more frustrating for victims than the flash crash is the platform’s response. Despite the obvious systemic data transmission vulnerability, the platform distanced itself, citing its decentralized nature. The existing penalty mechanism also proved ineffective. This tragedy, triggered by a single fragile data source, is peeling back the curtain on the excesses of on-chain derivatives.
Hyperliquid emphasized that the xyz:SKHYNIX contract was not deployed or operated by them but was independently managed by a third-party team, Trade.xyz, under the HIP-3 framework. Control over the price oracle also rests with Trade.xyz. As a result, affected users face a difficult path to compensation—even if the penalty mechanism against Trade.xyz is triggered, the staked tokens that are destroyed are not distributed to the affected traders.
Analysts believe this event has brought the structural risks of perpetual contract products in the crypto market to the forefront. When the price of an on-chain derivative is anchored to a single or fragile external data source, a single anomalous trade during a period of low liquidity can destroy tens of millions of dollars in leveraged positions within seconds.
How One Sell Order Triggered a Cascade of Liquidations
The starting point of this event was an anomalous order on the South Korean alternative stock exchange, Nextrade (NXT).
NXT launched in March 2025 and operates from 8:00 AM to 8:00 PM local time, providing a longer pre-market liquidity window compared to the main Korea Exchange (KRX), which trades from 9:00 AM to 3:30 PM. However, pre-market liquidity is extremely thin.
At 8:00 AM local time on July 28, as NXT opened, an order for SK Hynix stock was executed at 1,272,000 Korean won—precisely hitting the daily lower limit. This represented a drop of approximately 29.96% from the previous day's close of 1,785,000 won. With virtually no buy orders at that time, this single-share trade became the first reference price on the exchange.
Although the price returned to normal levels around 1.7 million won within about two minutes, it was too late. The oracle used by the xyz:SKHYNIX contract had updated the price about four seconds after NXT opened, lowering the reference price from $1131.40 to $954.99, a drop of 15.6%. Approximately 2.7 seconds later, the forced liquidation process began, pushing the on-chain execution price down to as low as $900.
Notably, several hours after the event, SK Hynix stock did experience a real decline of about 15% in the officially opened market, closely matching the magnitude of the flash crash. This coincidence made the anomalous price appear plausible at the time.
Furthermore, SK Hynix was already part of a broader sell-off in AI memory stocks. On that Tuesday (July 28), the Korea Composite Stock Price Index (KOSPI) closed down about 10%, adding to the confusion of the price signal.
Complete Picture of the Liquidations: 960 Accounts, $57.4 Million
According to MarketsAlpha’s on-chain analysis, the final profit and loss data for this event is as follows:
960 long accounts were forcibly liquidated.
The total size of the liquidated positions was approximately $57.4 million.
Traders suffered actual losses of about $17.3 million.
The liquidation triggered the Auto-Deleveraging (ADL) mechanism, with 100 profitable short accounts collectively gaining approximately $10.8 million.
The largest single account profit was $2.55 million, and the largest single account loss was $2.05 million.
It is worth noting that data from the enterprise-level blockchain data platform Allium largely aligns with these figures, estimating actual losses of about $17.4 million and over 900 affected users. However, neither Hyperliquid nor Trade.xyz has officially confirmed this data.
Why the Price Drop Was 17.9% Instead of 28.7%
Although the underlying price signal showed a drop of nearly 29%, the actual decline in the xyz:SKHYNIX contract was about 17.9%. This was not an accident but the result of a "price discovery boundary" mechanism in the Trade.xyz contract design.
According to Trade.xyz's public specifications, xyz:SKHYNIX has a 10% cap on instantaneous price movement and allows for one reset. With both layers, the hard upper limit for the mark price drop is approximately 19%. The final 17.9% decline fell within this limit, meaning the barrier mechanism absorbed about 11 percentage points of the price shock.
However, while protecting the market, this mechanism also left enough room for leveraged long positions to be liquidated. A maximum drop of 19% was sufficient to trigger forced liquidations of many long positions using significant leverage.
Another factor that amplified losses was the margin mode. xyz:SKHYNIX uses cross margin, while Samsung and Hyundai perpetual contracts on the same platform use isolated margin. Cross margin means that a losing position can use collateral from other positions in the same account, expanding the impact of a single event.
Why Hyperliquid Distanced Itself from Responsibility
After the event, a Hyperliquid team member and co-founder/core developer, known by the nickname "iliensinc," responded to questions from affected users in the project's Discord channel. Their stance was based on structural arguments. iliensinc wrote:
"Hyperliquid is a permissionless blockchain. Different teams can deploy and operate markets on Hyperliquid as an infrastructure layer... The XYZ team is investigating this, and once a conclusion is reached, it will be shared promptly."
The key to this distinction lies in the HIP-3 framework. Under this framework, the market operator (Trade.xyz) is responsible for pushing the mark price, oracle price, and external price inputs. Hyperliquid provides only one of the three price components. iliensinc explained with a simple example:
If the median of the latest on-chain transaction price, the best bid, and the best ask is 100, and the operator pushes prices of 150 and 151, the final mark price will be 150—the operator’s data carries decisive weight.
This means that control of the price oracle in this event rested entirely with Trade.xyz, and Hyperliquid was technically unable to intervene.
The Compensation Dilemma: A Useless Penalty Mechanism
The reality for affected traders is that even if the existing mechanism were fully executed, they would likely receive no compensation.
Under the HIP-3 rules, market deployers must continuously stake 500,000 HYPE tokens, worth approximately $27.4 million at Tuesday’s prices. Validators can vote to burn them using their staking weight. Conditions for triggering penalties cover malicious acts and operational errors, including cases where "contract specifications with design flaws were faithfully executed."
However, the penalized staked tokens are directly burned, not distributed to the affected users. Even if full penalties are triggered, the 960 liquidated accounts will receive nothing.
Furthermore, the automatic review mechanism for validators has a trigger threshold: it only activates automatically when the external price fluctuates by more than 50% from the day's opening price. The price movement in this event did not reach that threshold.
Currently, Trade.xyz has not released any post-event analysis report or proposed any compensation plan.
Industry Warning: Structural Vulnerabilities of On-Chain Traditional Asset Derivatives
This event has exposed the deep-seated contradictions of perpetual contract products in the crypto market.
Jordi Alexander, founder of digital asset hedge fund Selini Capital, compared users of such products to "people standing around a blackjack table, betting on the direction of the table," rather than genuine participants in the underlying market.
Tian Zeng, CEO of crypto hedge fund Third Eye, pointed out: "Typically, most exchanges use multiple pricing sources. Relying on a single source can be very dangerous."
He also stated that even with multiple data sources, "considering the leverage ratios of some traders, liquidations can still be triggered." He characterized this event as "part of the construction process for the nascent but rapidly growing market of on-chain traditional finance perpetual contracts."
Several time points will determine the future direction of this event: the contract deployer must hold the 500,000 HYPE stake for at least 183 days after launch. The staked tokens must go through a 7-day unstaking queue, so the window for validator action is currently open.
On the regulatory front, Trade.xyz met with crypto regulators from the U.S. Securities and Exchange Commission (SEC) alongside Hyperliquid's policy team this month. This event could further attract regulatory attention.
This event has also prompted a re-evaluation of Hyperliquid's previous controversial precedents.
During the JELLY token delisting incident in March 2025, Hyperliquid was criticized for centralization when it forcibly settled positions at a self-determined price. Now, in the face of user losses, the platform is refusing to intervene, citing its "permissionless infrastructure"—a starkly opposite stance.
Analysts point out that the core risk revealed by this event is not a universal problem with oracle mechanisms but a more specific design flaw:
For assets like SK Hynix, which can form a reference price during extremely thin pre-market trading, is a 19% maximum allowable price fluctuation reasonable?
A single share trade in a nearly empty market was enough to trigger tens of millions of dollars in liquidations.
Comments