Overview

op-deployer/v0.4.5 supports deploying, upgrading to, and producing calldata for op-contracts/v4.1.0 (u16a). This release supports all of the following:

op-deployer bootstrap [options] // deploy superchain|implementations contracts at op-contracts/v4.1.0
op-deployer apply [options] // deploy new OPChain contracts at op-contracts/4.1.0
op-deployer upgrade v2.0.0 // upgrade from op-contracts/v1.8.0 -> op-contracts/v2.0.0
op-deployer upgrade v3.0.0 // upgrade from op-contracts/v2.0.0 -> op-contracts/v3.0.0
op-deployer upgrade v4.0.0 // upgrade from op-contracts/v3.0.0 -> op-contracts/v4.0.0 (not recommended, should upgrade straight to op-contracts/v4.1.0 instead)
op-deployer upgrade v4.1.0 // upgrade from op-contracts/v3.0.0|v4.0.0 -> op-contracts/v4.1.0

All other commands are only guaranteed to work with op-contracts/v4.1.0. So you must upgrade to op-contracts/v4.1.0 before doing the following:

op-deployer manage [options]
op-deployer verify [options]

Details

Additional changes outside of op-contracts/v4.1.0 support include:

• ability to specify a custom block GasLimit when deploying a new OPChain via the chainIntent.GasLimit field
• fusaka defense via reduction of default tx.GasPadFactor from 2.0 -> 1.2 (to allow opcm.deploy to work)
• modified contracts locator in intent.toml (deprecated tag:// locator in favor of embedded)
  1. embedded (default) - embeds artifacts.tgz file containing contracts artifacts from same branch as op-deployer, ensuring compatibility
  2. https:// - download artifacts.tgz from remote server
  3. file:// - point to local filepath of contract artifacts

Diff compared to op-deployer/v0.4.4

• fixes bug in op-deployer upgrade related to contracts locator
• adds full cli based integration test suite