Hyperliquid vs dYdX vs Lighter for automated trading

Why compare these three

Hyperliquid, dYdX v4 and Lighter are the three decentralized perpetual exchanges where TensorTrader is live-ready: each has passed the paper-first parity checklist of balances, margin, fills, reconcile and fill-based profit booking, and each can execute TradingView alerts. They share the big advantage of decentralized venues for automation, which is that you keep custody and trade with a restricted key. They differ in how that key is created, how their chains work and how much leverage they offer.

Side by side

Hyperliquid: auth

Agent wallet approved from MetaMask with one EIP-712 signature

dYdX v4: auth

Restricted trading key derived from your wallet in the connect flow

Lighter: auth

EIP-712 agent key approved in the connect wizard

Hyperliquid: testnet

Confirmed: Hyperliquid testnet, balances from the public clearinghouse state

dYdX v4: testnet

Confirmed: dYdX v4 testnet, balances from the indexer subaccount equity

Lighter: testnet

Confirmed: zk-rollup testnet via CCXT sandbox, USDC collateral

Hyperliquid: max leverage

50x on the largest markets

dYdX v4: max leverage

20x

Lighter: max leverage

20x

all three: settlement

USDC-margined perpetuals

all three: TradingView execution

Yes, paper first

Hyperliquid: the liquidity leader

Hyperliquid runs its own layer-1 with an on-chain order book and has become the deepest decentralized perps venue. For bots that means tighter spreads and less slippage on major markets, plus the widest token list of the three. Its agent-wallet model is the cleanest to set up: you sign one approval and never paste a key. Unified Account mode makes margin management simpler for new accounts.

dYdX v4: an app chain with an off-chain book

dYdX v4 runs on its own Cosmos-based chain, where validators run the order book off-chain and settle on-chain. Authentication uses a trading key derived from your wallet; the dYdX owner mnemonic is the one documented exception in TensorTrader's key policy, labeled in the UI, because the connect flow derives the restricted key from it. Leverage is lower than Hyperliquid's, which is not a bad thing for automated strategies.

Lighter: zero-knowledge settlement

Lighter is a zk-rollup that proves trades with zero-knowledge proofs, aiming for verifiable matching. TensorTrader signs Lighter orders headlessly with the native signer that ships with the Lighter SDK, and the testnet runs through CCXT sandbox mode. It is the newest of the three, so check liquidity on the markets you plan to trade.

Which one to pick

1. 1Want the most liquidity and markets, with the simplest key setup: Hyperliquid.
2. 2Want lower maximum leverage and an established app-chain design: dYdX v4.
3. 3Want zero-knowledge settlement and are comfortable with a newer venue: Lighter.
4. 4Not sure: connect all three on testnet and run the same small alert set on each; compare fills and fees on paper.

What "live-ready" means in TensorTrader

A venue is live-ready only after it passes a parity checklist on a fresh test account, compared against a working venue: balances persist into the auth panel, equity and margin summaries are non-zero when funded, execution mode is reported correctly, TradingView webhooks size and clamp correctly on paper then testnet, deep reconcile and orphan close work without restart, and closed trades book profit from the venue's own fills. All three of these DEXs passed it. Venues that fail any item stay connectable only.

Running the same strategy on all three

1. 1Connect all three on testnet in Exchange Auth.
2. 2Create one Batch Create plan and select the three keys in step 1 · Exchanges.
3. 3Keep tokens that list on all three, such as BTC and ETH, and one timeframe.
4. 4After a few weeks, compare fill prices, fees and net ROI per venue on the dashboard.

Frequently asked questions

Can one TensorTrader account use all three?

Yes. Each venue has its own key, and Batch Create can target any of them in step 1 · Exchanges.

Do any of these need my seed phrase?

Hyperliquid and Lighter never do; they use agent keys. dYdX is the documented exception where the connect flow derives the restricted trading key.

Keep reading

• Hyperliquid trading bot: how to automate Hyperliquid perps safely

  The complete guide to automating Hyperliquid: agent wallets, testnet, TradingView and GoCharting alerts, leverage and margin, fees and funding, portfolio mode, and the real results of our own testnet books.

• Connect Hyperliquid to TensorTrader with a MetaMask agent wallet

  No API key to copy: approve a TensorTrader agent wallet from MetaMask, start on Hyperliquid testnet, and trade perps from TradingView alerts without ever sharing your seed phrase.

• Connect dYdX (v4) to TensorTrader: Wallet-approved agent key, paper first

  Approve a trade-only dYdX (v4) agent, save it in TensorTrader on paper first, and see what works on dYdX (v4) today, including TradingView alert execution.

• Connect Lighter to TensorTrader: Wallet-approved agent key, paper first

  Approve a trade-only Lighter agent, save it in TensorTrader on paper first, and see what works on Lighter today, including TradingView alert execution.