gmx

Create a MarketIncrease order by batching sendWnt (execution fee plus collateral) and createOrder into a single multicall on the ExchangeRouter. Leverage is implicit: it equals sizeDeltaUsd divided by collateral value, with sizeDeltaUsd using 30-decimal precision.

V1 used a single shared GLP pool for all markets, while V2 uses isolated pools per market with separate GM tokens. GLP is deprecated on V2, and each market like ETH/USD has its own pool with distinct long and short collateral tokens.

GMX orders are asynchronous: keepers execute them in a separate transaction using Chainlink Data Streams prices. Common causes are insufficient execution fee, keeper backlog during volatility, or the price moving past your acceptablePrice causing auto-cancellation.

Approve ERC-20 tokens to the Router contract (0x7452c558d45f8afC8c83dAe62C3f8A5BE19c71f6 on Arbitrum), not the ExchangeRouter. The ExchangeRouter calls the Router internally to transfer tokens, so approving the wrong contract causes TokenTransferError.

Yes, GMX V2 is also deployed on Avalanche with its own ExchangeRouter, Reader, and DataStore addresses. Avalanche has fewer markets than Arbitrum, and all addresses should be verified against the official docs before use.

GMX uses 30-decimal precision for USD values, not the standard 18 decimals. A $5,000 position must be encoded as 5000 * 10^30; using 18 decimals creates positions orders of magnitude off and can trigger MaxLeverageExceeded errors.