Institutional digital-asset exchange · Global markets, anchored in the Gulf
Integer-exact settlement, an append-only double-entry ledger, and a liquidation engine designed to hold when volatility does not.
Order book depth
The order book lives in the matching engine, which is not deployed in this environment. Its book would be empty in any case until orders rest on it.
Market data: Binance
Spot and USDT-margined perpetuals settle through the same double-entry core — one balance, one audit trail, and no reconciliation gap between products.
Price-time priority, integer-exact
A dedicated matching engine with a durable trade log. Prices and quantities are integer minor units end to end — never floating point — so a replay reproduces the book exactly.
Cross-margin with a real risk stack
Funding, margin tiers, partial liquidation, the insurance fund and auto-deleveraging are separate engines behind ports — each independently testable, each replay-deterministic.
Interface preview — illustrative market data.
Any venue can match orders in a calm market. What separates an exchange is what happens at the edge — so that is the part we engineered first.
Every step above is append-only. A correction is a compensating entry, never a rewrite.
A median across sources with an outlier band set by the risk desk, not by code. Too few healthy sources and the market is declared degraded rather than priced on a guess.
Tiered by position size and loaded from owner-controlled parameter files. The running engine asserts against the owner’s file, so the number on disk is the number in production.
A step closes the smallest amount that restores margin, written as one transaction with all of its legs. There is no half-applied step left to reconcile.
Absorbs the shortfall when a close leaves a deficit — as a balanced ledger movement like any other, never as an edit to history.
The last resort, ranked deterministically from the data, so the same book always produces the same queue.
Money systems fail quietly. These properties hold everywhere, enforced by the schema and the test suite rather than by review.
Every balance change is a balanced set of entries summing to exactly zero per asset. Append-only, enforced by database triggers.
Snapshot plus replay equals full replay, bit for bit. Tie-breaks come from the data, so a shuffled input produces an identical result.
Key custody sits behind a provider abstraction by design — we never write key management, signing, or seed handling ourselves.
When an operation cannot complete it leaves the safe inconsistency — funds held rather than lost, an error rather than an unverified success.
An append-only audit trail with verifiable chaining, so tampering is detectable rather than merely discouraged.
Right-to-left support from day one. The layout mirrors; prices, ladders and charts stay left-to-right.
An exchange being built the way a real money system has to be built — verified, not asserted.