Skip to content
First Access Exchange

Limits

Order rate limits

Per address (all its subaccounts together), enforced in CheckTx (/dydxprotocol/clob/block_rate). The testnet's genesis raises dYdX's long-term order limits so market makers can quote every book with long-term orders:

LimitTestnet
Long-term and conditional orders placed200 a block, 5,000 per 100 blocks
Short-term orders and cancels400 a block

Governance changes them with MsgUpdateBlockRateLimitConfiguration.

Open orders by equity

A subaccount may have only as many open orders as its net collateral allows (/dydxprotocol/clob/equity_tier). On the testnet, the same for short-term and for long-term orders:

Net collateral at leastOpen short-term ordersOpen long-term orders
$000
$2011
$10055
$1,0001010
$10,000100100
$100,0001,000200

So a subaccount needs at least $20 of net collateral to place any order. An order beyond its tier is refused. Untriggered stops count toward the long-term column.

Stop orders

Stops are limited per account only, as on dYdX and Hyperliquid:

  • by the equity tiers above, which count them with every stateful order;
  • by at most 20 untriggered stops a subaccount, on all chain-market books together (/dydxprotocol/clob/chain_stop_limits; governance changes it with MsgUpdateChainStopLimits). A 21st is refused with ErrTooManyChainStops (x/clob error 20112). A stop stops counting once it triggers, is cancelled or expires.

There is no limit per book: one account can't fill a book's stops and lock others out.

As on dYdX, the equity tier is checked only when a stop is placed. Collateral moved out afterwards (to another subaccount, or withdrawn) cancels no stop, and the same collateral can then place stops in another subaccount. So the number of stops isn't bounded by capital: it is bounded by the order rate limits per address above, the 20 a subaccount, and the 95-day expiry.

What each kind of market's stops trigger on, and when they can't trigger (an option's book without a valid average: no_book_average), is in stop orders.

Chain-market bounds

BoundValue
Short-term order expiryAt most 40 blocks ahead
Long-term and conditional order expiryAt most 95 days ahead
Long-term orders resting per subaccountOn one chain-market book at a time
Book levels read for S, the call marks and the indexThe first 16 a side (max_scan_per_side, max_scan)
A subaccount's orders counted in a book sampleIts best 4 a side
A subaccount's depth counted in SAt most 50 contracts a side
Strikes an event16
Events trading at once16
Companies active at once4
Holders paid out a block500, across every resolving market
A Yes resolution's market capAbove 0, at most $100,000B
Builder feeAt most 10,000 ppm (1%)
Binary order and trigger prices0.1¢ to 99.9¢, in steps of 0.1¢
Stop triggersAt most the market's price cap; none on a standalone binary
Untriggered stops per subaccount20, all chain-market books together; none per book
USDC withdrawals over IBCAt least $1, at most what the address received over the bridge less what it withdrew; all together per hour max($10,000, 1 ppm of all USDC), per day max($100,000, 10 ppm) (bridge)
Company perpetual leverage2×

Indexer limits

The indexer's HTTP API is rate limited per IP (dYdX's 100 requests per 10 seconds on most routes, and 20 a second at the testnet's edge, bursts of 40), and its WebSocket per connection, at most 20 open per IP (indexer API).

Public RPC and REST

The public RPC answers a fixed list of CometBFT's methods, over JSON-RPC (POST /) and as GET routes (/status, /abci_query?...). GET / lists them:

abci_info, abci_query, block, block_by_hash, block_results, block_search, blockchain, broadcast_tx_async, broadcast_tx_commit, broadcast_tx_sync, check_tx, commit, consensus_params, consensus_state, genesis, genesis_chunked, header, header_by_hash, health, status, tx, tx_search, validators.

  • Pending transactions can't be read: unconfirmed_txs, num_unconfirmed_txs and dump_consensus_state (which holds the proposed block before it commits) are refused, and there is no WebSocket. net_info and the unsafe routes are refused too.
  • A JSON-RPC batch holds at most 10 calls (the node's own limit).
  • A JSON-RPC POST needs a Content-Length: a body without one (chunked) is refused with HTTP 411.
  • A JSON-RPC answer larger than 8 MB isn't sent (the connection closes): ask for fewer results (tx_search's per_page), read genesis with genesis_chunked, or use the GET route, which has no such limit.
  • The RPC, the REST API and gRPC are each limited to 50 requests a second per IP, in bursts of up to 250, and to 30 open connections per IP across the three (over HTTP/2, each request in flight counts as one). A request over the limit gets HTTP 429 (gRPC: UNAVAILABLE).

Full nodes

Self-hosted full nodes come later. The testnet's P2P port is closed, so a node of your own can't join it yet; the public RPC above, the REST API and the indexer (its WebSocket for live updates) are the ways in until then.