You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add explanation to each line in the .env.example file (#387)
* add explanation to each line in the .env.example file
remove SCR_CHAIN_TYPE
* remove unused util
* fix up e2e tests
* add omitempty option to contract_versions_tag
Copy file name to clipboardExpand all lines: README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,8 @@ You will need [`jq`](https://jqlang.github.io/jq/download/) and [`foundry`](http
42
42
43
43
To contribute a standard OP-Stack chain configuration, in addition to user-supplied metadata (chain name) the following data is required: contracts deployment, rollup config, L2 genesis. We provide a tool to scrape this information from your local [monorepo](https://github.com/ethereum-optimism/optimism) folder.
44
44
45
-
First, make a copy of `.env.example` named `.env`, and alter the variables to appropriate values.
45
+
First, make a copy of `.env.example` named `.env`, and alter the variables to appropriate values. Each value is explained in a comment in `.env.example`.
46
+
46
47
#### Frontier chains
47
48
To contribute a frontier OP-Stack chain configuration, you set the `SCR_CHAIN_TYPE=frontier` in the `.env` file. This will set `superchain_level = 1` in the registry's config file for this chain.
0 commit comments