Skip to content
ORBITRAONE™

Orbitra L1 · Market services layer

The layer that makes Orbitra L1 market-native.

ApexMatch lives in the market-services layer of Orbitra L1, alongside Aegis, Prism, clearing and settlement. It is part of the protocol rather than a contract deployed on top of it — the property that makes Orbitra L1 a market-native Layer 1.

Explore ApexMatchOrbitra L1
Illustration: Orbitra L1 as six stacked layers: experience at the top, then market services, execution, consensus, data and network at the base. Light travels down through the layers as a transaction is executed and finalized, and back up as confirmed state.
  1. 01ExperienceOrbitra Prime · wallets · apps · institutional APIs
  2. 02Market servicesApexMatch · Aegis · Prism · clearing · settlement
  3. 03ExecutionVectorLanes · deterministic scheduler · NexusWASM
  4. 04ConsensusQSE quorum · finality certificates · validator policy
  5. 05DataState commitments · history · index streams · proofs
  6. 06NetworkRegional ingress · encrypted transport · availability mesh

Layer · Market services

Role in the Orbitra L1 stack

Orders arrive from the experience layer — Orbitra Prime, institutional APIs, wallets and applications — already signed. ApexMatch sequences them, consults Aegis and Prism within the same layer, matches them and produces clearing deltas.

Those deltas are not handed to a separate settlement system. They become transitions that the execution layer runs on VectorLanes and that QSE finalizes, so a fill and its settlement are one event rather than two records waiting to be reconciled.

Because matching is a native module, contracts on NexusWASM reach it through typed calls. Every application on the network shares the same books instead of fragmenting liquidity across separate copies.

Illustration: A signed order travels left to right through six stages: ingress, fair sequencing, the Aegis risk gate, price-time matching, clearing into net deltas and finalization with a QSE proof. A trace of signed evidence records each stage.
  1. 01IngressSigned order
  2. 02SequenceFair ordering
  3. 03RiskAegis gate
  4. 04MatchPrice-time
  5. 05ClearNet deltas
  6. 06FinalizeQSE proof
Deterministic
Same inputs, same fills, same state.
Atomic
Trade and collateral update together.
Observable
Every stage emits signed evidence.
Composable
Apps can invoke native market primitives.

What ApexMatch contributes to the network

  • 01

    Order books as protocol services

    Central limit order books, RFQ and block workflows serve Orbitra Prime and network applications through the same primitives.

  • 02

    Risk in the same layer

    Aegis pre-risk runs beside matching, so an order that would breach a limit is rejected before it reaches the book.

  • 03

    Reference data within reach

    Prism market state sets price bands and pause conditions for each market without leaving the layer.

  • 04

    Settlement as a transition

    Clearing deltas flow directly into execution and finality, with no batch reconciliation between venue and ledger.

Canonical technology pageInside the matching kernelThe canonical ApexMatch page follows a signed order through every stage of the kernel and details its components, failure controls and specifications.Explore ApexMatch

Orbitra L1

Other Orbitra L1 modules