Protocols / dYdX
Research Perpetual DEX

dYdX v4: Architecture and Market Position

An examination of dYdX's transition to a Cosmos-based appchain and the implications for performance, decentralization, and competitive positioning.

DH
Daniel Harrington
Editor-in-Chief
October 30, 2026
11 min read

Overview

dYdX is among the most established perpetual DEX platforms. Its v4 release, launched in late 2023, represented a fundamental architectural shift — from an Ethereum L2 built on StarkEx to a dedicated appchain built using the Cosmos SDK. The move was motivated by a desire for greater control over the full technology stack and alignment with a validator set dedicated specifically to dYdX's operation.

Architecture

The dYdX chain uses CometBFT (formerly Tendermint) for consensus, with a validator set running specialized nodes that handle both consensus and order matching. Order matching occurs off-chain in the validator nodes, with settlements written to the chain. This architecture balances the performance demands of order book trading against the transparency requirements of decentralized systems.

Market Position

dYdX occupies a distinctive position in the perpetual DEX landscape. Its longer operating history, institutional relationships, and established liquidity make it a reference point for the category. The v4 migration was a significant undertaking, and the full implications — particularly around validator incentives and MEV dynamics — continue to unfold.

Comparison with Hyperliquid

Both dYdX v4 and Hyperliquid chose dedicated chains, but with different design emphases. dYdX uses an established consensus framework (CometBFT) and off-chain matching; Hyperliquid built a custom consensus (HyperBFT) and executes matching on-chain. Each approach reflects different priorities regarding the trade-offs between performance, transparency, and ecosystem leverage.

Conclusion

The appchain approach that dYdX pioneered for the perpetual DEX category has been validated by subsequent entrants, though with varying implementations. As the market continues to mature, the differences in architectural philosophy between these protocols will become more apparent through operational performance, developer adoption, and community governance.

Editorial Note: This research is for informational purposes only. See our Risk Disclaimer for more information.