Hyperliquid States SK Hynix Perpetual Contract Operated Independently by Trade.xyz, Pinning Incident Under Investigation
Hyperliquid responded to the "pinning" incident of the SK Hynix perpetual contract, stating that the current HIP-3 perpetual contract market adopts a "builder deployment" model, where Hyperliquid serves only as a permissionless blockchain infrastructure layer and does not directly operate specific contract markets.
The official statement indicated that the xyz:SKHYNIX perpetual contract is deployed and operated by the Trade.xyz team on Hyperliquid, which is responsible for oracle definitions, contract parameters, and price source configurations; the Trade.xyz team has initiated an internal investigation and will provide updates on abnormal market conditions and liquidation situations once conclusions are reached.
At the market mechanism level, the HIP-3 structure delegates the listing and risk control rights of perpetual contracts to the deploying party: on-chain matching and settlement are uniformly executed by Hyperliquid's core engine, but specific underlying assets, oracles, and leverage limits are customized by each team. In the event of extreme prices or pinning, the market deploying party is primarily responsible and faces reputational pressure, and their staked assets and future fee income may also face penalties or adjustments.
Source: Public Information
ABAB AI Insight
Historically, Hyperliquid has attempted to achieve more thorough decentralization at the contract level by transferring the "creation and operation rights of perpetual contracts" from the official to market deployers through HIP-3: the official is responsible for the on-chain high-performance matching and settlement engine, while each team deploys its own perpetual market as needed—including stocks, RWA, and alternative assets; this transforms Hyperliquid from a single contract platform into a foundational financial infrastructure, and the SK Hynix contract pinning incident is the first risk sample exposed by this "decentralized listing right" under extreme market conditions.
In terms of capital pathways, HIP-3 effectively splits the "exchange business" between market deployers and protocol parties: deployers must stake a large amount of HYPE to gain market creation rights and earn income through fee sharing, branding, and traffic acquisition; the protocol collects basic fees and maintains system security through unified matching and settlement. When a market (such as SKHYNIX perpetual) experiences a crash and large-scale liquidation due to oracle anomalies or pre-market quote distortions, the protocol can emphasize that it is merely executing the prices and parameters defined by the deploying party, which economically locks more risk and responsibility on the deploying party and its staked assets—deployers enjoy revenue sharing from "opening exchanges" but must also face the consequences of "mismanaging oracles or risk parameters leading to staked assets being penalized and reputational damage."
In terms of industry and historical comparisons, this structure is similar to deployed leverage protocols on Ethereum: the main chain provides settlement and security, while the specific market parameters and oracles are the responsibility of the protocol team or operators; the difference is that Hyperliquid further opens "market-level exchange rights" to any team that meets the staking threshold, allowing them to create independent order books and risk parameters under the same matching engine. This essentially represents a "exchange factory" model— the pinning incident illustrates that this model has advantages in innovation and long-tail assets, but in extreme market conditions and oracle anomalies, it can make it difficult for users to distinguish between the responsibilities of "on-chain infrastructure" and "market operators."
Structurally, this response emphasizes that "the SKHYNIX market is deployed and operated by Trade.xyz," which is essentially a public statement of "responsibility attribution and pricing power division": Hyperliquid aims to maintain neutrality and technical credibility at the infrastructure layer, transferring more responsibility for price sources and settlement parameters to the deploying party; the deploying party, in turn, takes a higher fee share and brand premium economically, while also bearing more market risk control responsibilities legally and reputationally. Whoever controls the definition of the underlying asset and oracle effectively holds the pricing power and settlement logic of that market—the pinning incident reminds traders that when using such decentralized contract factories, the risk assessment target is not just the protocol itself, but also the technical capabilities, oracle choices, and risk culture of the specific deploying team.
ABAB News · Cognitive Laws
Decentralized listing rights do not mean no market makers, but rather a shift from platform market makers to market deployer market makers.
When exchanges serve as infrastructure, the responsibility for oracles and parameters naturally falls on those who open the market.
You are looking at the same matching engine, but the real determinant of liquidation fate is who is behind writing that pricing formula.