
Derivatives / Multichain / GMX
GMX
A decentralized spot and perpetual exchange where GM and GLV liquidity pools take the other side of trades.
THE OVERVIEW
What GMX does
GMX is a decentralized spot and perpetual exchange on Arbitrum, Avalanche and MegaETH. Trading is powered by GM and GLV liquidity pools, and pricing comes from Chainlink Data Stream oracles so that liquidations occur at aggregated market prices rather than on momentary spread spikes. A GMX Account lets traders use the exchange from other supported chains. [1]
A GM pool consists of an index price feed, a long token and a short token, and may be backed by one or several tokens. A GLV pool aggregates multiple GM markets and rebalances liquidity between them based on utilization. Liquidity providers earn the majority of fees from trading, liquidations, borrowing and swaps simply by holding pool tokens, and they are the counterparty to traders: trader profit comes out of the pool’s value. [2]
Positions use linear, USD-based profit and loss with flexible collateral, and collateral may come from a connected wallet or a GMX Account balance. Fees differ between crypto markets and traditional-finance markets such as commodities and indices, and for those markets liquidation parameters can change between on-hours and off-hours sessions. [3]
IN PRACTICE
What people use it for
UNDERSTAND THE TECHNOLOGY
Key concepts
GM and GLV pools
Single-market pools and vaults that spread liquidity across several markets. [2]
Oracle pricing
Execution and liquidation prices come from aggregated exchange data rather than a single venue. [1]
Counterparty exposure
Liquidity providers gain when traders lose and lose when traders profit. [2]
MARKET CONTEXT
GMX market
$8.04-0.22% 24hPrice history, market data and signal →FOLLOW THE STORY
GMX news & coverage
Dextape matches publisher headlines and asset references. Related asset reporting may cover the wider ecosystem.
No recent matching coverage is available. Explore the news wire →
GO DEEPER
Official resources & sources
Dextape explanations based on the primary documentation below.