Skip to main content
This guide provides step-by-step instructions for spinning up a sequencer node after deploying L1 smart contracts for your OP Stack chain with op-deployer. A sequencer node consists of two core components:
  • op-geth: Execution layer that processes transactions and maintains state
  • op-node: Consensus layer that orders transactions and creates L2 blocks
The sequencer is responsible for:
  • Ordering transactions from users
  • Building L2 blocks
  • Signing blocks on the P2P network

Prerequisites

Essential requirements

Before spinning up your sequencer, complete the following steps: 1. Successful L1 contract deployment:
  • Deployed L1 contracts using op-deployer apply command.
  • Generated genesis and rollup configuration files using:
    op-deployer inspect genesis --workdir .deployer <L2_CHAIN_ID> > .deployer/genesis.json
    op-deployer inspect rollup --workdir .deployer <L2_CHAIN_ID> > .deployer/rollup.json
    
2. Required configuration files:
  • genesis.json - L2 genesis file for initializing op-geth
  • rollup.json - Rollup configuration file for op-node
  • Access to your deployment state.json file from op-deployer
3. L1 network access:
  • L1 RPC endpoint (Ethereum, Sepolia, etc.)
  • L1 Beacon node endpoint

Software requirements

  • Git (for cloning repositories)
  • Go 1.21+ (if building from source)
  • Docker and Docker Compose (optional but recommended)
  • OpenSSL for JWT secret generation

Finding the current stable releases

To ensure you’re using the latest compatible versions of OP Stack components, always check the official releases page: release page The main components you’ll need for sequencer deployment are:
  • op-node: Look for the latest op-node/v* release
  • op-geth: Look for the latest op-geth/v* release
The versions used in this guide (op-node/v1.13.3 and op-geth/v1.101511.1) are verified compatible versions.According to the op-node v1.13.3 release notes, this op-node version specifically corresponds to op-geth v1.101511.1. Always check the release notes to ensure you’re using compatible versions.

Software installation

For spinning up a sequencer, we recommend building from source as it provides better control, and helps with debugging. In this guide Docker alternative is also provided.

    Next steps

    I