Skip to content
ORBITRAONE™

Orbitra L1 · Execution layer

The layer where parallel work stays deterministic.

VectorLanes is the parallel core of the execution layer in Orbitra L1. It sits between the market services above and QSE consensus below, turning a stream of transactions into deterministic results that can be finalized as one truth.

Explore VectorLanesOrbitra 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 · Execution

Role in the Orbitra L1 stack

The execution layer brings together three parts: the lanes themselves, the deterministic scheduler that feeds them and the NexusWASM contract runtime. The scheduler reads the state each transaction declares, maps where transactions conflict and assigns independent work to separate lanes. Work that touches shared state is ordered, never raced.

Above the layer, ApexMatch, Aegis and Prism generate transitions — fills, margin deltas, funding and oracle updates. Below it, QSE certifies the outcome while the data layer commits state roots and streams index output. VectorLanes is where the 1,000,000 TPS full-capacity architecture takes shape: 256+ parallel lanes in the engineered configuration, batched signature checks and local state access.

Parallelism never changes the answer. Every validator applies the same schedule to the same input and must reach the same state root before a quorum will sign it.

Illustration: Hundreds of independent execution lanes carry transactions in parallel. They pass through validation rings and converge at a single finality beacon, showing parallel execution that resolves into one deterministic, finalized state.
Independent lanesFinality beacon
256+
Parallel lanes
Batched
Signature checks
Local
State access
Streamed
Index output

What VectorLanes contributes to the stack

  • 01

    Throughput from independence

    Unrelated markets, accounts and contracts execute at the same time instead of queuing behind one another.

  • 02

    Deterministic ordering

    Conflict-aware scheduling fixes the order of dependent transactions, so replay on any validator yields identical results.

  • 03

    Isolation under load

    Activity concentrated in one market does not occupy the lanes serving unrelated markets and applications.

  • 04

    A clean handoff to consensus

    Lanes converge into one ordered set of transitions for QSE, with streamed output for indexers and the data layer.

Canonical technology pageThe complete VectorLanes referenceThe canonical VectorLanes page follows a batch from signature verification to streamed output and details the scheduler, serial equivalence, determinism controls and specifications.Explore VectorLanes

Orbitra L1

Other Orbitra L1 modules