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
Copy file name to clipboardExpand all lines: pages/operators/chain-operators/deploy/genesis.mdx
+3-9Lines changed: 3 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,10 +22,6 @@ import { Callout } from 'nextra/components'
22
22
23
23
# Overview
24
24
25
-
<Callouttype="info">
26
-
This guide uses `op-deployer` to generate genesis and rollup configuration files, ensuring standardization and compatibility with the Superchain.
27
-
</Callout>
28
-
29
25
After deploying the L1 system contracts for your OP Stack chain, you need to generate two files to run nodes on the L2 network:
30
26
31
27
***Genesis file** (`genesis.json`): Initializes the execution client (`op-geth`)
@@ -37,11 +33,9 @@ This guide shows you how to generate these files from your L1 contract deploymen
37
33
38
34
Before generating genesis and rollup configuration files, ensure you have:
39
35
40
-
1. Installed `op-deployer` following the instructions in the [op-deployer documentation](/operators/chain-operators/tools/op-deployer#installation)
41
-
42
-
2. Deployed the L1 contracts successfully using the [`op-deployer apply`](/operators/chain-operators/tools/op-deployer#apply-deploy-your-chain) command
36
+
1. Deployed the L1 contracts successfully using the [`op-deployer apply`](/operators/chain-operators/tools/op-deployer#apply-deploy-your-chain) command
43
37
44
-
3. Access to your deployment workspace directory (typically `.deployer`)
38
+
2. Access to your deployment workspace directory (`.deployer` if you've followed the instructions in the last guide)
45
39
46
40
## Generating genesis and rollup files
47
41
@@ -97,7 +91,7 @@ The `rollup.json` file contains the rollup protocol parameters, including:
0 commit comments