Sequencer Design

Arc’s sequencer node is designed to provide Features such as exposing simple APIs for blockchain integration and instant finality.
The sequencer node is rollup agnostic but certain functionalities which are exposed at the sequencer level are only available in certain rollups. Check Rollup Stacks for more details.
Each sequencer exposes all available information about Arc’s ecosystem.
Arc’s Sequencer Node performs such operations:
  1. 1.
    Inclusion is the process by which a transaction is accepted into the rollup.
    Arc backend receives APIs requests, validates them, and computes the corresponding transactions. Additionally, this component manages all on-chain events, collecting L1 transactions, and handles transaction flows efficiently, effectively abstracting blockchain complexity from developers.
  2. 2.
    Ordering is the process of arranging transactions in a specific sequence in the rollup.
    Arc currently processes transactions using a FIFO queue, ordering when they are included.
  3. 3.
    Execution is the process by which the transactions in the blockchain are processed, and their effects are applied to the state of the rollup.
    Arc sequencer’s perform execution of transactions and update the rollups’ state at the moment APIs requests are performed, providing instant rollup finality and synchronous rollup composition.
  4. 4.
    Aggregation is the process of batching transactions into one batch. A batch of transactions consists of one or more transactions.
    Arc aggregates rollup transactions from its rollup network, providing interoperability between them.
Overall, Inclusion, Ordering and Execution are done atomically when an #API call is performed.
Each Sequencer also has:
  • an RPC client for batch submission to different Data Availability providers;
  • an RPC client for batch submission to the Prover Network;
  • an RPC client for state update submission to the Settlement & Finality layer;