Pre-IPO perp markets on Hyperliquid are growing, but oracle misconfiguration—like misreading stock splits—can cause mass liquidations; Redstone's oracle stack is designed to prevent these failures.
DeFi & Yields ·
Pre-IPO perpetual markets on Hyperliquid have grown in activity, but the space faces critical infrastructure risks tied to how price data is configured. In May, a misconfiguration of the oracle feeding the $SPCX perp market caused it to drop 45 percent in under 30 minutes, as the system misinterpreted a routine stock split as a price collapse. That cascade liquidated 400 traders and erased $1.5 million in notional value.
The HIP-3 framework governing Hyperliquid perp markets grants deployers broad latitude to launch contracts on nearly any asset and select their own oracle provider. This flexibility creates a single point of failure: one misconfigured price feed can trigger cascading liquidations across an entire market. Stock splits and repricing events—common in pre-IPO assets—are particularly prone to misinterpretation if the oracle lacks separation between genuine price changes and mechanical corporate actions.
Redstone has built an oracle stack specifically for HIP-3 markets designed to distinguish price feeds from mechanical resets like splits, using a primary and fallback system to catch these errors. Whether this architecture becomes standard across deployer choices, or whether similar incidents will recur as pre-IPO perp volume expands, remains unresolved.