Skip to content
Blockchain LabTHE VENTURE STUDIO

LibraryMarkets2021Design paperCorpus record

GMX: A Decentralised Perpetual Exchange

GMX. GMX.

GMX v1 pools liquidity provider assets into a vault that takes the other side of leveraged trades. Prices come from an oracle. Traders pay fees to the pool.

A reading of the public document. Not a copy of it, and not a claim about a later network that reused the name.

A perpetual that says 'no order book' still has a counterparty. Name it, and name the price.

The five-minute read

The defect

A perpetual future needs a counterparty. An order book of professionals does not appear just because a chain exists.

The rule

GMX v1 pools liquidity provider assets into a vault that takes the other side of leveraged trades. Prices come from an oracle. Traders pay fees to the pool.

How it is put together

The pool is the counterparty, not another trader. Oracle prices, not an on-pool curve, mark the position. Leverage is a loan against the pooled assets.

Where the claim stops

The docs are a product description, not a proof that the pool cannot be drained.

One action, walked through

  1. A trader posts margin.
  2. The position's profit and loss is computed from oracle moves.
  3. Funding and fees are paid to the pool that warehouse the risk.
  4. Who loses when a trader wins?

The argument, unpacked

Why it is still on the desk

A perpetual that says 'no order book' still has a counterparty. Name it, and name the price.

After the text

Later GMX versions split markets. The v1 idea, a pooled warehouse plus an oracle, is the citation.

What has to be true

  • The docs are a product description, not a proof that the pool cannot be drained.
  • Oracle failure is the market's failure.
  • v2 changed the liquidity structure. Do not cite v1 for v2.

What happened after the paper

Later GMX versions split markets. The v1 idea, a pooled warehouse plus an oracle, is the citation.

What to check before you use the idea

  • Who loses when a trader wins?
  • Which oracle updates the price?
  • What stops one trade from taking the whole pool?

Terms

Warehouse
The pool that takes the other side of every trade.
Oracle price
A price from outside the pool, not the pool's own curve.

The problem the paper names

A perpetual future needs a counterparty. An order book of professionals does not appear just because a chain exists.

What the design proposes

  • The pool is the counterparty, not another trader.
  • Oracle prices, not an on-pool curve, mark the position.
  • Leverage is a loan against the pooled assets.

How the mechanism is specified

  • A trader posts margin.
  • The position's profit and loss is computed from oracle moves.
  • Funding and fees are paid to the pool that warehouse the risk.

What this page does not treat as proven

  • The docs are a product description, not a proof that the pool cannot be drained.
  • Oracle failure is the market's failure.
  • v2 changed the liquidity structure. Do not cite v1 for v2.

Why a venture studio still reads it

A perpetual that says 'no order book' still has a counterparty. Name it, and name the price.

This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.

Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.