Skip to content
ORBITRAONE™

Orbitra L1 · Across all layers

Cryptographic agility, from account to wire.

Q-Switch is not confined to one layer of Orbitra L1. Account keys authorize activity at the top of the stack, validator keys secure consensus in the middle and key exchange protects transport at the base. Q-Switch keeps all of them versioned and able to migrate.

Explore Q-SwitchOrbitra 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

Orbitra L1

Role in the Orbitra L1 stack

In the experience and market-services layers, every order, transfer and credential is signed by an account key. Q-Switch tags each key with a signature-suite version, supports hybrid classical and post-quantum credentials, and lets accounts rotate keys or migrate addresses without leaving the network.

In the consensus layer, QSE validators sign votes and quorum certificates with keys that follow the same suite rules, so the validator set can adopt new algorithms without interrupting finality. The data layer records which suite produced each signature, keeping historical records verifiable after a transition.

In the network layer, validator links, regional gateways and GateMesh connections negotiate key-exchange suites by version, so encrypted transport can adopt hybrid key exchange as implementations mature.

Illustration: Signature suites are versioned. An account moves from a classical suite to a hybrid credential that combines classical and post-quantum-ready signatures, rotates its keys and migrates its address without losing its history or assets.

Suite v1 · classical

Suite v2 · hybrid

Suite v3 · post-quantum ready

  1. 01Versioned suites
  2. 02Hybrid credentials
  3. 03Key rotation
  4. 04Address migration

What Q-Switch contributes across the stack

  • 01

    One version language

    Accounts, validators and transport identify their cryptography the same way, so a transition is planned once for the whole stack.

  • 02

    Transition without disruption

    Hybrid credentials protect accounts while classical and post-quantum algorithms run side by side.

  • 03

    Downgrade resistance

    Once a key or connection moves forward, weaker suites are no longer accepted for it.

  • 04

    A governed pace

    Suites are admitted and retired through protocol governance as standards, libraries and hardware mature.

Canonical technology pageThe full agility modelThe canonical Q-Switch page details suite versioning, hybrid credentials, key rotation, address migration, failure controls and specifications.Explore Q-Switch

Orbitra L1

Other Orbitra L1 modules