ZK-SNARK VERIFIED · BATCH SETTLEMENT · 100K ORDERS/SEC · P99 < 1MS · MEV EXPOSURE: ZERO · ZK-SNARK VERIFIED · BATCH SETTLEMENT · 100K ORDERS/SEC · P99 < 1MS · MEV EXPOSURE: ZERO · ZK-SNARK VERIFIED · BATCH SETTLEMENT · 100K ORDERS/SEC · P99 < 1MS · MEV EXPOSURE: ZERO · ZK-SNARK VERIFIED · BATCH SETTLEMENT · 100K ORDERS/SEC · P99 < 1MS · MEV EXPOSURE: ZERO · ZK-SNARK VERIFIED · BATCH SETTLEMENT · 100K ORDERS/SEC · P99 < 1MS · MEV EXPOSURE: ZERO · ZK-SNARK VERIFIED · BATCH SETTLEMENT · 100K ORDERS/SEC · P99 < 1MS · MEV EXPOSURE: ZERO · ZK-SNARK VERIFIED · BATCH SETTLEMENT · 100K ORDERS/SEC · P99 < 1MS · MEV EXPOSURE: ZERO · ZK-SNARK VERIFIED · BATCH SETTLEMENT · 100K ORDERS/SEC · P99 < 1MS · MEV EXPOSURE: ZERO ·

[ PROTOCOL v0.1 — ARBITRUM ]

TRADE WITHOUT
REVEALING ANYTHING.

Orders are cryptographic commitments.
The engine never sees price, pair or size.
Settlement is verified. Nothing is revealed.

100,000
ORDERS/SEC
< 1ms
P99 LATENCY
256
ORDERS/BATCH
0.05%
PROTOCOL FEE
HOW IT WORKS

FOUR STEPS,
ZERO KNOWLEDGE.

Each step is cryptographically isolated. The protocol never has enough information to reconstruct your order. Not even the operator knows what you're trading.

01

COMMIT

PEDERSEN COMMITMENT

Pedersen commitment generated locally. Price, pair and size never leave the device.

02

PROVE

halo2 / RUST WASM

Rust circuit generates a ZK proof of order validity — collateral, format, limits.

03

MATCH

GO MATCHING ENGINE

Engine receives only commitments and validity bits. Never sees real order data.

04

SETTLE

SOLIDITY + EVM

Batch of 256 matched pairs with aggregated proof verified on-chain. Atomic release.

PROTOCOL GUARANTEES
ZERO
DATA LEAKED
Private by default
NONE
MEV EXPOSURE
No visible mempool
256
TRADES / TX
Aggregated proofs