Cowrie Research

paradex-company-primary-sources-2026-08-12

3 min read

Paradex company primary-source snapshot

Fetched: 2026-08-12 UTC

1) Official links page

Source: https://docs.paradex.trade/docs/getting-started/official-links.md

Selected excerpts from the official docs:

Main website: https://paradex.trade

Documentation: https://docs.paradex.trade

GitHub: https://github.com/tradeparadex

Paradex UI - Main trading platform: https://app.paradex.trade/

Paradex Vaults - Secure asset management: https://app.paradex.trade/vaults

Additional signals from the source:

  • This page is useful company-layer evidence because it centralizes the canonical domains, trading UI, vault surface, docs, and code repositories users are expected to trust first.
  • That makes Paradex itself the naming, distribution, and endpoint authority around the live venue rather than merely a passive protocol brand.

2) Privacy page

Source: https://docs.paradex.trade/trading/privacy.mdx

Selected excerpts from the official docs:

Orders are only stored on the Paradex Cloud and are only known to the operators of Paradex Cloud.

The Paradex Privacy Council holds the decryption keys needed to decrypt in the event of an emergency.

The current members of the Privacy Council are:

  1. Paradex Foundation
  2. Paradex
  3. Karnot

Additional signals from the source:

  • This is the sharpest first-party evidence that the venue’s privacy guarantees still route through named operator entities, not only through neutral zk machinery.
  • The page also makes clear that Paradex Cloud order handling and emergency decryption are part of the practical control surface.

3) Maintenance & Releases

Source: https://docs.paradex.trade/docs/maintenance-mode.md

Selected excerpts from the official docs:

Paradex performs releases on all weekdays during the following window: 4:30 AM UTC / 12:30 PM SGT

During each release, the platform transitions through three modes: CANCEL_ONLY (~2 min) POST_ONLY (~2 min) OK

Additional signals from the source:

  • This is useful company-layer evidence because Paradex publishes a routine operator-controlled maintenance cadence that directly changes venue behavior and order admissibility.
  • The same page documents price-band restrictions during maintenance and routes users to a Paradex-run status and announcement surface for live operational truth.

4) API URLs and server location

Sources:

Selected excerpts from the official docs:

Mainnet REST API URL: https://api.prod.paradex.trade/v1

Our servers are located in the AWS AP-NORTHEAST-1 region (Tokyo).

Paradex leverages AWS Global Accelerator to route traffic to our infrastructure in Tokyo.

Additional signals from the source:

  • Paradex does not merely describe protocol mechanics; it publishes the canonical API endpoint and explains where the venue infrastructure actually runs.
  • That matters because trading and account access remain operationally concentrated in a company-defined infrastructure shell.

5) Security controls and guardian keys

Sources:

Selected excerpts from the official docs:

Paradex has following controls to manage funds security

  1. Block L1 Deposits
  2. Limit L1 Withdrawals
  3. Limit L2 Withdrawals

Paradex accounts, based on ArgentX, use an owner key and a guardian key for enhanced security.

Additional signals from the source:

  • This is useful company-layer evidence because the docs make emergency deposit/withdrawal controls an explicit part of the live operating shell.
  • The guardian-key page also shows Paradex packaging account-security workflow and recovery posture through its own CLI and account model rather than only pointing users to generic Starknet primitives.

Notes

  • Paradex clears the bar for a company/entity note because the practical dependency is not only a privacy-preserving derivatives appchain exists; it is that a named operator publishes the canonical UI, vault surface, API endpoint, maintenance cadence, infrastructure region, emergency security controls, and privacy-council structure users inherit.
  • The project note should stay on the exchange/appchain mechanism, privacy design, and market structure. The company note should stay on venue operation, endpoint truth, release cadence, emergency controls, and the operator-shaped privacy and account-security shell.

Graph View