Orchestrator
Overview
The orchestrator in a Madara Appchain is responsible for coordinating communication between the sequencer, prover and settlement layer. It can be considered as an extension to the sequencer: it offloads a lot of the communication complexities, making the sequencer lighter.
The orchestrator is a unique component in Madara Appchains.
Responsibilities
The orchestrator has four main responsibilities:
- SNOS communication. Asks SNOS to process ready blocks and retrieve results.
- Proof coordination. Sends the required data to the prover and monitors for ready proofs.
- DA communication. Submits data for Data Availability Layer (currently Ethereum or Starknet).
- SL communication. Submits data for Settlement Layer: proofs and state updates.
All of the responsibilities are handled through a individual queues: jobs enter the appropriate queue and are processed in the order they arrived. Possible retries are also managed through the queues.
Data flow
The data flow of the orchestrator is illustrated below.
- The orchestrator polls the sequencer for new, unprocessed blocks
- Once an unprocessed block is available, the orchestrator asks the SNOS to process the block number
- The SNOS processes the block, generates a validity proof and sends it to the orchestrator
- The orchestrator forwards the validity proof (and other metadata) for the prover to process
- The prover sends ready proofs to the Settlement Layer. The orchestrator polls the Settlement Layer for new, verified proofs.
- Once the orchestrator detects a new, verified proof in the Settlement Layer, the orchestator updates its state and sends the new state to the Settlement Layer's core contracts for updating their network state.