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
- 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:
genesis.json
- L2 genesis file for initializing op-gethrollup.json
- Rollup configuration file for op-node- Access to your deployment
state.json
file from op-deployer
- 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
- Discover how to deploy chains with op-deployer for standardized OP Stack deployments.
- Learn how to configure and deploy the batcher to submit transaction data to L1.
- Set up the proposer to submit output roots for withdrawals.
- Explore chain operator best practices for production deployments.