Skip to content

Commit 363849f

Browse files
committed
updated contents
1 parent ca7f3f3 commit 363849f

File tree

2 files changed

+5
-11
lines changed

2 files changed

+5
-11
lines changed
Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
{
22
"overview": "Deployment overview",
33
"smart-contracts": "Smart contract deployment",
4-
"genesis": "Chain artifacts creation",
5-
"validate-deployment": "Validate your contract deployment"
4+
"validate-deployment": "Validate your contract deployment",
5+
"genesis": "Chain artifacts creation"
66
}
77

pages/operators/chain-operators/deploy/genesis.mdx

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -22,10 +22,6 @@ import { Callout } from 'nextra/components'
2222

2323
# Overview
2424

25-
<Callout type="info">
26-
This guide uses `op-deployer` to generate genesis and rollup configuration files, ensuring standardization and compatibility with the Superchain.
27-
</Callout>
28-
2925
After deploying the L1 system contracts for your OP Stack chain, you need to generate two files to run nodes on the L2 network:
3026

3127
* **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
3733

3834
Before generating genesis and rollup configuration files, ensure you have:
3935

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
4337

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)
4539

4640
## Generating genesis and rollup files
4741

@@ -97,7 +91,7 @@ The `rollup.json` file contains the rollup protocol parameters, including:
9791

9892
* L1 contract addresses
9993
* Sequencing settings
100-
* Hardfork activations
94+
* Protocol upgrade activation times
10195

10296
## Troubleshooting
10397

0 commit comments

Comments
 (0)