Running a local development environment
# What is this?
A development environment is a local installation of the entire OP Mainnet system. Our default development environment includes both L1 and L2 development nodes. Running the OP Mainnet environment locally is a great way to test your code and see how your contracts will behave on OP Mainnet before you graduate to a testnet deployment (and eventually a mainnet deployment).
Alternatively, you can get a hosted development node from any of these providers.
# Do I need this?
We generally recommend using the local development environment if your application falls into one of the following categories:
You're building contracts on both OP Mainnet and Ethereum that need to interact with one another. The local development environment is a great way to quickly test interactions between L1 and L2. The OP Mainnet and test networks have a communication delay between L1 and L2 that can make testing slow during the early stages of development.
You're building an application that might be subject to one of the few differences between Ethereum and OP Mainnet. Although OP Mainnet is EVM equivalent (opens new window), it's not exactly the same as Ethereum. If you're building an application that might be subject to one of these differences, you should use the local development environment to double check that everything is running as expected. You might otherwise have unexpected issues when you move to testnet. We strongly recommend reviewing these differences carefully to see if you might fall into this category.
However, not everyone will need to use the local development environment. OP Mainnet is EVM equivalent (opens new window), which means that OP Mainnet looks almost exactly like Ethereum under the hood. If you don't fall into one of the above categories, you can probably get away with simply relying on existing testing tools like Truffle or Hardhat. If you don't know whether or not you should be using the development environment, feel free to hop into the Optimism discord (opens new window). Someone nice will help you out!
# How to do it
The Optimism monorepo includes a devnode setup you can use (opens new window).
- First, make sure these components are installed. Note that the command line directions were verified under Ubuntu 20.04 LTS. Other OSes or versions may use different tools.
The command line utilities
sudo apt install -y make jq1
sudo apt update wget https://go.dev/dl/go1.20.linux-amd64.tar.gz tar xvzf go1.20.linux-amd64.tar.gz sudo cp go/bin/go /usr/bin/go sudo mv go /usr/lib echo export GOROOT=/usr/lib/go >> ~/.bashrc1
The latest version of docker uses
docker composeinstead of a separate
docker-composeexecutable. To process scripts that use
docker-compose, run these commands:
echo docker compose '$*' | sudo tee /usr/local/bin/docker-compose sudo chmod +x /usr/local/bin/docker-compose1
The Optimism monorepo.
git clone https://github.com/ethereum-optimism/optimism.git cd optimism1
# Additional information
To start, run (in the root directory of the monorepo)
The first time it runs it will be relatively slow because it needs to download the images, after that it will be faster.
To stop, run (in the root directory of the monorepo)
To clean everything, run (in the root directory of the monorepo)
The monorepo includes the L1 contract addresses (opens new window). The L2 contract addresses are, of course, the standard ones.
There are some differences between the development node and the real world (a.k.a. Ethereum mainnet and OP Mainnet):
Parameter Real-world Devnode L1 chain ID 1 900 L2 chain ID 10 901 Time between L1 blocks (in seconds) 12 3
- Private key: