Skip to main content
OP Deployer can be installed both from pre-built binaries and from source. This guide will walk you through both methods.

Install From Binaries

Installing OP Deployer from pre-built binaries is the easiest and most preferred way to get started. To install from binaries, download the latest release from the releases page and extract the binary to a directory in your $PATH.

Install From Source

To install from source, you will need Go, just, and git. Then, run the following:

Runtime Dependencies

OP Deployer runs its Solidity deploy scripts with forge, and op-deployer prepare and op-deployer continue also run anvil. Live apply and bootstrap run each script as a forge dry run, without the deployer key, then sign and send the transactions that forge records with txmgr, which rebroadcasts and bumps the fee of a stuck transaction. Use an up-to-date L1 RPC endpoint: each dry run forks the L1 at its current head and fails if the endpoint cannot serve that block. OP Deployer pins one Foundry version, in version.json.
  • If forge and anvil of that version are on your PATH, OP Deployer uses them.
  • If they are not, OP Deployer downloads that Foundry release to its cache directory (--cache-dir, default ~/.op-deployer/cache) on first use, and verifies the checksum of the download. It downloads only for Linux and macOS.
  • Without network access, install the pinned Foundry version and put forge and anvil on your PATH.
The OP Deployer Docker images include forge and anvil. Go programs that use the OP Deployer packages, such as devstack tests, have the same runtime dependencies.