Paradex

• Name: Paradex
• URL: https://www.paradex.trade/
• Category: privacy-preserving derivatives exchange / Starknet appchain / trading infrastructure
• Tags: ethereum-ecosystem
• Summary: Paradex is a privacy-heavy derivatives venue with its own Starknet appchain. The useful cut is vertical integration: exchange UI, APIs, margin stack, chain, and emergency decryption path all sit in one operator surface. More trading infrastructure than neutral exchange primitive. Keep this note on the exchange and privacy mechanism; the named venue-operator boundary around canonical domains, API access, release cadence, cloud order custody, and Privacy Council participation now lives in paradex.
• What it does:
  • Operates a decentralized exchange where users trade directly from wallets across perpetual futures, dated options, spot markets, and some commodity-linked markets
  • Runs as a Starknet appchain / dedicated L2 environment rather than as a simple smart-contract application on a shared chain
  • Offers unified-margin trading, sub-accounts, vault products, and advanced order types for active traders and market makers
  • Exposes a large REST and WebSocket API surface for bots, market-data consumers, account management, algorithmic orders, and block-trade workflows
  • Implements privacy-focused trading infrastructure in which orders live in Paradex Cloud, account data is masked by default on the appchain RPC, and encrypted state diffs are posted to Ethereum with emergency decryption delegated to a Privacy Council
  • Publishes SDKs, code samples, CLI tooling, signing libraries, and agent-oriented repos that support systematic and API-native usage
• Key claims:
  • Official docs describe Paradex as a decentralized exchange built as a Starknet appchain that combines centralized-exchange performance with blockchain security and transparency
  • The public site frames Paradex around liquidity, performance, and privacy as foundational primitives, not just around token incentives or a consumer trading UI
  • Paradex claims its privacy model is end-to-end: orders, positions, and trades remain private in Paradex Cloud, on Paradex Chain, and in the encrypted data ultimately posted to Ethereum
  • The roadmap and docs show Paradex expanding beyond perpetuals into spot, options, vaults, portfolio margin, and a broader chain / privacy stack rather than remaining a single-market venue
  • The GitHub organization and docs surface suggest Paradex is building not just an exchange UI but a full operator / developer stack including SDKs, CLI tools, code samples, AI-agent skills, and an MCP server
• Whitepaper: No classic standalone whitepaper or litepaper was found during this pass. The strongest primary materials were Paradex’s official site, public docs, API docs, roadmap, and GitHub organization / docs repository; see ../whitepapers/paradex-primary-sources-2026-04-26.md.
• Sources:
  • https://www.paradex.trade/
  • https://docs.paradex.trade/
  • https://docs.paradex.trade/docs/getting-started/what-is-paradex.mdx
  • https://docs.paradex.trade/docs/getting-started/roadmap.mdx
  • https://docs.paradex.trade/trading/privacy.mdx
  • https://docs.paradex.trade/api
  • https://github.com/tradeparadex
  • https://github.com/tradeparadex/paradex-docs
  • https://raw.githubusercontent.com/tradeparadex/paradex-docs/main/README.md

Internal linkages

• Company / operator boundary for venue access, release policy, and privacy-council structure: paradex.
• Best high-performance exchange-stack contrast: hyperliquid.
• Best privacy-first execution contrast: renegade.

Protocol / company boundary

• Keep this note focused on the mechanism layer: the Starknet appchain, unified-margin venue design, API-native trading stack, privacy architecture, and the way Paradex bundles chain and exchange logic into one product surface.
• Use paradex for the named operator boundary around canonical domains, cloud order custody, main API endpoint publication, maintenance cadence, emergency deposit / withdrawal controls, and the entity-level Privacy Council path.
• That split matters because how does Paradex's exchange stack work? and which organization operates the default route into that stack? are related but not identical questions.

Control surface

• At the mechanism layer, real leverage sits in Paradex Cloud order handling, API and margin-policy defaults, chain operations, vault and account controls, and the Privacy Council path that can force emergency decryption.

• For the named venue-operator layer around canonical domains, API publication, maintenance windows, infrastructure placement, and emergency security levers, read paradex.

• Read Paradex as vertically integrated exchange infrastructure with privacy features, not as a neutral market primitive.

• Last reviewed: 2026-08-12 UTC