Ventuals has acknowledged an incident on its SPACEX market after an offchain data provider returned incorrect pricing data, causing the market’s oracle price and mark price to move sharply. The move triggered liquidations for some user positions, turning a private-market pricing error into a live derivatives risk event.
The team said it has taken immediate steps to prevent the same issue from affecting any of its other pre-IPO markets. Ventuals is also reviewing the impact on affected users and said appropriate compensation is being evaluated.
This was not a SpaceX valuation shock, IPO update, funding round, or company-specific news event. It was a pricing-infrastructure failure inside a market built to track SpaceX’s implied private valuation. That distinction is important because the SPACEX market does not represent direct ownership in SpaceX shares.
What Actually Broke
On Ventuals, the SPACEX market is a private-company valuation perpetual. Traders are not buying SpaceX stock, shareholder rights, or SPV interests. They are trading a synthetic perp tied to the company’s implied valuation, with 1 SPACEX representing $1 billion of company valuation for easier readability.
That structure depends heavily on the oracle. Ventuals uses a weighted oracle built from two components: an external private-market valuation input and a 2-hour incremental EMA of the market’s own mark price. The external input comes from Notice, whose private-market pricing model incorporates financing rounds, 409A appraisals, mutual fund marks, verified trades, bids and offers, and peer-company comparisons.
The incident appears to have started when that offchain input returned incorrect data. Once the bad value entered the oracle system, the SPACEX oracle moved dramatically. Because Ventuals’ mark price is tied to oracle constraints and is used for margining, unrealized PnL, stop and limit triggers, funding, and liquidations, the error could quickly affect leveraged positions.
A public trader flagged shortly before the team’s statement that the Ventuals SPACEX contract appeared broken, with mark price sitting at roughly half of oracle price. Ventuals has not yet released a full postmortem, exact price path, liquidation count, loss estimate, or compensation formula.
Why The Liquidations Happened
The liquidation path is the most important part of the story. In a normal spot market, a bad external quote might distort a reference price. In a leveraged perp market, the same problem can directly change account equity, margin health, and liquidation thresholds.
Ventuals’ own market design makes mark price the operational reference for liquidation. If the mark price moves sharply against a trader, the system can treat that position as undercollateralized even if the underlying private company’s real-world valuation did not change. That is exactly why oracle design is a critical risk layer in synthetic RWA markets, pre-IPO perps, prediction markets, and other products where there is no deep, continuous spot market underneath.
The SPACEX market is especially sensitive because SpaceX is private. There is no public stock exchange price, no official intraday tape, and no liquid spot market that can instantly anchor the contract. Ventuals tries to solve that by blending private-market valuation data with onchain price discovery. The incident shows how fragile that model can become when one component produces a wrong value.
Pre-IPO Perps Face A Bigger Trust Test
The incident lands during a wider boom in tokenized private-market exposure. Crypto markets have already shown strong demand for AI and pre-IPO narratives, including Anthropic’s implied valuation crossing $1 trillion on Jupiter and the later Anthropic PreStocks selloff after transfer-risk warnings. The same theme runs through Ventuals: traders want access to companies that remain private for longer, while crypto infrastructure tries to turn those valuations into liquid 24/7 markets.
The problem is that private-company valuation is not the same as public equity pricing. Private marks can be delayed, negotiated, restricted, model-driven, or based on sparse secondary-market activity. When those marks feed leveraged derivatives, the risk moves beyond simple valuation disagreement. It becomes liquidation risk.
This is also why oracle incidents sit beside broader DeFi security concerns. Recent crypto security coverage has repeatedly shown that failures around oracles, cross-chain accounting, admin controls, and liquidity assumptions can create losses even when the visible frontend appears normal. Ventuals’ SPACEX incident is not being described as an exploit, but it still exposed the same core dependency: automated markets are only as safe as the data and control systems feeding them.
Compensation Details Remain Unclear
Ventuals has confirmed that some user positions were liquidated and that compensation is under review. The team has not yet published the affected user count, total liquidation value, incorrect oracle level, duration of the bad data window, or whether compensation will cover full realized losses, partial losses, liquidation penalties, funding effects, or missed recovery.
Those details will determine whether the incident becomes a short-lived oracle fault or a larger trust issue for pre-IPO perps. The immediate fix may prevent the same data path from repeating across other markets, but traders will still want a clear postmortem showing what failed, how the guardrails changed, whether bad prints were isolated, and how compensation will be calculated.
The SPACEX market incident gives Ventuals a direct test of user protection in a new category of crypto derivatives. Pre-IPO perps can give traders exposure to private-company valuation narratives, but the trade-off is now visible: when the reference asset has no liquid public market, oracle accuracy, mark-price controls, and liquidation safeguards become the real product.
Be the first to comment