Orbis
  • Orbis
  • High-Level Overview
  • Technology
    • zk-SNARKs
    • Halo 2
    • Cardano
      • EUTXO
  • Architecture
    • Process
    • L1 Rollup Protocol: On-Chain Inputs and Outputs
    • L2 Rollup Protocol: On-Rollup Transactions
    • Orbis Specification Language (OSL)
  • Smart Contracts
    • Programming on Orbis
    • Plutus Language Family
  • Design Considerations
    • Reliability
    • Liveness and Safety
    • Decentralization
      • Single node
      • Static master/workers
      • Dynamic master/workers
    • Data Availability
    • Upgradability and Governance
    • Performance
  • Inter-Rollup and Inter-Protocol Bridges
  • HALO Token
    • HALO
    • Tokenomics
  • Official Links
    • Website
    • Twitter
    • Blog
    • Discord
    • Github
    • LinkedIn
Powered by GitBook
On this page
Export as PDF
  1. Design Considerations
  2. Decentralization

Single node

In this setup, the system runs on a single machine controlled by Orbis Labs.

This system is fully centralized. Because Orbis Labs will control this single node, it becomes a single point of failure. It is neither crash-only nor resistant to Byzantine failure.

This system should be considered a milestone that enables testing of all user-facing features like sending funds, submitting transactions, inspecting the rollup, retrieving funds, and syncing the rollup with layer 1.

PreviousDecentralizationNextStatic master/workers

Last updated 2 years ago