dYdX
Perpetual futures DEX running on its own Cosmos SDK app-chain with REST/WebSocket and gRPC APIs.
- Sato Score83
- ChainsCosmos
dYdX is an open-source venue by dYdX Trading Inc. on Cosmos, with last code activity on 2026-10-22 (Active). Latest release on 2026-10-15. Sato Score 83/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-24. How the score works →
See more: Trading →Last commit Oct 22, 2026 · Last release Oct 15, 2026 (indexer/v9.5.10) · ★ 346
Listed from dydx.xyz on 2026-06-08. Install: not attempted. Evidence →
Next step
Watch dYdX
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on dydxprotocol/v4-chain before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
dYdX (v4) is a decentralized perpetual futures exchange that runs as its own Cosmos SDK / CometBFT application-specific blockchain (dYdX Chain). An Indexer service exposes REST and WebSocket APIs for market and account data, while orders are submitted as Cosmos transactions over gRPC; official TypeScript and Python clients support programmatic and bot/agent trading. The protocol and indexer are open source. Leverage, performance, and safety are not verified here.
Sato Score
83/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 19/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 15/15
- Independent verification
- 8/10
Independently verified — listing reviewed against evidence, never self-reported.
Sato Check
v3.6.0 · as of 2026-09-28- Does it take your key?
- Asks for a key
- Does your key leave?
- Not observed
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from dydx.xyz on 2026-06-08. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Cosmos | self-reported | dydx.exchange | as of 2026-06-25 |
| Verification status | Verifiedreview date and evidence link not recorded on this listing | ✓ reviewed | — | not dated |
| Recent activity | last release 2026-10-15 · last commit 2026-10-22 | observed | github.com/dydxprotocol/v4-chain | 2026-10-24 |
| Install works | documented by the project, not run by Sato Hubnot attempted: the run did not complete and the log named no cause we could attribute | self-reported | docs.dydx.exchange | as of 2026-10-19 |
| Website answers | answered (HTTP 301) | observed | dydx.xyz | 2026-10-24 |
| Daily check record | 90 of 90 daily checks since 2026-07-26 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-23 |
| Takes your key | asks for a private key or seed phrase | declared | satohub.ai | as of 2026-09-28 |
| Key leaves the machine | not observed during install and start-uplater or triggered code paths are not covered | observed | satohub.ai | 2026-09-28 |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-09-28 |
| Built by | dYdX Trading Inc.confidence 0.80 | self-reported | github.com/dydxprotocol/v4-chain | as of 2026-06-25 |
| Creator profile | https://github.com/dydxprotocolconfidence 0.80 | self-reported | github.com/dydxprotocol/v4-chain | as of 2026-06-25 |
| Deploys as | npm, pip, API, Self-hostedconfidence 0.80 | self-reported | github.com/dydxprotocol/v4-chain | as of 2026-06-25 |
| Works with | Cosmos SDK, CometBFTconfidence 0.90 | self-reported | github.com/dydxprotocol/v4-chain | as of 2026-06-25 |
| Sato Score | 83/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-24 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — not run by us — the run did not complete and the log named no cause we could attribute
Runtime: node
npm install @dydxprotocol/v4-client-js
import { CompositeClient } from '@dydxprotocol/v4-client-js'You supply: A dYdX (Cosmos-derived) wallet mnemonic/private key with USDC collateral to place orders; read-only market data needs only the public REST/WS/gRPC endpoints
Read from the project’s own docs as of 2026-10-19. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-26
- Succeeded
- 91
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 37 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-24, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Cosmos
- Agent types
- Trading Venue, Perps DEX
- Open source
- Yes
- Pricing
- Trading fees (maker/taker tiered)
- Deploys as
- npm, pip, API, Self-hosted
- Works with
- Cosmos SDK, CometBFT
- Last checked
- 2026-10-24
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where dYdX fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are MCPs? The Standard Way to Give Agents Tools
Recent Activity
All news →Releases and posts from dYdX, pulled from its GitHub and X.
v4-chain Release indexer/v9.5.10
What's Changed Backported to release/indexer/v9.x via #3435 : perf(ender:candles): precompute strings, simpler getCandle by @UnbornAztecKing in #3317 chore: info to debug logs by @ben-dydx-ops in #3348 chore: decommission dev4 environment by @UnbornAztecKing in #3373 fix(comlink): prevent deep pagination from overloading primary DB by @2dpetkov in #3362 perf(socks): skip parsing messages without s
v4-chain Release protocol/v9.8.1
Release v9.8.1 What's Changed mempool: CheckTx for txs received from peers now runs on a worker pool, so it no longer delays that peer's consensus messages ( dydxprotocol/cometbft#62 , #3426 ) [mempool] recv_workers defaults to 4, including when config.toml lacks the key; recv_workers = 0 restores the old inline path Queued txs are capped by recv_queue_size (default 100000); txs beyond the cap are
v4-chain protocol/v9.8.1-rc0
protocol/v9.8.1-rc0
v4-chain Release protocol/v9.8.0
Release v9.8.0 Mainnet release for the v9.8 upgrade (upgrade handler name v9.8 ), applied at height 109170000. This is the same commit ( 9ab4e17 ) as v9.8.0-rc0, which upgraded dydx-testnet-4 at height 88375358. This release contains security fixes. Binaries were distributed to validators ahead of the upgrade, and the source is published now that the upgrade is live. The build is reproducible: the
v4-chain Release protocol/v9.7.1
Release v9.7.1 What's Changed fix(clob): enforce short-term order equity tier in CheckTx Full Changelog : protocol/v9.7.0...protocol/v9.7.1
v4-chain Release protocol/v9.7.0
Release v9.7.0 What's Changed Backport v9.7 changes to release/protocol/v9.x ( #3384 , #3386 , #3388 ) by @tqin7 in #3389 Full Changelog : protocol/v9.6.4...protocol/v9.7.0
Listing History
Recorded changes to dYdX's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 19, 2026Verified: deploy spec
- Oct 15, 2026New release published
- Oct 14, 2026New release published
- Oct 9, 2026Edited: chains supported
- Sep 26, 2026Edited: website url, docs url
- Aug 26, 20269 releases trackedShowing the 2 most recent. Full release history is retained in the listing record.
- Jul 27, 2026Sato Hub began tracking this listing
- Jun 25, 2026Enriched: marketplace notes
- Jun 25, 2026Auto-enriched: creator profile url, creator name, deployment options, supported integrations +2 more
Compared with
Appears in
Related Resources
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Jupiter
ActiveSolana swap aggregator that routes trades across DEXs via a widely used API and SDKs.
1inch
ActiveMultichain DEX aggregator with a developer API suite and an official MCP server for AI-agent swap execution.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about dYdX
- Is dYdX open source?
- Yes. dYdX is open source under the AGPL-3.0 (modified — subject to dYdX Terms of Use) license; the repository is https://github.com/dydxprotocol/v4-chain. Checked as of 2026-10-24.
- Which chains does dYdX support?
- dYdX lists support for Cosmos as of 2026-10-24.
- Is dYdX still maintained?
- The most recent code activity Sato Hub observed was on 2026-10-22 (last commit 2026-10-22, last release 2026-10-15), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run dYdX?
- node. Install: npm install @dydxprotocol/v4-client-js. Entry: import { CompositeClient } from '@dydxprotocol/v4-client-js'. This is taken from the project's own documentation and has not been reproduced by Sato Hub.
- Is dYdX verified on Sato Hub?
- Sato Hub holds one earned check for dYdX: Independently verified — listing reviewed against evidence, never self-reported. Its Sato Score is 83 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "dYdX — Sato Hub." Sato Hub, updated 2026-10-24, accessed 2026-10-24. https://satohub.ai/resources/dydx-chainData last refreshed 2026-10-24; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.