The venue is dYdX Chain, not every product with the dYdX name
The dYdX Operations help center describes dYdX Chain's v4 software as supporting perpetual markets, and its market guide identifies BTC-USD, ETH-USD and other pairs. The official status page lists the Chain, Indexer and trade frontend as operational at this review. That establishes an active perp venue; it does not establish a comparable historical trading-volume total.
The dYdX Foundation distinguishes legacy dYdX v3, built around Ethereum and StarkEx, from dYdX Chain and native DYDX. Chain is the current v4 venue; v3 history is a different deployment. A frontend can route orders into the Chain without being a second execution venue. Parent ecosystem, v3, Chain and frontend rows must not be added to one another without a documented, non-overlapping scope.
Sources: dYdX Operations: selecting a market on dYdX Chain ↗ · dYdX Chain live service status ↗ · dYdX Foundation: v3 sunset and token FAQ ↗
A useful Indexer API still needs a historical coverage test
Official documentation identifies the mainnet Indexer at indexer.dydx.trade/v4. Its perpetual-markets route returns a market map when no ticker is specified. The published market type includes status, market type, 24-hour volume, open interest and base open interest. Those fields describe a market response at retrieval time; the type page does not document an observation timestamp, the exact 24-hour boundary or a conversion rule between its two open-interest fields. We therefore cannot promote a sum of those fields as a verified daily venue figure.
The Indexer also exposes per-market candles. Its candle type has a UTC startedAt, usdVolume, baseTokenVolume, trade count and startingOpenInterest; the endpoint supports a 1DAY resolution and ISO time filters. A historical collector must enumerate every perp market that existed in each UTC interval, including markets that later entered final settlement or disappeared from a current active-only view. It must archive each raw response and hash, test daily boundary and partial-candle behavior, and retain source-empty intervals as null with reasons. The current market list alone cannot reconstruct those past cohorts.
Sources: dYdX mainnet Indexer endpoint reference ↗ · dYdX Indexer HTTP market and candle API ↗ · dYdX perpetual market response fields ↗ · dYdX candle response fields ↗
DYDX token terms are a separate money-flow question
The Foundation's v3 FAQ distinguishes Ethereum ethDYDX and wethDYDX governance assets from native DYDX on dYdX Chain. Token identity and the supply denominator must be pinned before a market quote or holder-flow figure is attached to the Chain profile. A migration or wrapper balance is not automatically a new economic claim.
A dYdX Labs post announced a buyback program in March 2025, initially allocating 25% of net protocol fees to monthly DYDX purchases and staking the acquired tokens. The same historical announcement described 10% for the Treasury SubDAO, 25% for MegaVault and 40% for staking rewards. These are terms at that date, not proof of the current allocation or executed purchases in October 2026. A current program record needs the governing vote or terms, the definition of net fees, identified purchasing and destination wallets, dated transactions, and a reconciliation of purchased versus distributed or staked DYDX. One purchase cannot be counted as both a burn and a holder distribution.
Sources: dYdX Foundation: v3 sunset and token FAQ ↗ · dYdX Labs: March 2025 buyback program terms ↗
What must be checked before dYdX appears in a comparative ranking
A 30- or 90-day comparison requires a complete perp-only daily series on one UTC boundary, a dated inventory of listed and settled markets, verified volume units, raw source archives, missing-day reasons and an open-interest convention that is consistent across dates. The reported user fees and net protocol fees must then be traced to the same Chain product and period. Historical fee holidays or trading incentives need dated annotations rather than being treated as organic growth. We have not published numeric dYdX Chain volume, OI, fees, buybacks or DYDX holder revenue here because those reconciliations are still open.
The profile also needs current token rights, supply and unlock records, a terms-versus-execution waterfall, and a clearly labelled official trade destination. Until then the coverage entry is the honest result: dYdX Chain is inside the perp universe, but a ranking slot would imply comparability that has not yet been demonstrated. Access rules vary by jurisdiction; the operator's market guide flags restrictions, so readers must check the live product terms before trading.
Sources: dYdX Operations: selecting a market on dYdX Chain ↗ · dYdX Indexer HTTP market and candle API ↗ · dYdX Labs: March 2025 buyback program terms ↗
What we monitor next
- Archive the Chain Indexer market map and complete per-market UTC daily candles, including historical settled markets.
- Reconcile 24-hour volume and both open-interest fields with the daily candle and provider conventions before cross-venue comparison.
- Verify the currently effective net-fee allocation, actual DYDX purchases and destination transactions; annotate incentive windows separately.
Frequently asked questions
Is dYdX Chain the same venue as dYdX v3?
No. dYdX Chain is the v4 venue; the Foundation distinguishes it from the legacy v3 deployment and its Ethereum governance assets.
Does the Indexer market map prove 30-day venue volume?
No. It lists markets and current fields. A complete historical market cohort, UTC boundaries, units and raw daily responses are required for a comparable 30-day total.
Do DYDX holders automatically receive the announced buyback allocation?
The March 2025 announcement described a program, not a direct holder distribution. Current terms and actual purchases or staking transfers need separate verification.
Compare the evidence
Related research
Source register
- dYdX Operations: selecting a market on dYdX Chain · checked 2026-10-05
- dYdX Chain live service status · checked 2026-10-05
- dYdX Foundation: v3 sunset and token FAQ · checked 2026-10-05
- dYdX mainnet Indexer endpoint reference · checked 2026-10-05
- dYdX Indexer HTTP market and candle API · checked 2026-10-05
- dYdX perpetual market response fields · checked 2026-10-05
- dYdX candle response fields · checked 2026-10-05
- dYdX Labs: March 2025 buyback program terms · checked 2026-10-05
Research revisions
- 2026-10-05 — First source-reviewed dYdX Chain coverage audit; no ranked metric promoted.
AI-assisted research checked against cited sources. Facts, assumptions and interpretation are distinguished; this is not a financial audit or a recommendation tailored to you. Editorial standards.
Compare protocols →