Overview
op-deployer reads an intent file describing a chain’s desired configuration and makes the minimum set of smart contract calls required to make the deployment match it. It is distributed as a standalone binary with no additional dependencies, its configuration is optimized for deploying Standard OP Chains, and it exposes lower-level primitives and Go libraries for more complex setups. Itsupgrade and manage commands are deprecated;
see the
deprecation notice for the
supported upgrade paths and alternatives.
It exists because deploying an OP Stack chain means deploying a large,
interdependent set of L1 contracts at specific supported versions.
op-deployer turns that into a declarative, repeatable process, and each of
its releases maps to the contract releases it supports.
Who runs it: chain operators and developers deploying chains. It runs
on demand, from a workstation, in CI pipelines, or inside local development
environments; it is not a long-running service.
Unlike most components, op-deployer already has a full documentation set on
this site, under OP Deployer
in the Chain Operators tab; this hub routes into it.
Get started
- Deploy L1 contracts with op-deployer: install op-deployer, prepare your environment, and deploy a chain’s L1 contracts as the first step of standing up an OP Stack chain. To install the binary on its own, see Installation.
How-tos
- Custom deployments: manage deployments that depart from the standard configuration.
- Release workflows: backport fixes onto earlier op-deployer versions and add support for new contract versions.
- Upgrade L1 contracts using op-deployer:
version availability and migration paths for the deprecated
upgradecommand, which supports upgrades only up toop-contracts/v5.0.0. For later upgrades, see the deprecation notice.
Configuration & flags reference
- Command reference: init, apply, bootstrap, and verify document each command’s flags and the intent file settings.
- Artifacts locators: how op-deployer points at contract artifacts.
- Known limitations: current limitations and their workarounds.
Releases
- op-deployer release history
- OP Deployer releases reference: which op-deployer version supports which contract release.
Source & spec links
- Source:
op-deployer/in the Optimism monorepo; its README declares this documentation set as its source of truth. - Architecture reference: op-deployer’s internals, including its deployment pipeline and execution engine.
- op-deployer is deployment tooling and has no section of its own in the OP Stack specifications; the standard chain configuration it deploys is specified in OP Stack Configurability.