Skip to content
ORBITRAONE™

Orbitra L1 · Network boundary

The edge where other networks connect.

GateMesh operates at the outer boundary of Orbitra L1, beside the network layer’s regional ingress, encrypted transport and availability mesh. It is the governed path by which assets and messages from other chains enter and leave the network.

Explore GateMeshOrbitra 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 · Network

Role in the Orbitra L1 stack

The network layer carries Orbitra L1’s own traffic: orders from regional gateways, blocks and votes between validators, state streams to indexers. GateMesh extends that edge outward, running independent clients for each connected chain.

Nothing observed at the edge changes state directly. A verified, capped transfer becomes a transaction like any other — scheduled in the execution layer, recorded in the data layer and finalized by QSE. Only then are represented assets usable by market services and applications.

External prices take a different route, through Prism in the market-services layer. Keeping the two paths apart means a data fault cannot move assets and a route fault cannot move prices.

Illustration: A cross-chain transfer passes five gates: independent clients observe the source chain, proofs are verified against finality rules, asset and route caps are applied, the transfer is executed by escrow, mint or release, and a recovery path can pause and resolve disputes.
  1. 01ObserveIndependent chain clients
  2. 02VerifyProof and finality rules
  3. 03LimitAsset and route caps
  4. 04TransferEscrow / mint / release
  5. 05RecoverPause and dispute path

What GateMesh contributes to the stack

  • 01

    Independent observation

    Connected chains are followed by GateMesh’s own clients rather than through a single relayer.

  • 02

    Finality alignment

    Each source chain’s finality rule is met before its events can change Orbitra L1 state.

  • 03

    Bounded exposure

    Asset and route caps limit what any single connection can carry, including value still in flight.

  • 04

    Contained failure

    Circuit breakers pause one route while the rest of the network keeps executing and finalizing.

Canonical technology pageThe full interoperability pipelineThe canonical GateMesh page covers all five stages, the escrow, mint and release models, security controls, the recovery path and specifications.Explore GateMesh

Orbitra L1

Other Orbitra L1 modules