A venue-specific limit-order instruction intended to prevent immediate matching so the order rests on the book if accepted. Exact cancellation, rejection, adjustment, and fee behavior depend on the venue.
Supports: Hyperliquid defines Post Only (ALO) as an order added to the book rather than executing immediately and documents venue-specific order handling.
Supports: Hyperliquid documents that ALO limit orders are canceled instead of immediately matching, while other time-in-force choices have different behavior.
Post-only semantics are venue-specific and can cancel, reject, or otherwise handle an immediate match
If accepted, it rests first but can remain unfilled, fill partially, be canceled, or lose priority
Maker fee schedules and rebates are not universal and must be checked per product and account
Post-only does not guarantee execution, price improvement, profit, or protection from market risk
A user checks that the selected venue cancels a post-only order that would immediately match, verifies the product's maker fee schedule, and submits a valid limit order. They monitor its accepted, canceled, partial-fill, and queue state rather than assuming the instruction produces a rebate or an execution.
A layer-1 blockchain whose documentation describes HyperCore spot and perpetual order books and HyperBFT consensus. Product availability, latency, fees, liquidity, and risk remain deployment- and market-specific.
The smallest permitted price increment for an order on a specific trading venue and market. It is a venue rule, not a universal property of the asset or a measure of execution quality.
An execution method that schedules parts of an order across a defined time interval. Its schedule, sizing, slippage controls, fill behaviour, and result are venue- and configuration-specific.
The difference between a quoted or expected trade result and the result that can execute under the protocol's state and limits.
Explore all our strategic guides about Trading to take your operations to the next level.
View all articles