Skip to main content
Once you have initialized your intent and state files, you can use the apply command to perform the deployment.

Usage

You can call the apply command like this:
You will need to specify additional arguments depending on what you’re trying to do. See below for a reference of each supported CLI arg.

CLI Arguments

--deployment-target

Default: live --deployment-target specifies where each chain should be deployed to. It can be one of the following values:
  • live: Deploys to a live L1. Concretely, this means that OP Deployer will send transactions identified by vm.broadcast calls to L1. --l1-rpc-url and --private-key must be specified when using this target.
  • genesis: Deploys to an L1 genesis file. This is useful for testing or local development purposes. The generated genesis contains no SP1 verifier, so pass --deploy-mock-sp1-verifier.

--deploy-mock-sp1-verifier

Deploys a mock SP1 verifier for the ZK dispute game to use. A genesis contains no SP1 verifier, and neither does a live L1 without a release verifier, such as a local devnet. The mock accepts every proof, so use it for development only. On an L1 chain ID with a release verifier, such as Sepolia, op-deployer refuses the flag, also for a genesis.

--l1-rpc-url

Defines the RPC URL of the L1 chain to deploy to.

--private-key

Defines the private key to use for signing transactions. This is only required for deployment targets that involve sending live transactions. Note that ownership over each L2 is transferred to the proxy admin owner specified in the intent after the deployment completes, so it’s OK to use a hot key for this purpose.