🎉 We are deprecating the Optimism SDK and migrating all tutorials to use viem/op-stack. Read more →
Operators
Chains
Deployment
Contract deployment

OP Stack smart contract deployment

This guide outlines the process for deploying the OP Stack L1 smart contracts using op-deployer.

Overview

Deploying OP Stack L1 contracts is a critical step in setting up your rollup.

⚠️

Always deploy from official contract releases. You can find official release versions in the smart contract overview. Contract changes are generally not considered backwards compatible.

Deployment workflow

Install op-deployer

First, install the op-deployer tool following the installation instructions.

Create an intent file

Generate an intent file that defines your chain configuration:

op-deployer init \
  --l1-chain-id <chain ID of your L1> \
  --l2-chain-ids <comma-separated list of chain IDs for your L2s> \
  --workdir .deployer \
  --intent-type <standard|custom|standard-overrides>

Customize the generated intent file according to your requirements. See the op-deployer configuration guide for details.

Deploy the contracts

Execute the deployment:

op-deployer apply --workdir .deployer --l1-rpc-url <rpc-url> --private-key <private key hex>

Verify contract source code (Optional)

Verify your deployed contracts on block explorers:

op-deployer verify \
  --l1-rpc-url <l1 rpc url> \
  --etherscan-api-key <your free etherscan api key>

Generate chain configuration files

Generate the necessary configuration files for your L2 node:

op-deployer inspect genesis --workdir .deployer <l2-chain-id> > .deployer/genesis.json
op-deployer inspect rollup --workdir .deployer <l2-chain-id> > .deployer/rollup.json

Contract versioning

The OP Stack follows semantic versioning (X.Y.Z) for contract releases:

  • Major (X): Breaking changes that require coordination, such as Ecotone or the Fault Proof System
  • Minor (Y): New features or improvements that maintain backwards compatibility
  • Patch (Z): Bug fixes and minor improvements

Contract releases are tagged in the repository as op-contracts/vX.Y.Z.

For standard chains intended to join the Superchain, always use the latest Optimism Governance approved release. You can find these in the Superchain Registry (opens in a new tab).

Version compatibility

When selecting a contract version, consider:

  • L2 Client compatibility: Ensure your chosen contract version is compatible with the op-geth and op-node versions you plan to use
  • Feature requirements: Different versions support different features (e.g., only v2.0.0+ supports permissionless fault proofs)
  • Security updates: Always prefer the latest patch version within your chosen major.minor version

Next Steps