HostNexFlow › Library › Hyperliquid vs dYdX
Hyperliquid vs dYdX: two architectures for putting a derivatives book on-chain
The two biggest answers to decentralized perpetuals made opposite bets. Hyperliquid built a whole L1 around its book and a community vault that eats the losses; dYdX left Ethereum for its own Cosmos chain and validator set. Both restrict US users — their incident files are where the difference shows.
Hyperliquid and dYdX answer the same question — can a serious derivatives book live fully on-chain — with opposite machinery. One wrote a chain whose only job is the book; the other took Ethereum's biggest perp venue and rebuilt it as a sovereign Cosmos chain. Both custody stays with the user, both books are inspectable, and both keep US persons out at the interface layer.
Every row below names its source and date.
The parameter table
| Parameter | Hyperliquid | dYdX |
|---|---|---|
| Architecture | Purpose-built L1 (HyperBFT consensus) where the order book, matching, and margin engine are chain primitives — no general-purpose VM on the critical path (project docs, as of 2026-09-28). | Own Cosmos SDK proof-of-stake chain since genesis Oct-26-2023; off-chain order book in validator memory, on-chain settlement — full production trading Nov-28-2023 (dYdX blog, The Block). |
| Custody | Self-custodied margin — USDC collateral posted to bridge escrow; withdrawals are validator-signed, no omnibus wallet. | Self-custodied margin — collateral on the chain itself; the Ops subDAO front end is one of several surfaces onto the same contracts. |
| Loss backstop | HLP — a public community vault that earns fees and absorbs liquidation shortfalls; anyone can inspect its P&L (protocol docs). | On-chain insurance fund plus MegaVault (user-funded liquidity vault); v3 ran a company-visible insurance fund that paid out ~$9M in the Nov-17-2023 YFI event (dYdX post-incident posts). |
| Validator set | Small permissioned-style set in the early era; the JELLYJELLY episode showed validators can force-settle positions. | 60+ independent validators at genesis, open staking — DYDX is the L1 staking token via the one-way wethDYDX bridge from Ethereum (dYdX Foundation). |
| US access | Restricted jurisdictions blocked at the interface — the Genesis claim page rejected wallets for “repeated attempts to access it from a restricted jurisdiction.” | US persons barred from the front end by terms; the chain itself is permissionless but the operated surfaces geo-fence. |
| Token | HYPE — 310M announced, 270.9M credited to 94,019 addresses Nov-29-2024; no VC unlock column. | DYDX — migrated from ethDYDX governance token to L1 staking+fee token; v3 holders bridge one-way. |
| Incident file | Mar-2025 JELLYJELLY: a manipulated market was force-settled by validators and HLP absorbed the position — kept depositors whole, invited the “decentralized in name only” critique. | Nov-2023: ~$9M insurance payout on engineered YFI liquidations (“targeted attack,” FBI engaged, no user funds lost). Jul-2024: Squarespace DNS hijacks of dydx.exchange — Jul-9 blocked by DNSSEC, Jul-23 a ~30-minute malicious front end cost two users ~$31K, recovery promised (dYdX postmortem). |
The architecture fork
Hyperliquid's bet is vertical: build the chain for the book, not the book for the chain. Matching, margining, and liquidations execute as L1 primitives under HyperBFT, which removes the mempool games and gas auctions that general-purpose chains impose on liquidations. The cost is a younger, narrower validator set — the chain is fast partly because it is small.
dYdX's bet is horizontal sovereignty. After three versions on Ethereum, v4 shipped as its own Cosmos SDK chain: genesis block Oct-26-2023, 60+ validators, full production trading opened by governance vote Nov-28-2023 with a $20M DYDX launch-incentives program run by Chaos Labs. Order matching lives in validator memory (an off-chain book that settles on-chain), and DYDX itself migrated from an Ethereum governance token into the chain's staking asset via the wethDYDX one-way bridge.
The practical read: Hyperliquid optimizes for execution quality and unified liquidity on one venue; dYdX optimizes for validator decentralization and Cosmos interoperability — IBC transfers, a public validator market, and governance that genuinely controls the fee switch.
Backstops: the vault and the fund
Every leveraged venue needs a payer of last resort, and this is where the designs diverge cleanly. Hyperliquid's HLP is a public community vault: depositors earn trading fees and liquidations flow through it, including the ugly ones — its P&L is inspectable in real time. In the Mar-2025 JELLYJELLY manipulation the venue force-settled the market and HLP absorbed the position, which protected the book but showed who holds the override keys.
dYdX runs a formal insurance fund plus MegaVault, a user-funded liquidity vault. Its documented stress test came on Nov-17-2023, when engineered liquidations in the YFI market forced ~$9M out of the v3 insurance fund — founder Antonio Juliano called it a “targeted attack,” reported it to the FBI, and noted the fund still held ~$13.5M with no user funds lost. His framing matters for this comparison: “v3 has central components, dYdX Chain does not.”
The incident files, side by side
Neither venue has lost user margin to a protocol breach — the losses on record are of different shapes. Hyperliquid's file is governance-shaped: the JELLYJELLY force-settle proved validators can override a market mid-flight, which is either prudent risk management or discretion a CEX would also exercise, depending on what you thought you were buying.
dYdX's file is operational. Beyond the $9M insurance event, its dydx.exchange front end was DNS-hijacked twice in July 2024 after the Google Domains→Squarespace migration: Jul-9 was caught by DNSSEC before users saw it; Jul-23 got ~30 minutes of malicious wallet-drain page live, cost two users ~$31K, and was cleaned up with SEAL's incident team. The domain layer — not the chain — was the attack surface, and it was the same wave that hit several DeFi front ends that month. Bloomberg reporting the same week said dYdX was in talks to sell the v3 software to a consortium including Wintermute and Selini — the venue quite literally winding down the centralized version while the decentralized one takes over.
Access, fees, and who each is for
Both venues keep US persons out at the interface. Hyperliquid does it by terms plus active blocking — the Genesis claim page is documented to have rejected wallets for “repeated attempts to access it from a restricted jurisdiction.” dYdX bars US users on its operated front ends while the chain remains permissionless underneath. Phantom's in-app perps run on Hyperliquid rails, which puts a US-facing wrapper over a venue that bars US users directly.
Pick Hyperliquid if you want the deepest single-venue on-chain perp book and you accept a concentrated validator set plus demonstrated override discretion. Pick dYdX if you want the older name's mature chain — 60+ validators, real staking governance, Cosmos interoperability — and accept that its liquidity fragmented across the v3→v4 transition. Neither is a softened version of a centralized exchange; both are the genuine article with different trust surfaces.
Frequently asked
Is Hyperliquid or dYdX safer for perp trading?
Both are self-custodial with public books. Hyperliquid's risk is concentrated validators — the JELLYJELLY force-settle showed discretion exists. dYdX's risk is operational — its front-end domain was DNS-hijacked twice in Jul-2024 (~$31K lost by two users). The chain itself was not breached in either event.
Did dYdX lose $9 million in 2023?
The v3 insurance fund paid ~$9M on Nov-17-2023 to cover engineered YFI liquidations — founder Antonio Juliano called it a targeted attack and engaged the FBI. User funds were not affected; the fund still held ~$13.5M afterward.
What happened in the JELLYJELLY incident?
Mar-2025: a manipulated JELLYJELLY market on Hyperliquid was force-settled by validators and the HLP vault absorbed the position. Depositors were kept whole, but it proved the validator set can override markets — the “decentralized in name only” critique.
Do Hyperliquid or dYdX report to the IRS?
Neither issues US tax forms — both restrict US persons at the interface layer. On-chain fills are public but arriving without forms means you reconstruct basis yourself.
Is dYdX still on Ethereum?
No — v4 is a standalone Cosmos chain (genesis Oct-26-2023, full trading Nov-28-2023). The Ethereum v3 exchange wound down; its software was reportedly in sale talks in mid-2024.
Which has more decentralization?
On validator count, dYdX — 60+ permissionless-style validators vs Hyperliquid's smaller set. On discretion, the JELLYJELLY force-settle is the documented data point; dYdX governance is slower but more distributed.