Operations
Running the OP Stack devnet
The single-sequencer L3 in infra/op-stack: L1 as an anvil fork of Base Sepolia, the four OP services, config generation via op-deployer, and the make targets (with a PowerShell path on Windows).
infra/op-stack is a Docker Compose stack that runs a complete OP Stack rollup with one sequencer. It's how you get real L3 blocks; the privacy core itself runs fine without it.
The services
| Service | Role |
|---|---|
| L1 (anvil) | An anvil fork of Base Sepolia, standing in as the settlement layer. |
op-geth | The L3 execution engine. |
op-node | The rollup node / consensus client. |
op-batcher | Posts L3 transaction batches to L1. |
op-proposer | Posts output roots (DisputeGameFactory-based). |
Generate config & boot
cd infra/op-stack
cp .env.example .env
make generate # genesis + rollup config via op-deployer
docker compose up -dmake generate runs the generation scripts (scripts/generate.sh, or generate.ps1 on Windows) to produce the genesis and rollup config with op-deployer. The lifecycle targets:
make generate- Produce genesis + rollup config.
make up- Start the stack.
make down- Stop the stack.
make reset- Tear down and clear state.
Windows
A PowerShell generation script (scripts/generate.ps1) mirrors the shell path, so the devnet generates on Windows without a POSIX shell.