Paradex

• Name: Paradex
• URL: https://www.paradex.trade/
• Category: derivatives-exchange operating company / appchain-and-api operator / privacy-council and venue-control boundary
• Tags: ethereum-ecosystem
• Summary: Paradex belongs in companies/, not only projects/paradex, because the practical authority is not just the Starknet-appchain mechanism. The named operator publishes the canonical trading UI, vault surface, docs, and GitHub organization; runs the main API and cloud orderflow path; sets a weekday release cadence with explicit venue modes; and sits inside the Privacy Council structure that can decrypt and publish state in emergencies. The project note explains the exchange and privacy architecture; this entity note is for the venue-operated shell around endpoints, infrastructure, release policy, emergency controls, and the operator-shaped privacy perimeter users actually inherit.
• What it does:
  • Operates the Paradex trading venue, mobile path, vault surface, docs, and developer repositories as the canonical production entrypoints into the exchange
  • Publishes and runs the main REST API endpoint and the cloud-hosted orderflow path that traders, bots, and integrations use to reach the venue
  • Operates exchange infrastructure from AWS AP-NORTHEAST-1 (Tokyo) with AWS Global Accelerator routing according to the official API docs
  • Defines the live maintenance and release workflow, including weekday deployment windows, venue mode transitions, and temporary order-admissibility constraints
  • Sits inside the privacy-and-recovery control surface through Paradex Cloud order visibility, emergency decryption design, and the stated Privacy Council membership structure
  • Packages account-security workflow through its owner-plus-guardian account model and CLI-driven hardening path
• Key claims:
  • The official links page centralizes paradex.trade, docs.paradex.trade, app.paradex.trade, the vault surface, and the tradeparadex GitHub organization as the domains and repos users are expected to trust first
  • The privacy docs say orders are only stored on Paradex Cloud and are only known to the operators of Paradex Cloud, which makes offchain order custody and visibility part of the real control surface
  • The same privacy docs say the Paradex Privacy Council holds decryption keys for emergencies and list the current members as Paradex Foundation, Paradex, and Karnot, which is unusually direct evidence that the privacy story still routes through named entities
  • The maintenance docs say Paradex performs weekday releases during a fixed UTC window and transitions the venue through CANCEL_ONLY, POST_ONLY, and OK modes, meaning live market behavior is explicitly operator-shaped during routine deployments
  • The API docs publish a single mainnet REST endpoint at https://api.prod.paradex.trade/v1 and say the infrastructure runs in AWS Tokyo with Global Accelerator routing, which makes venue access and latency posture part of the company boundary rather than only the chain design
  • The security docs make emergency authority legible by stating Paradex can block L1 deposits and limit L1 or L2 withdrawals, while the guardian-key docs show Paradex packaging account hardening and recovery workflow through its own account model and CLI materials
• Whitepaper: No separate company whitepaper is the point here. The most useful primary materials are the official links, privacy, maintenance, API, and security docs captured in ../whitepapers/paradex-company-primary-sources-2026-08-12.md.
• Sources:
  • https://www.paradex.trade/
  • https://docs.paradex.trade/docs/getting-started/official-links.md
  • https://docs.paradex.trade/trading/privacy.mdx
  • https://docs.paradex.trade/docs/maintenance-mode.md
  • https://docs.paradex.trade/api/general-information/api-urls.md
  • https://docs.paradex.trade/api/general-information/server-location.md
  • https://docs.paradex.trade/chain/security/security-lockdown.md
  • https://docs.paradex.trade/chain/security/guardian-keys.md
  • ../whitepapers/paradex-company-primary-sources-2026-08-12.md

Internal linkages

• Protocol note: paradex.
• Useful operator / venue comparisons: hyperliquid-labs, megaeth-labs, and flashbots.
• Useful privacy-and-account-shell comparison: tools-for-humanity.

Protocol / company boundary

• Keep projects/paradex focused on the mechanism layer: the Starknet appchain, privacy architecture, margin and product design, API-native trading surface, and the way the exchange bundles execution, chain, and data publication.
• Keep this entity note focused on the named operator boundary that publishes the official UI and API entrypoints, runs the cloud orderflow path, schedules venue-wide releases, controls emergency security levers, and participates in the Privacy Council structure around decryption and recovery.
• That split matters because the analytical question is not only how does Paradex work? but also who currently operates the easiest path into Paradex, and which parts of the venue's privacy and continuity story still depend on named organizations?

Control surface

• The sharpest present-day leverage sits in the venue-operated shell: canonical app and vault domains, the main API endpoint, infrastructure placement in Tokyo, cloud order custody, weekday release windows that change market mode, and operator-defined emergency deposit / withdrawal controls.

• Paradex’s appchain and zk machinery matter, but the production trading experience is still company-shaped because users and bots reach the system through Paradex-managed infrastructure and a privacy model that explicitly reserves emergency decryption power to named entities.

• Read the durable risk here as privacy-preserving exchange architecture with a still-concentrated operating shell, not as a claim that the operator boundary has disappeared just because the stack uses an appchain and zero-knowledge proofs.

• Last reviewed: 2026-08-12 UTC