LibraryMarkets2023Design paperCorpus record
dYdX v4: an application-specific chain for perpetuals
dYdX v4. dYdX Trading.
dYdX v4 moves the perpetual order book onto its own chain, so matching is no longer a set of Ethereum transactions in a smart contract.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
dYdX v4 moves the perpetual order book onto its own chain, so matching is no longer a set of Ethereum transactions in a smart contract.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 8
01 Claim ledger
What the paper is allowed to say
Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.
Claim 01 · Paper model
The defect
Leaving Ethereum does not, by itself, change the definition of a perpetual. It changes who orders trades and which light client you must trust.
Claim 02 · Paper model
The proposal
dYdX v4 moves the perpetual order book onto its own chain, so matching is no longer a set of Ethereum transactions in a smart contract.
Claim 03 · Paper model
The mechanism
The chain's consensus finalises orders and trades. The v3 StarkEx deployment is a different design and a different document.
Claim 04 · Paper model
The bound
No volume, fee, or funding rate is stated here.
02 Three cuts
Observation, model, falsifier
A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.
01 The defect
Observation
What the study says
Leaving Ethereum does not, by itself, change the definition of a perpetual. It changes who orders trades and which light client you must trust.
Model
What has to hold
You are reading the v4 documentation. The v3 system is a different object.
Falsifier
What would retire it
Which document is in force: v3 StarkEx or the v4 chain?
02 The proposal
Observation
What the study says
dYdX v4 moves the perpetual order book onto its own chain, so matching is no longer a set of Ethereum transactions in a smart contract.
Model
What has to hold
The document is the one at the source URL. A marketing page with the same brand is not this text.
Falsifier
What would retire it
Which document is in force: v3 StarkEx or the v4 chain?
03 The mechanism
Observation
What the study says
The chain's consensus finalises orders and trades. The v3 StarkEx deployment is a different design and a different document.
Model
What has to hold
You are reading the v4 documentation. The v3 system is a different object.
Falsifier
What would retire it
Which document is in force: v3 StarkEx or the v4 chain?
04 The bound
Observation
What the study says
No volume, fee, or funding rate is stated here.
Model
What has to hold
You are reading the v4 documentation. The v3 system is a different object.
Falsifier
What would retire it
Which document is in force: v3 StarkEx or the v4 chain?
03 Sequence
One action, as an operating tape
- 01The chain's consensus finalises orders and trades. The v3 StarkEx deployment is a different design and a different document.
- 02The insurance fund and the liquidation rule are protocol parameters. This note does not restate their current values.
- 03A bridge for USDC or another settlement asset is not the order book. Its trust assumption is separate.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
dYdX v4 moves the perpetual order book onto its own chain, so matching is no longer a set of Ethereum transactions in a smart contract.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
Validator-set assumptions follow the chain they actually ship, which the docs must name.
What actually moves
The cut
The insurance fund and the liquidation rule are protocol parameters. This note does not restate their current values.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A later client, parameter or reward formula is a different object from this paragraph.
What a later deployment may change
The cut
A bridge for USDC or another settlement asset is not the order book. Its trust assumption is separate.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A later client, parameter or reward formula is a different object from this paragraph.
05 Register
What has to be true
Model · Not re-measured
You are reading the v4 documentation. The v3 system is a different object.
Model · Not re-measured
The document is the one at the source URL. A marketing page with the same brand is not this text.
Model · Not re-measured
No price, supply, yield, or adoption figure is added by this desk.
06 Divergence
What happened after the paper
This is not a statement about the dYdX foundation's governance outcomes.
A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.
07 Pre-mortem
What to check before you use the idea
- 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.
08 Anatomy
The paper, in the order a builder needs
The problem it names
Leaving Ethereum does not, by itself, change the definition of a perpetual. It changes who orders trades and which light client you must trust.
What the design proposes
- The chain's consensus finalises orders and trades. The v3 StarkEx deployment is a different design and a different document.
- The insurance fund and the liquidation rule are protocol parameters. This note does not restate their current values.
- A bridge for USDC or another settlement asset is not the order book. Its trust assumption is separate.
How the mechanism is specified
- The chain's consensus finalises orders and trades. The v3 StarkEx deployment is a different design and a different document.
- The insurance fund and the liquidation rule are protocol parameters. This note does not restate their current values.
- A bridge for USDC or another settlement asset is not the order book. Its trust assumption is separate.
What this page does not treat as proven
- No volume, fee, or funding rate is stated here.
- Validator-set assumptions follow the chain they actually ship, which the docs must name.
- This is not a statement about the dYdX foundation's governance outcomes.
Why the desk still reads it
dYdX v4 moves the perpetual order book onto its own chain, so matching is no longer a set of Ethereum transactions in a smart contract.
09 Lexicon
Terms, opened into the record
- Application-specific chain
- A chain whose state machine is the exchange, rather than a general virtual machine hosting an exchange contract.
- Perpetual
- A position with a funding payment and no expiry. It is not a loan and not a spot trade.
10 Repository
Every linked record on this page
Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.
This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.
Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.
