Architecture and trust
Omega's current scope is a verifiable omnichain exchange with a lit order book and private balances.
Trading model#
Market and limit orders are part of the target exchange API. Public market data and private account views serve different purposes. An indicative just-in-time estimate helps prepare a trade; it does not reserve a price or guarantee execution.
What verification means#
A trusted execution environment (TEE) supports verification of execution. It does not make Omega's operator blind to transactions. Do not equate verifiability with operator-blind confidentiality.
This documentation does not claim current zero-knowledge proofs or a universal recovery guarantee. The precise released proof and settlement interfaces must be checked against the environment used.
Data availability#
MVP data availability relies on server-hosted data. A production availability provider is unresolved. Execution verification does not itself guarantee that all data required for an independent recovery remains available.
Privacy boundaries#
| Surface | Boundary |
|---|---|
| Order book | Lit market model; public market-data disclosure still follows the applicable contract. |
| Account balances | Private account views require authorized access. |
| Operator | The operator can see transactions; TEE verification does not hide them. |
| Settlement | A separate observation from API acceptance or matching completion. |
Integrator responsibility#
Use exact asset identities, obtain explicit spending authority, preserve operation identity and reconcile results. Keep private account data out of public logs. Treat verification, finality, availability and external delivery as separate questions.