Trading mechanics
GMX order types explained
4 min read · Fact-checked July 26, 2026 · gmxreferralcodes.com editorial team
GMX supports market, limit, stop market, take-profit, stop-loss and TWAP orders. The labels are familiar, but a trigger order on an oracle-based perpetual DEX does not behave exactly like an order resting in a centralized order book.
A GMX order must satisfy its trigger condition, have valid signed prices and pass on-chain simulation when a keeper attempts execution. Understanding those gates is more useful than memorizing the button names.
Key takeaways
- GMX orders execute from oracle prices through keepers, not against a visible central order book.
- Limit, stop, TP/SL and TWAP orders are not guaranteed to execute.
- A stop-loss should have space from the liquidation price and cannot replace prudent leverage.
- TWAP can reduce the impact of a large order but each part has separate execution conditions.
- Review pending orders after any material position or collateral change.
Market orders
A market order asks for execution at the next available oracle update within the allowed-slippage constraint. It does not fill against a visible stack of bids or offers. The interface estimates the result using current market information, but the final execution happens after submission.
Before sending a market order, inspect the expected fee, allowed slippage, collateral spread, leverage, liquidation price and net price impact. A market label means immediate intent, not a guaranteed exact chart price.
Limit and stop market orders
A limit increase order is intended to open or add to a position at a more favorable trigger price. A stop market increase order is intended to enter after price moves through a less favorable trigger, often for momentum or breakout setups. GMX evaluates the relevant minPrice or maxPrice according to the order direction.
These orders are not guaranteed. The price may never satisfy the condition, signed prices can be unavailable, liquidity or leverage constraints can fail, or the execution transaction can revert. Unlike a resting order-book limit, passing through a visible chart level does not by itself prove that an on-chain fill occurred.
Take-profit and stop-loss
Take-profit and stop-loss orders decrease an existing position when their trigger conditions are met. You can attach basic TP/SL when opening a trade or create multiple partial decreases afterward from the Positions list.
A stop-loss is not a guarantee against liquidation. If a fast move makes the position liquidatable before the stop executes, liquidation may happen first. GMX attempts eligible StopLossDecrease orders before liquidation in certain conditions, but execution can still fail. Leave a meaningful buffer and use lower leverage rather than placing the stop almost on the liquidation price.
TWAP orders
TWAP divides an increase, decrease or swap into multiple parts executed over time. It can reduce the effect of a large order on net price impact, especially when a single operation would materially worsen market balance.
The total execution fee is paid upfront and divided among the parts. A part can freeze if its allocated execution fee becomes insufficient after network costs rise. TWAP orders cannot be edited; changing one requires cancellation and creation of a new order. Individual parts can also fail because of liquidity or leverage limits.
Trigger prices, oracle sides and order management
GMX receives a minPrice and maxPrice. Trigger evaluation uses a different side depending on the order type and whether the position is long or short. This protects the pool from a trader choosing the most favorable edge of the oracle spread, but it can make a trigger appear different from a chart midpoint.
Monitor pending orders in the Orders tab and cancel orders you no longer need. After changing collateral or position size, re-check whether old TP/SL amounts and trigger distances still make sense. Auto-cancel settings can remove related orders after a position closes, but traders should verify the resulting state.
GMX order types and execution limits
| Order | Typical use | Guaranteed? |
|---|---|---|
| Market | Open, increase, decrease or close at the next valid execution | No; acceptable price and on-chain checks still apply |
| Limit increase | Enter at a more favorable trigger | No |
| Stop market increase | Enter after price crosses a less favorable trigger | No |
| Take-profit / stop-loss | Decrease a position after a trigger | No; liquidation can occur first |
| TWAP | Split a larger operation over time | No; individual parts can freeze or fail |
Primary sources
These sources were checked on July 26, 2026. Protocol parameters can change.
Read our verification methodology →Trade GMX with 10% off eligible position fees
Use referral code PRO for the tier-2 10% discount on eligible opening and closing position fees.
Trade now with the codeFrequently asked questions
Are GMX limit orders guaranteed to fill?
No. The oracle trigger must be satisfied and the order must pass price, liquidity, leverage, execution-fee and on-chain validation checks when a keeper attempts execution.
Can a GMX stop-loss fail before liquidation?
Yes. A rapid move can make the position liquidatable before the stop-loss executes, and execution can also fail because of missing signed prices, insufficient liquidity or validation errors.
Why use a TWAP order on GMX?
TWAP splits a large operation into smaller parts over time. That may reduce adverse net price impact, but it adds multiple execution events and is not guaranteed to complete.
Can I edit a GMX TWAP order?
No. GMX documentation states that a TWAP cannot be edited. Cancel the remaining parts and create a new TWAP with the desired settings.
Continue learning