Dydx exchange is a validator-run perpetuals market

Dydx exchange and Hyperliquid take different routes to an order book

Two Layer 1 networks support these venues, yet dYdX distributes unfilled short-term orders across validator memory while Hyperliquid records order activity onchain.

Both systems give traders a central-limit order book rather than an automated market maker pool. dYdX validators gossip orders, and the selected proposer places matched fills into a block for CometBFT consensus. Hyperliquid embeds price-time-priority books in HyperCore, where orders, cancellations, trades, and liquidations enter Layer 1 state. dYdX therefore reduces permanent chain writes for rapid order changes, while Hyperliquid emphasizes fully onchain order activity. That design difference matters most during frequent placement and cancellation inside dYdX's 20-block short-term window.

What does a first dYdX trade require?

Three onboarding actions - connect, link, and deposit - prepare a dYdX Chain account before the first perpetual order reaches validators.

Connect a wallet and derive the chain address

MetaMask, Phantom for Solana, Keplr, WalletConnect, and Coinbase Wallet cover the main connection routes. Ledger connects through MetaMask, while Keplr with Ledger lacks the required signature support. A first EVM or SVM connection presents 2 signing requests: one derives the dYdX Chain wallet, and the other checks compatibility. The dYdX Chain wallet uses a 24-word recovery phrase for backup, so account control remains tied to that phrase.

Move USDC into the trading account

USDC funds perpetual margin. The integrated deposit flow uses Skip to route supported EVM or Solana balances, while direct transfers send native USDC to the Noble address associated with the dYdX Chain address. The published direct route estimates about 30 seconds before funds appear. Source-network costs still apply before collateral reaches the chain, and supported paths reflect the connected wallet type. The source wallet also needs its network gas asset, such as ETH on an EVM chain or SOL on Solana.

Select a market and define the order

BTC-USD and ETH-USD illustrate the linear perpetual format: USDC measures collateral, profit, loss, fees, and funding. The trade ticket needs a side, amount, order type, and price instruction where relevant. An isolated position opened through a long-term order requires at least 20 USDC of backing margin. The market's tick size, step size, and margin fractions then constrain valid entries.

Order types turn directional views into defined instructions

Six perpetual order types cover immediate execution, resting liquidity, stop exits, and take-profit exits on the dYdX Chain.

Market and limit instructions

Market orders use Immediate-or-Cancel, so available size fills at the best resting prices and the remainder cancels. Limit orders specify the worst acceptable price: a buy fills at that level or lower, while a sell fills there or higher. The interface gives an ordinary limit order a default 28-day Good-Til-Date, which the trader can edit before submission.

Stop and take-profit instructions

Stop Market, Stop Limit, Take Profit Market, and Take Profit Limit complete the six-type set. Triggerable orders reference the oracle price or a constrained last-traded price. A triggered market instruction accepts execution across available depth, subject to a default 10% maximum slippage setting. That 10% ceiling bounds the instruction rather than forecasting its final average fill. A triggered limit instruction protects its limit price, although it can remain unfilled when the book moves away.

Time-in-force and position controls

Post-Only makes a limit order rest or cancel, preserving maker status instead of crossing as a taker. Immediate-or-Cancel removes any unfilled remainder at once. Reduce-Only prevents an instruction from increasing or reversing the position, and it requires Immediate-or-Cancel. The dedicated close-position flow enables Reduce-Only automatically, connecting one execution rule to a zero-position outcome.

Maker-taker fees separate resting liquidity from immediate execution

Zero trading gas fees apply to ordinary dYdX fills, while maker-taker charges accrue only on the amount that actually executes.

A resting order adds book depth and receives the maker rate; an immediately crossing order removes depth and pays the taker rate. The active schedule is governance-adjustable, and the interface maps taker pricing to trailing 30-day volume across perpetual books. Canceling an unfilled order incurs 0 trading fees. Funding, source-chain transfer costs, and execution across several price levels remain separate from the displayed maker or taker percentage.

For one worked example, all changing inputs are hypothetical: a 5000 USDC notional, 2000 USDC collateral, a 2% favorable move, a 0.04% fee on each fill, and zero funding. Starting leverage equals 2.5x, and gross profit equals 100 USDC. The entry fee is 2 USDC; the 5100 USDC closing notional costs 2.04 USDC. Ending equity is therefore 2095.96 USDC, a net gain of 95.96 USDC. It excludes slippage because the 2% move already defines the average exit level.

The worked amount shows why notional, rather than posted collateral, drives the fill fee. Actual outcomes also reflect the book prices consumed by the order. Post-Only fixes maker classification, but it does not guarantee a fill. Immediate-or-Cancel fixes the handling of any remainder, while the fee tier shown at submission supplies the governing percentage for that fill.

Cross and isolated margin change where losses are contained

Two margin modes organize dYdX collateral: cross margin shares equity within a subaccount, while isolated margin separates one market's exposure.

Cross margin pools account equity

Cross margin lets multiple eligible positions draw on the same USDC balance and unrealized profit or loss. Gains in one position support the subaccount, while losses reduce the buffer for every position sharing it. Default parameter examples pair 5% initial margin with 3% maintenance for large-cap markets, 10% with 5% for mid-cap markets, and 20% with 10% for long-tail markets. Those values imply starting leverage ceilings of 20x, 10x, and 5x before open-interest scaling raises the initial margin fraction.

Isolated margin contains the position

An isolated perpetual uses a dedicated subaccount, collateral pool, and insurance fund for that market. The separation prevents its equity from supporting another position and keeps another position from consuming its buffer. Long-term or conditional isolated orders need 20 USDC of backing margin to pass the equity-tier check. At a 100% effective initial margin fraction, the market requires 1:1 collateral and removes additional leverage.

USDC collateral connects deposits, positions, and settlement

One USDC-denominated balance anchors perpetual accounting, while native DYDX serves staking and governance rather than position collateral. Noble carries the native USDC used for direct Cosmos transfers, and Inter-Blockchain Communication moves balances between compatible chains. The trading account records realized profit, loss, fees, and funding in USDC. Stablecoin collateral reduces quote-unit complexity, although its market value remains an exposure separate from BTC-USD or ETH-USD direction (see also Exchange details ).

Funding payments pull perpetual prices toward oracle prices

Sixty one-minute premium samples form each hourly funding calculation, aligning the perpetual price with its oracle index over time.

When the perpetual trades above its index, longs pay shorts; below the index, shorts pay longs. The default interest component is 0%, leaving the premium component to determine the payment. Impact notional equals 500 USDC divided by the initial margin fraction: a 10% fraction produces 5000 USDC. The eight-hour cap equals 600% of the gap between initial and maintenance margin. A 5% initial fraction and 3% maintenance fraction therefore produce a 12% eight-hour cap.

How does the validator order book settle a fill?

Twenty blocks define the default short-term window: validators gossip orders, a proposer matches them, and consensus commits each accepted fill.

Short-term orders stay in validator memory unless they fill, leaving only fill data and expiry state for the chain. The 20-block window corresponds to about 30 seconds under the documented default. Stateful orders enter chain state and persist until they fill, cancel, or expire. The front end permits up to 90 days, while the protocol permits 95 days. This split lets market makers refresh quotes rapidly without writing every abandoned quote permanently.

After consensus, full nodes stream committed data to Indexers, which serve REST and WebSocket reads to interfaces and trading systems. Official clients support Python, TypeScript, and Rust workflows. The Indexer improves retrieval speed, but node transactions remain the write path for authenticated account actions. Each component therefore owns one task: validators match, consensus finalizes, and Indexers distribute updates for orders lasting up to the 95-day protocol maximum.

Liquidation rules convert margin deficits into forced closes

A 1.5% maximum liquidation penalty applies under the default configuration when account value falls below its maintenance requirement.

The protocol values positions with validator-approved oracle prices and compares total equity with required maintenance margin. Once the threshold breaks, a protocol-generated order closes part or all of the position against resting book liquidity. The insurance fund receives the penalty and absorbs liquidation profit or loss. Cross margin evaluates the shared subaccount, whereas isolated margin evaluates its dedicated market account. Higher leverage narrows the distance to that threshold because less equity backs each unit of notional.

Oracle-based triggers do not guarantee a chosen exit price. A stop-market order crosses available liquidity after activation, while a stop-limit order preserves its limit and might wait. Reducing notional, adding collateral, or using isolated margin changes the exposure before liquidation. The decisive values remain position size, oracle price, maintenance fraction, account equity, and the 1.5% maximum penalty.

DYDX staking links chain security with protocol governance

At least two-thirds of staked voting power must approve a proposed dYdX Chain block before CometBFT commits it.

Native DYDX carries three protocol roles: staking, proof-of-stake security, and governance. Holders delegate to validators or validate directly, and stake weight influences consensus participation. Protocol trading fees accrue in USDC to validators and their stakers under the default design. Governance proposals adjust parameters such as margin tiers, funding clamps, order limits, market settings, and software upgrades. This separates the settlement asset, USDC, from the coordination asset and leaves parameter control with native DYDX voting.

GMX, Drift, and Uniswap fit different trading jobs

Three established alternatives separate pool-based perpetuals, Solana execution, and spot swaps from dYdX's validator-run central-limit order book.

GMX routes perpetual trades against GM and GLV liquidity pools, using oracle pricing across Arbitrum, Avalanche, and MegaETH rather than resting maker orders. Drift operates on Solana and combines a decentralized limit order book with just-in-time auctions and automated market maker liquidity. Uniswap targets spot token exchange through automated liquidity pools, so buying an asset there creates direct token ownership instead of a perpetual position. Hyperliquid remains the closest order-book comparison because HyperCore keeps perpetual books in Layer 1 state.

The selection turns on market structure. dYdX suits traders who want USDC-margined perpetuals, familiar maker-taker execution, API access, and Cosmos-based governance. Hyperliquid offers a fully onchain order-book path; GMX substitutes pooled liquidity; Drift combines several execution sources on Solana; and Uniswap serves spot conversion. Those mechanisms affect custody, fees, price formation, and position accounting more directly than a brand label, with Drift's just-in-time auction as one concrete example.