dYdX: A Standard for Decentralized Margin Trading and Derivatives

Authors Antonio Juliano
Year 2017 (revised 2018)
Project dYdX
License Not stated in the paper
First-party reference Antonio Juliano’s history of dYdX (the original paper host is no longer available)

Scope note: This page summarizes Antonio Juliano’s early dYdX proposal, not a 2021 v3 paper or a technical specification for today’s dYdX Chain. The original dYdX-hosted paper URL no longer resolves. The available text preview points to a copy uploaded to a third-party site, so it is not a substitute for an official archive.

Directories Ethereum Whitepapers & Research

This educational summary is not a verbatim reproduction or financial advice. The original paper’s statements about fairness, trustlessness, and open access describe its proposed design; they should not be read as guarantees about every later dYdX product.

What the 2017 paper proposed

dYdX: A Standard for Decentralized Margin Trading and Derivatives is attributed to Antonio Juliano and dated September 25, 2017, with a revision dated August 6, 2018. Its abstract proposes protocols for financial products built around pairs of Ethereum ERC-20 tokens. It focuses on margin trading and fully collateralized, or “covered,” options. It does not describe the later dYdX perpetual-futures exchange, StarkEx, or dYdX Chain.

The paper’s central design choice was to keep order books off-chain while settling completed trades through Ethereum smart contracts. Moving order discovery away from the chain could avoid recording every order-book update on Ethereum, while on-chain settlement was intended to enforce the resulting trade. This is a tradeoff: execution can be more practical, but users still rely on the order-book and settlement design behaving as specified. The paper’s abstract and its author’s first-person retrospective support this historical scope.

“Covered” options are options whose obligations are fully collateralized under the proposed mechanism. The paper is therefore useful for understanding an early attempt to bring lending, leverage, and derivatives to Ethereum-based tokens. It is not evidence that the first prototype contracts described there were deployed: Juliano later wrote that the initial contracts never shipped to production.

How the project changed after the paper

dYdX’s history is a sequence of different products and architectures. In Juliano’s account, a margin protocol and product launched in 2018; the Solo lending and margin protocol followed in 2019; and dYdX introduced perpetual contracts in 2020. A StarkWare-based Layer 2 product followed in 2021. The software for dYdX Chain, also called v4, was released in 2023. These milestones come from Juliano’s project history; they should not be folded back into the contents of the 2017 paper.

The distinction matters when reading older explanations. Perpetual futures and funding rates belong to later products, not this proposal. Likewise, the v3 and v4 labels describe later systems with different infrastructure. The dYdX Foundation said the v3 wind-down was scheduled for the end of October 2024 and that dYdX Chain users were unaffected by that change; see its v3 sunset and token FAQs.

What the later dYdX Chain design says

The official dYdX Chain repository describes v4 as sovereign blockchain software built with the Cosmos SDK and CometBFT, with a perpetual-futures exchange, order book, and matching engine. That repository is a source for the later software, not for the 2017 paper.

A dYdX technical architecture overview describes validators keeping orders in in-memory books that are off-chain and not part of consensus; when an order matches, the proposer includes it in a proposed block for validators to approve. The page is a dated overview (shown as published January 24, 2025 and last updated November 1, 2023) and says design details were subject to change. It is useful for explaining the intended distinction between order-book data and committed trades, but should not be used alone to assert every detail of the current live implementation.

The official archived v1 contract repository is marked deprecated. Its Apache-2.0 code license does not establish a license for Juliano’s separate 2017 paper. No license statement was found in the paper copy reviewed for this summary.

How to read this paper today

Use the document as a historical design proposal. It helps explain why an early dYdX system separated order-book handling from Ethereum settlement, and why the project explored margin products and covered options. It does not establish current fees, leverage limits, funding intervals, trading volume, or censorship guarantees. Those are version-specific operational claims and need current product documentation or chain data.

In particular, the 2017 proposal should not be described as a “v3 whitepaper.” It predates perpetuals and the StarkWare product by several years. The available third-party-hosted text preview lets readers inspect the paper, but the paper’s original hosting is unavailable and its publication details are corroborated here through Juliano’s own history rather than a currently working official paper archive.

Related Terms

See Also

Social Media Sentiment

A small sample from r/dydxprotocol shows discussion rather than a reliable measure of overall opinion. In an August 2023 thread, a user questioned whether v4’s decentralization and open-source design would protect users if the platform failed; replies offered differing interpretations of how validator-held order books and consensus fit together. A separate April 2025 post described a favorable personal trading experience, but used recommendation language and may be promotional. Taken together, these posts show interest in decentralization and usability alongside questions about reliability; they are anecdotal, self-selected, and not representative of all users.

Last updated: 2026-10

Sources

Last updated: 11 October 2026