DarkX Documentation
DarkX is a perpetual futures DEX built around two ideas the market hasn't combined: dark pool execution and zero-knowledge privacy. Orders cross inside private pools so size never hits the public book. Positions and liquidation levels are sealed with zk proofs. Underneath, orders route through Orderly Network's omnichain liquidity and settle on Ethereum mainnet.
You trade. The chain only sees the net.
What you'll find here
- How it works — the commit → seal → match → settle lifecycle
- Getting started — connect, deposit, place your first order
- Privacy model — what's hidden, what's public, and why
- Security & audits — current audit status and disclosure policy
How it works
Every order moves through four layers. The first two happen on your device; the chain never sees a readable order, only the netted result.
Commit
Your client builds a Poseidon commitment of the order and signs it locally. The raw order — side, size, price — never leaves your machine in the clear.
Seal
Uniform-size sealed payloads enter the mempool. Every order looks identical from the outside, so size and intent can't be inferred from the wire.
Match
A zk circuit clears the batch inside a proof. Orders cross against each other and against Orderly liquidity without any party reading the individual orders.
Settle
Net positions route through Orderly Network and settle on Ethereum mainnet. The chain records the net outcome — not who traded what.
Architecture
DarkX is a thin, privacy-preserving layer on top of proven infrastructure rather than a from-scratch exchange. Three pieces do the work:
Execution — Orderly Network
Matching and liquidity come from Orderly's omnichain orderbook. DarkX doesn't run its own market makers; it routes netted flow into shared liquidity so traders get real depth from day one.
Privacy — zkPrivacy circuits
Orders are Poseidon commitments salted with a client nonce. A proving circuit verifies that a batch was matched correctly without revealing the orders inside it. The relayer that sequences sealed payloads cannot read them.
Settlement — Ethereum mainnet
Net positions and collateral settle on Ethereum. Verification of the matching proof happens on-chain, so correctness is checkable by anyone without exposing individual traders.
Getting started
- Connect a wallet. DarkX supports any EVM wallet on Ethereum mainnet.
- Deposit collateral. Positions are margined in
USDC. Your balance funds margin across all markets. - Pick a market. Choose a perpetual (e.g.
ETH-PERP) and set your leverage. - Place an order. Your client seals it locally before it ever hits the network — nothing to configure.
- Manage the position. Your size, entry, and liquidation level stay private to you.
Markets
Live perpetual markets, all margined in USDC with up to 100× leverage.
NoteMarket list and leverage tiers are configured by governance and may change. Always confirm the live tier in the app before sizing a position.
Fees & leverage
| Item | Value | Notes |
|---|---|---|
| Maker fee | 0.02% | Rebate-eligible on resting flow |
| Taker fee | 0.06% | Charged on fill |
| Max leverage | up to 100× | Per-market, see Markets |
| Collateral | USDC | Cross-margined |
| Funding | 8h interval | Paid between longs and shorts |
Privacy model
Privacy on DarkX is structural. Here's exactly what is hidden and what is public.
| Data | Visibility |
|---|---|
| Your order side, size, and price | Private |
| Your open position | Private |
| Your liquidation level | Private |
| Net market position (aggregate) | Public |
| Settlement on Ethereum | Public |
Doctrine
- All orders are Poseidon commitments salted with a client nonce.
- The relayer that sequences orders cannot read them.
- The chain only ever sees the net.
- Your anonymity set is the entire pool — sealed orders are indistinguishable.
Security & audits
DarkX is being built in the open. This table reflects current, honest status — not aspirational claims.
| Auditor | Scope | Status |
|---|---|---|
| Trail of Bits | zk circuits + verifier contracts | In review |
| Spearbit | Orderbook integration | Scheduled Q3 2026 |
Reporting a vulnerability
Email security@darkx.xyz with details. Do not open public issues for security bugs. DarkX follows a 90-day responsible-disclosure window, with bounties paid in USDC for confirmed findings, tiered by severity.
SDK
The DarkX TypeScript SDK seals orders client-side and submits them to the relayer. Install:
npm install @darkx/sdkPlace a sealed order:
import { DarkX } from '@darkx/sdk';
// orders are sealed locally before they ever hit the wire
const dx = new DarkX({ wallet, chain: 'ethereum' });
await dx.order({
market: 'ETH-PERP',
side: 'long',
size: '2.5',
leverage: 10,
});FAQ
Is DarkX itself the dark pool?
No. DarkX is a perpetual futures DEX. Dark pools and zk privacy are how it executes — they're features of the protocol, not the brand identity.
What can the relayer see?
Nothing readable. Orders arrive as uniform-size sealed commitments. The relayer sequences them but cannot decode side, size, or price.
What does the chain record?
The net outcome of a matched batch, plus the verification of the matching proof. It does not record who traded what.
Who provides liquidity?
Orderly Network's omnichain orderbook. DarkX routes netted flow into shared liquidity rather than running isolated market makers.
Is it live and audited?
The trading frontend and brand are shipped. The zk proving layer is in active development and the circuits are in audit review — not yet complete. See Security & audits.
Risk disclaimer
This documentation is for informational purposes only and is not financial, investment, or legal advice. Perpetual futures are leveraged instruments and can result in the total loss of your collateral. Privacy and cryptography features described here are under active development and may be incomplete or unaudited at the time you read this.
Use of DarkX may be restricted in your jurisdiction. You are responsible for your own compliance, custody, and risk management. Never deposit funds you cannot afford to lose.