Solidus Flags Over $170 Million in Hyperliquid Oil Orders as Suspected Spoofing

What the report says happened

Odaily, citing Bloomberg, says Solidus examined a trader who placed large orders on one side of the order book, canceled them quickly and executed trades on the other side. The account describes suspected spoofing during a period of sharp international oil-price movements on March 8–10. The more than $170 million figure refers to unusual orders across two accounts; it should not be read as $170 million of completed purchases or sales. The reported trading pattern.

One example in the report involves the rapid cancellation of about $17 million of sell orders alongside execution of about $425,000 of buy orders. Odaily says the Brent crude perpetual price moved noticeably around the cancellation. Its brief does not provide a complete transaction sequence or enough price observations to calculate the size of that move. The reported $119,000 profit is an attributed research finding, rather than a profit calculation reproduced here.

The two amounts describe different actions. A canceled sell order did not become a completed sale merely because it appeared on screen. The buy amount describes executed orders in the example. Adding the figures together and calling the result trading volume would lose that distinction. Likewise, the $17 million example is part of the account of the broader activity, not a separate loss to be added to $170 million.

All incident figures in the table come from the same Odaily brief. They are not separate confirmations of the event.

What Hyperliquid and the contract issuer said

According to Odaily, Hyperliquid Labs responded that orders, cancellations and executions are recorded publicly on-chain and can be examined in real time. The brief also says the relevant contract issuer, Trade.xyz, described order limits and continuous monitoring. These are responses attributed to the companies by the report. They do not establish what any particular trader intended. The reported responses.

Public records and an intent finding answer different questions. An order history can show the sequence an analyst examined. A statement about why someone placed an order needs additional support. The report explicitly leaves identity and subjective manipulative intent unconfirmed, so the allegation should remain an allegation when shared or used in a trading discussion.

The brief supplies no current order-book snapshot. It does not establish today's spread, executable size, account eligibility or trading status for a particular oil contract. Before changing a live order, work from that exact contract's current screen and your own order history. A historical episode cannot supply a current executable quote.

SponsoredHyperliquid

Partner rebate share30%Up to

Check regional eligibility and account terms

✓Code applied automatically by the sign-up link: NEXU888

Sign up on Hyperliquid →CodeNEXU888Copied

The order choice that matters to an existing trader

Hyperliquid's official documentation defines a market order as one that executes immediately at the current market price. A limit order executes at the selected limit price or better. For a reader unsettled by a large displayed order, that is a useful place to begin: decide whether the priority is immediate execution or a specified price before submitting anything. Source: Hyperliquid Docs, Trading, Order types.

For a limit order, write down the selected price and intended size before confirming. Then inspect whether the order filled, remains open or was canceled. The documentation's Good Til Cancel option rests on the book until filled or canceled. A resting order therefore needs a later status check; seeing it accepted does not establish that the position has changed.

Post Only, also called ALO in the documentation, adds an order to the book without executing immediately. It executes only as a resting order. Immediate or Cancel, or IOC, is canceled if not immediately filled. Readers reviewing their own activity should keep these instructions attached to the record. A cancellation under a selected order instruction cannot, by itself, establish the same allegation as the pattern described by Solidus.

A trader who wants to reduce an existing position should check the Reduce Only instruction. Hyperliquid describes it as reducing a current position rather than opening a new position in the opposite direction. Record the existing position and the intended reduction together. This is a specific check available from the opened order documentation; the news brief supplies no account-level instruction for an individual reader.

Check the trigger as well as the price

Hyperliquid distinguishes a Stop Market order, which activates a market order at the selected trigger, from a Stop Limit order, which activates a limit order. Its documentation also distinguishes Take Market and Take Limit orders on the same basis. A trigger reaching its selected level and an order executing are separate events in the documented sequence. The official Order types page describes these conditional instructions.

When reviewing an existing conditional order, record its trigger, its resulting order type and any limit price. That makes a later account-history check useful: did the condition activate, and what happened to the order afterward? Looking only at the trigger field leaves out the execution instruction. The historical $17 million cancellation example does not tell a reader which conditional instruction to choose today.

The official page says take-profit and stop-loss instructions are automatically market orders, with an option to set a limit price and configure the amount of the position covered. Check those settings for the actual position rather than assuming a familiar label means the same submitted instruction in every case. Keep the confirmation and subsequent order status so a canceled instruction is not confused with a completed exit.

Splitting an order also requires a completion check

Hyperliquid documents TWAP as a large order divided into smaller suborders and executed at intervals. The page states a minimum interval of 30 seconds and a maximum slippage of 3% for suborders. Those are documented order parameters; they are unrelated to the percentage change in an underlying oil benchmark or to the profit allegation. The official Order types documentation supplies these TWAP parameters.

The page describes how a TWAP follows an execution target based on elapsed time, total running time and total size. If market conditions prevent suborders from filling, it can fall behind that target. Later suborders can become larger as it tries to catch up, subject to a constraint of three times the normal suborder size. The documentation says a TWAP may still finish without completing the full intended size.

For someone already using this instruction, check intended size against completed size when the running period ends. Then check the remaining position. The 3% suborder constraint should not be rewritten as a promise that the entire intended order will fill. The relevant evidence is the completed record for the reader's own order, not the presence of a large bid or offer elsewhere in the book.

The official page also describes an optional randomization setting that varies each suborder's size by up to 20% in either direction. If enabled, preserve that setting in the order record when reconciling individual fills. A set of unequal fills may reflect a selected instruction; the published news brief does not provide a method for classifying every unusual-looking order sequence as manipulation.

What remains unconfirmed

The news report does not provide the trader's verified identity, a finding of manipulative intent, a complete dataset for reproducing the profit estimate or a final enforcement outcome. These are the missing details that would let readers assess the allegation beyond the reported order pattern.

For the next update, the useful additions would be a published analysis with order identifiers and a reproducible sequence, a response addressing the particular accounts, or an official finding. Another headline repeating the same $170 million would not supply those missing details. Keep any subsequent claim attached to the document that actually adds it.

Questions the report can answer

Was $170 million stolen?

The accessible brief describes unusual orders totaling more than $170 million. It does not describe that amount as stolen funds, customer losses or completed trading volume. The reported profit is a different figure, about $119,000, attributed to Solidus.

Did this activity happen on October 29?

The brief was published at 00:46 SGT on October 29 and describes trading during March 8–10. The publication time and the activity period should remain separate when quoting the story.

Has manipulation been established?

The report calls the activity suspected spoofing and explicitly leaves the trader's identity and subjective intent unconfirmed. Its account of the companies' responses does not change that status.

For an existing Hyperliquid oil position, first match the contract name in your position record to the order you intend to change. Write down its size and whether the pending instruction is market, limit or conditional. Then compare completed fills with the remaining open order and position; if the aim is a reduction, check Reduce Only before confirming the replacement instruction. NexuAlpha's funding board and liquidation board provide separate market context; neither substitutes for the status of an order in your account.