@@ -10,8 +10,6 @@ If neither `EVM` nor `OVM` are listed, the contract is likely intended to be use
...
@@ -10,8 +10,6 @@ If neither `EVM` nor `OVM` are listed, the contract is likely intended to be use
## Usage (npm)
## Usage (npm)
You can import `@eth-optimism/contracts` to use the Optimism contracts within your own codebase.
You can import `@eth-optimism/contracts` to use the Optimism contracts within your own codebase.
We currently only export `@eth-optimism/contracts` via `npm`.
Install via `npm` or `yarn`:
Install via `npm` or `yarn`:
```shell
```shell
...
@@ -92,98 +90,87 @@ yarn build:contracts
...
@@ -92,98 +90,87 @@ yarn build:contracts
```
```
### Deploying the Contracts
### Deploying the Contracts
To deploy the contracts first clone, install, and build the contracts package.
Next set the following env vars:
#### Required environment variables
You must set the following environment variables to execute a deployment:
```bash
```bash
CONTRACTS_TARGET_NETWORK=...
# Name for the network to deploy to ("mainnet", "kovan", etc.)
CONTRACTS_DEPLOYER_KEY=...
export CONTRACTS_TARGET_NETWORK=...
CONTRACTS_RPC_URL=...
```
Then to perform the actual deployment run:
# Private key that will send deployment transactions
export CONTRACTS_DEPLOYER_KEY=...
```bash
# RPC URL connected to the L1 chain we're deploying to
npx hardhat deploy \
export CONTRACTS_RPC_URL=...
--network ... \ # `network` MUST equal your env var `CONTRACTS_TARGET_NETWORK`
--ovm-address-manager-owner ... \
# Your Etherscan API key for the L1 network
--ovm-proposer-address ... \
export ETHERSCAN_API_KEY=...
--ovm-relayer-address ... \
--ovm-sequencer-address ... \
--scc-fraud-proof-window ... \
--scc-sequencer-publish-window ...
```
```
This will deploy the contracts to the network specified in your env and create
#### Creating a deployment script
an artifacts directory in `./deployments`.
To view all deployment options run:
Before you can carry out a deployment, you must create a deployment script.
See [mainnet.sh](./scripts/deploy-scripts/mainnet.sh) for an example deployment script.
We recommend duplicating an existing deployment script and modifying it to satisfy your requirements.
```bash
Most variables within the deploy script are relatively self-explanatory.
npx hardhat deploy --help
If you intend to upgrade an existing system you **MUST**[include the following argument](https://github.com/ethereum-optimism/optimism/blob/6f633f915b34a46ac14430724bed9722af8bd05e/packages/contracts/scripts/deploy-scripts/mainnet.sh#L33) in the deploy script:
If you are deploying a system from scratch, you should **NOT** include `--tags upgrade` or you will fail to deploy several contracts.
To whitelist deployers on Mainnet you must have the whitelist Owner wallet connected, then run:
#### Executing a deployment
```bash
npx hardhat whitelist \
--use-ledgertrue\
--contracts-rpc-url https://mainnet.optimism.io \
--address ... \ # address to whitelist
```
To withdraw ETH fees to L1 on Mainnet, run:
Once you've created your deploy script, simply run the script to trigger a deployment.
```bash
During the deployment process, you will be asked to transfer ownership of several contracts to a special contract address.
npx hardhat withdraw-fees \
You will also be asked to verify various configuration values.
--use-ledger\ # The ledger to withdraw fees with. Ensure this wallet has ETH on L2 to pay the tx fee.
This is a safety mechanism to make sure that actions within an upgrade are performed atomically.
--contracts-rpc-url https://mainnet.optimism.io \
Ownership of these addresses will be automatically returned to the original owner address once the upgrade is complete.
The original owner can always recover ownership from the upgrade contract in an emergency.
Please read these instructions carefully, verify each of the presented configuration values, and carefully confirm that the contract you are giving ownership to has not been compromised (e.g., check the code on Etherscan).
After your deployment is complete, your new contracts will be written to an artifacts directory in `./deployments/<name>`.
Your contracts will also be automatically verified as part of the deployment script.
#### Creating a genesis file
Optimism expects that certain contracts (called "predeploys") be deployed to the L2 network at pre-determined addresses.
Doing this requires that you generate a special genesis file to be used by your corresponding L2Geth nodes.
You must first create a genesis generation script.
Like in the deploy script, we recommend starting from an [existing script](./scripts/deploy-scripts/mainnet-genesis.sh).
Modify each of the values within this script to match the values of your own deployment, taking any L1 contract addresses from the `./deployments/<name>` folder that was just generated or modified.
Execute this script to generate the genesis file.
You will find this genesis file at `./dist/dumps/state-dump.latest.json`.
You can then ingest this file via `geth init`.
### Hardhat tasks
#### Whitelisting
Optimism has removed the whitelist from the Optimism mainnet.
However, if you are running your own network and still wish to use the whitelist, you can manage the whitelist with the `whitelist` task.
Run the following to get help text for the `whitelist` command:
```
npx hardhat whitelist --help
```
```
#### Withdrawing fees
Any wallet can trigger a withdrawal of fees within the `SequencerFeeWallet` contract on L2 back to L1 as long as a threshold balance has been reached.
Fees within the wallet will return to a fixed address on L1.
Run the following to get help text for the `withdraw-fees` command:
```
npx hardhat withdraw-fees --help
```
## Security
## Security
Please refer to our [Security Policy](https://github.com/ethereum-optimism/.github/security/policy) for information about how to disclose security issues with this code.
Please refer to our [Security Policy](https://github.com/ethereum-optimism/.github/security/policy) for information about how to disclose security issues with this code.
We also maintain a [bug bounty program via Immunefi](https://immunefi.com/bounty/optimism/) with a maximum payout of $2,000,042 for critical bug reports.
