<aside> ☝

Refs https://docs.arbitrum.io/launch-orbit-chain/orbit-sdk-introduction

</aside>

Grocery

• Data Availability Committee - stores and serves data on-demand instead storing the data on parent chain Data Availability layer
• Orbit Node - base node for all other services/roles
• Sequencer - Orders transactions and submits them to the parent chain (L2)
• Batch Poster - Packages transactions into batches and posts them to the DA layer (e.g., Avail, Ethereum, or Celestia, or self-hosted layer like Data Availability Committee)
• Validator - Monitors the chain, verifies state transitions, and participates in fraud proofs

Images

• Data Availability Server (offchainlabs/nitro-node:v3.4.0-d896e9c)
• Orbit node (offchainlabs/nitro-node:v3.4.0-d896e9c )
  • Validator
  • Sequencer
  • Batch Poster
  • Simple chain
• BlockScout
  • Needs PostgressDB https://github.com/OffchainLabs/orbit-setup-script/blob/main/docker-compose/services/db.yml
  • Backend (Indexer) https://github.com/OffchainLabs/orbit-setup-script/blob/main/docker-compose/services/backend.yml
  • Frontend (Explorer) https://github.com/OffchainLabs/orbit-setup-script/blob/main/docker-compose/services/frontend.yml
  • Needs NGINX on top Backend and Frontend service

Example of docker-compose bringing up all the services https://github.com/OffchainLabs/orbit-setup-script/blob/main/docker-compose.yaml

Scaling considerations

• Data Availability Server (main)
  • storage
  • maybe needs nginx for mirror because of REST API
• Validator - none
• Sequencer - none (investigate)
• Batch Poster - none (investigate)