A perpetual DEX is a decentralized exchange where traders open leveraged long or short positions on crypto with no expiration date — perpetual futures. The settlement, margining, and liquidations all happen on-chain. The two dominant designs are order-book (e.g., dYdX) and pool-based (e.g., GMX, Jupiter Perps), each with different trade-offs for traders and liquidity providers.
Key takeaways
- A perpetual DEX brings leveraged futures trading on-chain — no expiry, settled in stablecoins or the chain's native asset.
- Order-book perp DEXes match traders against each other; pool-based perp DEXes match traders against a liquidity pool.
- LPs (in pool-based designs) bear the net PnL of traders against the pool and earn fees and funding.
- Risks for traders include liquidation and oracle issues; for LPs, bearing trader profit and the structural risk of the pool.
The problem it solves
Perpetual futures dominate centralized crypto trading. Bringing them on-chain — with self-custody, transparency, and composability — was historically hard because order books are gas-expensive on Ethereum L1 and liquidations need fast oracles. Perp DEXes solve these problems in different ways, opening leveraged trading to anyone with a wallet.
How it works
Three pieces.
Order-book vs. pool-based
An order-book perp DEX (dYdX, Hyperliquid, others) matches traders against each other through an on-chain or partially-on-chain order book. A pool-based perp DEX (GMX, Jupiter Perps, others) pools liquidity and lets traders take leveraged positions against the pool. Order books offer tighter spreads when market-makers are active; pools offer consistent liquidity with LPs as the counterparty.
Funding rates
To keep the perpetual contract's price close to spot, traders pay or receive a periodic funding rate based on whether longs or shorts dominate. This applies on any perp design, centralized or decentralized.
Liquidation
If a trader's collateral falls below maintenance margin, the position is liquidated automatically. Liquidators (or in pool models the protocol) close the position and the trader pays a penalty.
Real use cases
- Leveraged exposure without a centralized exchange. Trade BTC or ETH long or short with leverage from your own wallet.
- Hedging spot positions. Use a short perp to offset a spot long.
- Earning fees as an LP. Provide liquidity to pool-based perp DEXes for trading fees and funding rate flows.
- Composable derivatives. Other protocols build vaults, leveraged tokens, and structured products on top of perp DEX infrastructure.
Risks worth knowing
- Liquidation risk for traders. High leverage means small price moves can liquidate the position; flash crashes amplify this.
- Oracle risk. Bad oracle data can wrongly liquidate users or distort funding rates.
- Pool risk for LPs. Net trader winnings come out of the LP pool; in trending markets, LPs can lose money even when traders are individually small.
- Smart-contract risk. Perp DEXes are complex; new versions and integrations expand surface.
- Chain-level risk. Outages, congestion, or sequencer issues on the host chain affect liquidations and execution.
None of this is financial advice — it is the context you need before trading or providing liquidity on a perpetual DEX.
Following perpetual DEXes with the right lens
Perp-DEX headlines move on protocol upgrades, large incidents (LP drawdowns, oracle issues), and broader regulatory or market-structure shifts. Each one matters differently for traders, LPs, and governance holders. Zippfeed surfaces perp-DEX-related headlines with sentiment and importance scoring across sources, so you can tell whether news is structural or noise. This is education, not financial advice.