GMX

GMX is a decentralized spot and perpetual exchange launched in 2021 that allows traders to swap tokens and open leveraged long and short perpetual futures positions directly from a connected Web3 wallet on Arbitrum and Avalanche. The protocol operates without requiring users to deposit funds into a centralized custodian — trades are executed and settled on-chain against GMX liquidity pools, with position state, collateral balances, and funding accruals recorded on the respective network. GMX is accessible at gmx.io and uses a pool-based liquidity model where GLP and GM token holders provide the counterparty liquidity against which traders open leveraged positions

GMX has evolved through two major protocol versions — the original GMX V1 architecture using GLP as a single multi-asset liquidity pool, and the GMX V2 architecture using isolated GM pools for individual markets alongside the gmx-synthetics smart contract infrastructure. The GMX token is used for protocol governance participation and for staking to earn a share of protocol fees generated by trading activity across supported markets on Arbitrum and Avalanche. Open-source smart contract repositories are publicly available on GitHub under the gmx-io organization, including the core gmx-contracts and gmx-synthetics repositories, with documentation maintained at docs.gmx.io

The primary interaction with GMX begins at gmx.io, where users connect an EVM-compatible wallet on the Arbitrum or Avalanche network to access the trading interface. Traders can execute spot swaps between supported tokens at oracle-determined prices, or open leveraged long and short perpetual futures positions by selecting a market, a position direction, a collateral token, and a leverage level. Positions are opened on-chain against the corresponding GMX liquidity pool, with the position's collateral, leverage ratio, entry price, and liquidation threshold recorded on-chain and accessible through the GMX interface or directly via the deployed contract state

GMX liquidity is provided by pool token holders who deposit supported assets into GLP (V1) or GM (V2) pools. In the GMX V1 architecture, GLP is a composite basket of assets including stablecoins and crypto assets that serves as counterparty liquidity for all V1 markets on a given chain. In the GMX V2 architecture, GM pools are isolated per market — for example, a BTC/USD GM pool holds BTC and USDC as the collateral backing the BTC perpetual market — allowing liquidity risk to be contained per market rather than spread across a single shared pool. Liquidity providers who hold GLP or GM tokens earn a portion of the fees generated by trading activity routed through the respective pool

The GMX V2 architecture introduces isolated market structures through the gmx-synthetics smart contract system, published as open-source at github.com/gmx-io/gmx-synthetics. Each V2 market is backed by its own dedicated GM pool holding the long and short collateral assets for that market, which isolates liquidity risk and allows individual markets to be configured with independent parameters including leverage limits, fee rates, and oracle price sources. This isolated pool model contrasts with the shared GLP pool of V1, allowing V2 markets to be added or adjusted without changing the parameters of existing markets and allowing liquidity providers to choose specific market exposure rather than a composite basket

GMX V2 uses Chainlink Data Streams as the oracle pricing layer for perpetual market execution, providing low-latency price updates sourced from Chainlink's decentralized oracle network for each supported market. Chainlink Data Streams deliver signed price data that keepers use to execute pending orders and update position prices, enabling GMX to price perpetual entries, exits, and liquidations against an externally validated reference price rather than relying solely on on-chain AMM spot prices. This oracle architecture is documented in the GMX technical documentation at docs.gmx.io and is part of the V2 design to reduce oracle manipulation risk in the perpetuals execution path

Leveraged trading on GMX allows users to open positions with collateral that is a fraction of the total position size, with GMX V2 supporting configurable leverage levels for each market up to the protocol's defined maximum. Long positions can be opened with the market's long token as collateral — for example, ETH as collateral for an ETH/USD long — while short positions can be opened with a supported stablecoin as collateral, allowing traders to express both directional views on asset prices. Open positions accrue borrowing fees charged against the position's collateral at a rate based on the pool's utilization, along with a price impact applied at entry and exit based on the size of the position relative to the pool's available liquidity depth

The GMX token's utility within the protocol includes fee sharing for staked GMX holders and governance participation. GMX holders who stake their tokens receive esGMX — an escrowed form of GMX — and multiplier points as additional staking rewards, alongside a portion of ETH or AVAX fees generated by trading activity on the respective chain. Protocol governance decisions including market listings, fee parameter changes, and protocol upgrades are subject to community discussion, with protocol development coordinated through the GMX community channels referenced at docs.gmx.io/docs/community

GMX supports a range of spot and derivatives use cases across Arbitrum and Avalanche: traders use the gmx.io interface to execute leveraged long and short perpetual futures on supported crypto asset pairs without depositing into a centralized exchange; spot traders swap between supported tokens at oracle-based prices without requiring a full AMM liquidity pool for each pair; liquidity providers deposit assets into GLP (V1) or GM pools (V2) to earn trading fees and borrowing fees as the counterparty to trader positions; GMX token holders stake their GMX to earn protocol fee distributions and esGMX staking rewards; and developers build trading integrations, analytics tools, and automated trading strategies using the open-source gmx-contracts and gmx-synthetics repositories along with the integration documentation at docs.gmx.io

Developer integration with GMX is supported through the documentation at docs.gmx.io and the open-source smart contract repositories at github.com/gmx-io, including the core gmx-contracts repository at github.com/gmx-io/gmx-contracts and the V2 gmx-synthetics repository at github.com/gmx-io/gmx-synthetics. Both repositories include ABI definitions and contract source code for Arbitrum and Avalanche deployments, allowing developers building on-chain integrations to interact directly with GMX market contracts for position management, fee queries, and liquidity pool interactions without depending on a centralized API endpoint. Developers integrating GMX pricing or building trading bots can reference the oracle and keeper documentation to understand how Chainlink Data Streams deliver prices to V2 market contracts and how keeper execution triggers order fills and liquidations through the synthetics contract system

GMX maintains security documentation at docs.gmx.io/docs/security, which covers the protocol's security model, audit history, and responsible disclosure information for reporting vulnerabilities. All core GMX smart contract source code — including the gmx-contracts and gmx-synthetics repositories — is publicly available on GitHub under the gmx-io organization for independent review and verification. As a non-custodial protocol, GMX does not hold trader funds in a centralized account — collateral is deposited into on-chain smart contracts and positions are settled atomically through contract execution, with all state changes verifiable on-chain by any external observer. Users evaluating GMX should review the security documentation, inspect the relevant contract code for their target chain, and assess the oracle trust assumptions of the Chainlink Data Streams pricing layer before opening leveraged positions

GMX provides decentralized spot and perpetual trading infrastructure on Arbitrum and Avalanche through two protocol versions — V1 with shared GLP pool liquidity and V2 with isolated GM market pools powered by Chainlink Data Streams oracles and the open-source gmx-synthetics contract infrastructure. Published security documentation at docs.gmx.io/docs/security, open-source repositories at github.com/gmx-io, and protocol fee sharing for GMX stakers give developers and traders structured access to GMX's trading mechanics and governance resources. Teams and users evaluating GMX should review the documentation at docs.gmx.io, the gmx-synthetics repository at github.com/gmx-io/gmx-synthetics, and the security documentation to understand V2 market structure, oracle pricing mechanics, and pool liquidity risk before trading or providing liquidity through the protocol