Skip to content
ORBITRAONE™

Orbitra L1

Built for markets. Open to everything else.

Orbitra L1 is the sovereign Layer 1 of ORBITRA ONE™: non-EVM-native and market-native by design. Its execution, consensus, storage and fee systems are built around deterministic financial state, while the network stays open to general applications.

Explore the architectureRun a validator
  • Deterministic BFT finality
  • Parallel VectorLanes
  • Native ApexMatch
  • NexusWASM + EVM Capsule

The trading platform is not placed on the chain; the chain understands the market.

Matching, risk, oracle data, clearing and settlement are native deterministic modules of the protocol rather than contracts competing for block space. Everything else — payments, games, agents, enterprise logic — runs in NexusWASM, with Ethereum compatibility contained in an isolated capsule.

Layered architecture

Six layers, with markets inside the protocol.

Market services sit between the experience people use and the execution that makes it final.

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

Orbitra L1 drawn as six stacked layers, from top to bottom: Experience (Orbitra Prime, wallets, applications and institutional APIs); Market services (ApexMatch, Aegis, Prism, clearing and settlement); Execution (VectorLanes, the deterministic scheduler and NexusWASM); Consensus (the QSE quorum, finality certificates and validator policy); Data (state commitments, history, index streams and proofs); and Network (regional ingress, encrypted transport and the availability mesh).

Engineered for financial state

Four core systems, shaped by markets.

Orbitra L1 is non-EVM-native by design. Each core system answers a requirement that markets impose.

  1. 01

    Execution

    Native market modules and a deterministic scheduler run independent state in parallel, so unrelated markets do not wait on each other.

  2. 02

    Consensus

    A QSE quorum certificate makes each transition final. Settlement does not depend on waiting for confirmation depth.

  3. 03

    Storage

    State commitments, history, index streams and proofs are kept so that any balance, position or fill can be proven and reconstructed.

  4. 04

    Fees

    Compute and storage carry explicit resource prices, and market ordering follows declared sequencing rules rather than fee bidding.

Performance envelope

Capacity engineered for global markets.

Full-capacity architecture
1,000,000 TPSEngineered aggregate capacity across parallel execution lanes.
Finality class
Sub-secondDeterministic BFT finality through QSE quorum certificates.
Global market access
24/7Always-on settlement across every time zone.
Native plus compatibility
Multi-VMNexusWASM at the core, with an isolated EVM Capsule.

1,000,000 transactions per second represents the engineered aggregate full-capacity architecture of ORBITRA ONE™ and is intended for validation under defined benchmark conditions.

The modules

Eight modules. One deterministic state.

Follow each module to its place in the Orbitra L1 stack.

Consensus

QSE

Quorum-Staked Execution combines stake, authority and verified work; a Byzantine quorum signs each transition for deterministic finality. QSE in the stack

Execution

VectorLanes

Parallel lanes — 256+ in the engineered configuration — run independent state, with conflict-aware scheduling that keeps results deterministic. VectorLanes in the stack

Market services

ApexMatch

Order books run inside the protocol, and every fill clears and settles in the same atomic transition that matched it. ApexMatch in the stack

Contracts

NexusWASM

The primary contract environment: capability-scoped WebAssembly, explicit resource pricing and native calls into market modules. NexusWASM in the stack

Compatibility

EVM Capsule

An isolated domain for Ethereum tooling and bytecode, with independent resource limits, a rate-limited asset gateway and circuit breakers. Explore EVM Capsule

Data

Prism

Diverse price sources become one signed market state, combined by robust median and weighting and scored for freshness and dispersion. Prism in the stack

Interoperability

GateMesh

Cross-chain transfers face independent chain clients, proof and finality rules, asset and route caps, and a pause-and-dispute recovery path. GateMesh in the stack

Cryptography

Q-Switch

Cryptography can change without a hard break: each signature suite carries a version, hybrid credentials bridge old and new, and accounts rotate keys and migrate addresses toward post-quantum-ready interfaces. Q-Switch in the stack

Validators

Secured by accountable operators.

Validators secure Orbitra L1 through QSE. Stake puts economic weight behind each signature, authority assigns who proposes and who sits on each committee, and verified work — availability, validation and service quality — shapes their rewards.

Protocol security rests on formal specifications, client diversity and slashing for provable misbehavior. QSE is a BFT protocol, not proof-of-work mining.

  • Stake-weighted security set
  • Explicit proposer and committee duties
  • Rewards shaped by verified service
  • Slashing for provable misbehavior
Become a validator
Illustration: Three forces — stake, authority and verified work — shape a validator set. Validators vote on the same state transition; once a configured Byzantine quorum has signed, their signatures form a quorum certificate and one state is finalized.
  1. StakeEconomic security and slashing exposure
  2. AuthorityProposer and committee duties
  3. WorkVerified availability, validation and service

Validator votes

Quorum certificate

Finalized state

7 / 10

Build on a chain that understands markets.

Deploy contracts in NexusWASM, bring Ethereum code through EVM Capsule, or help secure the network as a validator.

Build on Orbitra L1Register validator interest