OMEGARequest access

Pre-releaseIntroducing Omega Markets

One exchange.
Across chains.

A verifiable omnichain exchange for spot trading.
Public market depth. Private balances.

Request access Explore the API
A closer look

THE EXCHANGE / 01

Public
depth.

A lit order book. More ways to trade.

Market orders, limit orders and just-in-time quotes, brought together in one spot exchange.

Trade against available depth. This example buys 1 ETH at 3,001.00 USDC.

Explore ways to trade

ETH / USDC

Public order book

Example
Illustrative ETH / USDC public order book. Buy 1 ETH at the available price. Example prices, not live market data.
Price (USDC)Order statusSize (ETH)
3,003.002.40
3,002.001.75
3,001.00Filled1.00
Bid / ask spread
2,999.001.60
2,998.003.10

Market order

Filled at 3,001.00

Takes available sell-side liquidity

Illustrative order flow · Example prices, not live data

YOUR ACCOUNT / 02

Private
balances.

The market is public.
Your balances are private.

Public market depth and private account balances are different parts of the same exchange.

Private from the public market. The operator can see transactions.

Understand the architecture
Public market depth and private account balances are separateMarket participants can see bid and ask prices. Account balances are not displayed in public depth. The Omega operator can see transactions.

Public market

Depth and prices are visible.

Best bid
2,999.00
Best ask
3,001.00

Your balances

Private

Not shown in the public order book

Separate views · Balances stay out of public depth

FOR DEVELOPERS / 03

The exchange.
Your application.

Make it your own.

Build trading experiences around market data, orders and updates.

Explore the developer API
Your application connects to the Omega APIYour application sends orders through the API. Market data and order updates return to your application.

Your application

Trading interface

Orders
  • Send an order. From your application to the Omega API.
  • Read market data. From the Omega API to your application.
  • Receive order updates. From the Omega API to your application.

OMEGA API

One exchange connection

  • Public order book
  • Order execution
Conceptual integration · Data and order flow, not API endpoints

BUILT WITH A CLEAR BOUNDARY

Know what
you’re trusting.

Execution verification uses a TEE. The operator can see transactions; current execution is not ZK-proven.

Understand the trust boundary
The execution trust boundaryTransaction input enters the operator boundary, which contains a TEE for execution verification. The operator can see transactions. Current execution is not ZK-proven.

Transaction input

Operator boundary

Operator can see transactions

TEE

Execution verification

Execution result

Current execution is not ZK-proven

Your next move.
Across chains.

Request access

Pre-release. Explore what comes next.