Product model
| Property | Contract |
|---|---|
| Product type | Perpetual swaps |
| Repo-listed tradable perps in shared market specs | ETHP, BTCP, SPCXP |
| Test-only spec product | DOGEP |
| Margin model | Cross-margin at strategy level |
| Matching model | Central limit order book with price-time priority |
Source artifact lineage
| Source layer | Role |
|---|---|
| operator core market/spec constants | production-style baseline for the published constraint table |
| this public reference page | canonical public explanation of the baseline values and caveats |
| generated API routes | runtime-oriented schema lookup for live symbol exposure and client tolerance to listing changes |
Use this page when
| If you need… | Use this page because… |
|---|---|
| symbol-level product and order-shape facts | it is the factual reference carrier for those market-spec constraints |
| pre-trade validity boundaries | it collects the major acceptance constraints before matching |
| the public baseline for repo-backed market-spec values | it exposes current code-backed baselines while warning against assuming universal live deployment parity |
Pre-trade constraint categories
| Constraint | Enforcement |
|---|---|
| Tradable product validity | Required before sequencing |
| Tick-size compliance | Price must be a multiple of product tick size |
| Minimum order size | Amount must be a multiple of product minimum |
| Order type validity | Limit/market compatibility checks |
| Max open orders per product | Enforced per strategy per symbol (20 default builds, 10 with alpha1) |
| Max order notional | Product-specific notional cap enforced before sequencing |
| Price-deviation bound | Explicitly priced orders are checked during sequencing; market orders are bounded during matching by mark-price-relative max_taker_price_deviation when no taker limit is present |
Repo shared market-spec values
These are the shared market-spec values currently defined in repo market constants. They are a code-backed baseline, not a guarantee that a given deployment exposes the same live listing set.| Symbol | Tick size | Minimum order size | Max order notional | Max taker price deviation |
|---|---|---|---|---|
ETHP | 0.1 | 0.0001 | 1,000,000 | 0.02 |
BTCP | 1 | 0.00001 | 1,000,000 | 0.02 |
SPCXP | 0.1 | 0.0001 | 1,000,000 | 0.02 |
Test-only market spec
| Symbol | Tick size | Minimum order size | Max order notional | Max taker price deviation |
|---|---|---|---|---|
DOGEP | 0.000001 | 1 | 100,000 | 0.1 |
Non-baseline product families
Feature-gated or non-baseline product families can exist in repo sources without becoming part of the current published contract. Treat the tables above as the current public baseline, not as a statement that every repo-carried family is live and public today.Internal symbol note
| Symbol | Role |
|---|---|
DDXP | Internal dummy DDX perp used for oracle and DDX-fee-discount logic; not treated as a normal tradable product |
What this page does not answer alone
| Need | Use instead |
|---|---|
| exact solvency and liquidation threshold formulas | Margin Requirements |
| mark-price inputs and funding cadence details | Price Feeds and Mark Price Inputs and Funding Rate Logic |
| broader rationale for why these controls exist | Price Formation, Risk Controls, and Solvency |
| visibility of public versus restricted API families | API Reference |
Settlement and checkpoint timing
| Mechanic | Public contract |
|---|---|
| Product expiry | Public products are perpetual swaps rather than expiring futures |
| Funding transfer timing | Funding is applied on settlement boundaries rather than on every trade event |
| PnL settlement timing | Realized settlement updates are checkpoint- and settlement-driven events, not per-fill blockchain settlements |
| Withdrawal finality reference | Checkpointed state is the public anchor for settlement and withdrawal eligibility |
Market availability and maintenance posture
| Topic | Public contract |
|---|---|
| Trading-hours model | Public docs do not define asset-specific market-hours windows; treat product availability as continuous unless a published maintenance or status notice says otherwise |
| Maintenance posture | Operational maintenance can still affect availability even when product rules stay unchanged |
| Runtime confirmation path | Use public status, changelog, and support routes when availability or maintenance posture matters operationally |
Fee and insurance context
| Topic | Public contract |
|---|---|
| Fee discount behavior | DDX-linked fee-discount constants are documented in Trade Mining Parameters |
| Effective fee state | Public docs do not currently publish one timeless maker/taker fee schedule table for every deployment; treat fee posture as deployment-conditional unless a published reference says otherwise |
| Insurance-fund relevance | Insurance-fund flows matter during liquidation and ADL, and their public safety role is documented in Trading Safeties and Guards |
Related references
- Trading Safeties and Guards
- Margin Requirements
- Rate Limits and Access Tiers
- Trade Mining Parameters
- Glossary