Module 7: Perpetual Futures
Decentralised Perpetual Exchanges
Chapter 13 of 14 · about 6 minutes
13.1 Perps without a company holding your money
After learning about FTX and exchange risk, Node asked an obvious question. "Can I trade perps without trusting a centralised exchange with my margin?"
"Yes," said Hash. "Decentralised perpetual exchanges have grown into some of the largest venues in crypto. You keep custody until you deposit margin into a smart contract, and every position is visible on-chain. But 'decentralised' changes the risks. It doesn't remove them."
13.2 What a decentralised perp exchange is
A decentralised perpetual exchange (perp DEX) lets users trade perpetual futures through smart contracts or a dedicated blockchain, rather than through a company's internal systems. Users typically connect a self-custody wallet (Module 2), deposit collateral, and trade.
| Centralised perp exchange | Decentralised perp exchange | |
|---|---|---|
| Who holds margin | The exchange company | Smart contracts or a protocol's chain |
| Account | Username, password, usually KYC | Wallet connection, often no KYC |
| Transparency | Positions private; exchange reports aggregate data | Positions and liquidations visible on-chain |
| Main counterparty risk | The company's solvency and honesty | Smart contracts, oracles, and protocol design |
| Typical access restrictions | Based on regulation and KYC | Often based on front-end restrictions by location |
13.3 Three main designs
1. On-chain order books. Some perp DEXs run a full order book, matching buyers and sellers like a centralised exchange. To make this fast enough, many run on their own specialised blockchains or high-throughput networks (Module 3, Chapter 9), with very fast block times. The user experience can feel very similar to a centralised exchange.
2. Oracle-based pool models. Traders trade against a shared liquidity pool, at prices supplied by oracles (Module 3, Chapter 12), rather than against other traders' orders. Liquidity providers deposit into the pool and act as the counterparty to all traders. When traders lose, the pool gains; when traders win, the pool pays.
3. Hybrid and other designs. Some combine off-chain order matching with on-chain settlement, or use automated market maker designs adapted for perps.
| Design | Price source | Who is the counterparty | Main risks |
|---|---|---|---|
| On-chain order book | Orders from traders and market makers | Other traders | Chain or validator centralisation, liquidity in smaller markets |
| Oracle-based pool | Oracles | The liquidity pool | Oracle manipulation, pool losses when traders win big |
| Hybrid | Off-chain matching | Other traders | Trust in the off-chain operator |
13.4 Transparency as a feature
On a perp DEX, positions are often fully visible on-chain. Anyone can see open interest, large positions, liquidation levels of specific wallets, and liquidations as they happen.
This transparency has led to a new kind of market watching. Very large positions on public perp DEXs sometimes attract attention, with other traders tracking specific wallets and their liquidation prices (Module 6, Chapter 9). It cuts both ways: transparency helps the market understand risk, but it also exposes large traders to others trying to push price toward their liquidation levels.
"So everyone can see where my liquidation price is," said Mint.
"On many perp DEXs, if they know your address, yes," said Hash. "For small positions, nobody cares. For large ones, it's a real consideration."
13.5 Risks specific to perp DEXs
| Risk | Example |
|---|---|
| Smart contract bugs | A flaw lets attackers drain margin or pools (Module 1, Chapter 4) |
| Oracle manipulation | An attacker manipulates a thinly traded token's price feed to profit from positions against the pool (Module 3, Chapter 12) |
| Liquidity pool losses | In pool models, a run of trader wins drains the pool, hurting liquidity providers |
| Thin markets | Small tokens with low liquidity are easier to manipulate, sometimes causing losses for the protocol |
| Validator or operator centralisation | A protocol's own chain may rely on a small set of validators or a single operator (Module 3, Chapter 13) |
| Bridging | Collateral often has to be bridged to the perp DEX's chain (Module 3, Chapter 10) |
| Governance and admin keys | Teams or governance may have powers to change parameters or pause markets |
| Front-end and access restrictions | Websites may block certain countries; check local rules |
Several perp DEXs have faced incidents involving manipulation of smaller markets, where traders exploited thin liquidity or oracle design to extract value from the protocol's pool or insurance funds. Protocols have responded with tighter position limits on smaller markets, better oracles, and emergency controls, which themselves raise centralisation questions.
13.6 Evaluating a perp DEX
Using what you learned in Module 5, Chapter 10:
| Question | Why it matters |
|---|---|
| Which design does it use? | Determines the counterparty and main risks |
| How long has it operated with significant volume? | Track record without incidents |
| How are prices and liquidations determined? | Oracle quality and mark price methods (Chapter 6) |
| What happens if a market is manipulated? | Insurance funds, position limits, emergency powers |
| Who controls upgrades and parameters? | Admin keys and governance (Module 5, Chapter 11) |
| How decentralised is the underlying chain? | Validator count and independence |
| How is collateral bridged and held? | Bridge and custody risk |
| Is open interest concentrated in a few wallets? | Concentration risk |
13.7 Using a perp DEX safely
- Use a dedicated wallet for derivatives trading, separate from your vault (Module 2, Chapter 12).
- Bridge only what you need, and use well-established bridges.
- Read approvals and signatures carefully when depositing and trading (Module 2, Chapters 7 and 8).
- Bookmark the official site. Fake perp DEX sites are common phishing targets.
- Start with major markets like BTC and ETH, which have deeper liquidity and better oracles.
- Apply the same risk rules as on any exchange: low leverage, stops, isolated margin where available (Chapter 14).
13.8 Node's comparison
"So the choice isn't 'safe' versus 'risky'," said Node. "It's which risks I'd rather have."
"That's it exactly," said Hash. "A centralised exchange asks you to trust a company. A perp DEX asks you to trust code, oracles, and a protocol's design. Many traders use both, keeping amounts on each that they can afford to lose if that venue fails."
13.9 Try it yourself
Choose one decentralised perp exchange. Find out which design it uses, which chain it runs on, how its oracle or price feed works, and what its liquidation process is. Then look at its public data: total open interest, the largest open positions, and recent liquidations. Compare its funding rate for BTC with a centralised exchange.
Key takeaways from this chapter
- Perp DEXs let users trade perpetual futures with margin held by smart contracts or protocol chains, not companies.
- Main designs include on-chain order books, oracle-based liquidity pools, and hybrids.
- On-chain transparency shows positions and liquidations publicly, which helps risk awareness but exposes large traders.
- Risks include smart contract bugs, oracle manipulation, pool losses, thin markets, centralised validators, bridging, and admin powers.
- Evaluate perp DEXs on design, track record, price sources, manipulation safeguards, governance, chain decentralisation, and concentration.
- Use a dedicated wallet, bridge carefully, check signatures, start with major markets, and keep the same risk rules.
- Centralised and decentralised venues carry different risks. Choose deliberately and limit exposure to each.