Orbitra L1 · Market services layer
The boundary where outside prices become state.
Prism sits in the market-services layer of Orbitra L1 at a boundary. It is where information from outside the network — exchange prices, dealer quotes and benchmarks — becomes state the rest of the stack can rely on.
- 01ExperienceOrbitra Prime · wallets · apps · institutional APIs
- 02Market servicesApexMatch · Aegis · Prism · clearing · settlement
- 03ExecutionVectorLanes · deterministic scheduler · NexusWASM
- 04ConsensusQSE quorum · finality certificates · validator policy
- 05DataState commitments · history · index streams · proofs
- 06NetworkRegional ingress · encrypted transport · availability mesh
Layer · Market services
Role in the Orbitra L1 stack
Every neighboring module consumes what Prism publishes. ApexMatch derives price bands, Aegis values collateral and positions, funding and liquidation reference index prices, and tokenized real-world assets draw valuation inputs — all from the same signed market state.
Prism writes into the execution layer as ordinary state. Values are read deterministically on VectorLanes and finalized by QSE together with the transactions that used them, so every validator sees the same price at the same point in history.
At the network edge, GateMesh governs assets arriving from other chains. Together they form the protected boundary where external truth enters Orbitra L1: Prism for data, GateMesh for value.
- 01SourcesExchanges, dealers, benchmarks
- 02NormalizeTime, units, quality
- 03AggregateRobust median + weighting
- 04ConfidenceFreshness and dispersion
- 05PublishSigned market state
What Prism contributes to the stack
- 01
One reference per instrument
Risk, matching and settlement read the same published value, so they never disagree about what a price was.
- 02
Confidence as data
Each value carries a confidence score, derived from freshness and dispersion, that downstream modules can act upon.
- 03
Automatic protection
Falling confidence trips circuit breakers in the markets that depend on the affected price.
- 04
Replayable history
Because prices are committed state, any past decision can be re-examined against the exact value it used.
Orbitra L1
Other Orbitra L1 modules
- QSE in Orbitra L1The consensus layer.
- VectorLanes in Orbitra L1The parallel execution layer.
- ApexMatch in Orbitra L1Market services as protocol modules.
- NexusWASM in Orbitra L1The native contract runtime.
- GateMesh in Orbitra L1The interoperability boundary.
- Q-Switch in Orbitra L1Agility across every layer.