ethereum-optimism · krofax · May 16, 2025 · Mar 6, 2025 · Mar 6, 2025 · Mar 6, 2025
@@ -24,12 +24,12 @@ import { Card, Cards } from 'nextra/components'
 This section provides information on OP Stack genesis creation, deployment overview, and smart contract deployment. You'll find guides and overviews to help you understand and work with these topics.
 
 <Cards>
-  <Card title="Op stack genesis creation" href="/operators/chain-operators/deploy/genesis" />
+  <Card title="Chain artifacts creation" href="/operators/chain-operators/deploy/genesis" />
 
-  <Card title="Op stack deployment overview" href="/operators/chain-operators/deploy/overview" />
+  <Card title="Deployment overview" href="/operators/chain-operators/deploy/overview" />
 
-  <Card title="Op stack smart contract deployment" href="/operators/chain-operators/deploy/smart-contracts" />
+  <Card title="Smart contract deployment" href="/operators/chain-operators/deploy/smart-contracts" />
 
-  <Card title="Learn how to validate your OP Stack deployment using op-validator" href="/operators/chain-operators/deploy/validate-deployment" />
+  <Card title="Validate your contract deployment" href="/operators/chain-operators/deploy/validate-deployment" />
 
 </Cards>
@@ -0,0 +1,7 @@
+{
+  "overview": "Deployment overview",
+  "smart-contracts": "Smart contract deployment",
+  "genesis": "Chain artifacts creation",
+  "validate-deployment": "Validate your contract deployment"
+}
+
@@ -1,7 +1,7 @@
 ---
-title: OP Stack genesis creation
+title: Chain artifacts creation
 lang: en-US
-description: Learn how to create a genesis file for the OP Stack.
+description: Learn how to retrieve genesis and rollup configuration files using op-deployer after L1 contract deployment.
 content_type: guide
 topic: genesis-creation
 personas:
@@ -20,78 +20,99 @@ is_imported_content: 'false'
 
 import { Callout } from 'nextra/components'
 
-# OP Stack genesis creation
+# Overview
 
 <Callout type="info">
-  The recommended way to generate genesis and rollup configuration files is using `op-deployer`.
-  This ensures standardization and compatibility with the Superchain.
+  This guide uses `op-deployer` to generate genesis and rollup configuration files, ensuring standardization and compatibility with the Superchain.
 </Callout>
 
-The `op-deployer` tool simplifies the creation of genesis and rollup configuration files (`genesis.json` and `rollup.json`).
-These files are crucial for initializing the execution client (`op-geth`) and consensus client (`op-node`) for your network.
+After deploying the L1 system contracts for your OP Stack chain, you need to generate two critical configuration files:
 
-The recommended flow for creating a genesis file and rollup configuration file on the OP Stack is as follows:
+*   **Genesis file** (`genesis.json`): Initializes the execution client (`op-geth`)
+*   **Rollup configuration file** (`rollup.json`): Configures the consensus client (`op-node`)
 
-1.  **Deploy the L1 contracts** using [op-deployer](/operators/chain-operators/tools/op-deployer).
-2.  **Generate** both the L2 genesis file (`genesis.json`) and the rollup configuration file (`rollup.json`) using op-deployer's `inspect` commands.
-3.  **Initialize** your off-chain components (e.g., execution client, consensus client).
+This guide shows you how to generate these files from your L1 contract deployment data using `op-deployer`.
 
-## Recommended method: using op-deployer
+## Prerequisites
 
-### Prerequisites
+Before generating genesis and rollup configuration files, ensure you have:
 
-1.  You have installed the `op-deployer` binary following the instructions in [deployer docs](/operators/chain-operators/tools/op-deployer#installation).
-    After installation, extract the `op-deployer` into your `PATH` and `cd op-deployer`.
+1.  Installed `op-deployer` following the instructions in the [op-deployer documentation](/operators/chain-operators/tools/op-deployer#installation)
 
-2.  You have created and customized an intent file in a `.deployer` directory, typically by running:
+2.  Deployed the L1 contracts successfully using the [`op-deployer apply`](/operators/chain-operators/tools/op-deployer#apply-deploy-your-chain) command
 
-    ```bash
-    ./bin/op-deployer init --l1-chain-id <YOUR_L1_CHAIN_ID> --l2-chain-ids <YOUR_L2_CHAIN_ID> --workdir .deployer
-    ```
+3.  Access to your deployment workspace directory (typically `.deployer`)
 
-    Replace `<YOUR_L1_CHAIN_ID>` and `<YOUR_L2_CHAIN_ID>` with their respective values, see a list of [`chainIds`](https://chainid.network/).
+## Generating genesis and rollup files
 
-3.  You have edited that intent file to your liking (roles, addresses, etc.).
+After your L1 contracts have been deployed, follow these steps to generate the configuration files:
 
-### Step 1: Deploy the L1 contracts
+### Step 1: Locate your deployment state file
 
-To deploy your chain to L1, run:
+The `op-deployer` tool creates a `state.json` file in your workspace directory that contains all the necessary information about your deployed contracts.
+
+Verify that this file exists in your workspace:
+
+```bash
+ls -la .deployer/state.json
+```
+
+### Step 2: Generate the L2 genesis file
+
+Use the `inspect genesis` command to retrieve your L2 genesis file:
 
 ```bash
-./bin/op-deployer apply --workdir .deployer \
-  --l1-rpc-url <RPC_URL_FOR_L1> \
-  --private-key <DEPLOYER_PRIVATE_KEY_HEX>
+op-deployer inspect genesis --workdir .deployer <L2_CHAIN_ID> > .deployer/genesis.json
 ```
 
-This command:
+Replace `<L2_CHAIN_ID>` with your L2 network's chain ID.
+
+### Step 3: Generate the rollup configuration file
+
+Use the `inspect rollup` command to retrieve your rollup configuration file:
 
-*   Reads your intent file in `.deployer/.`
-*   Deploys the OP Stack contracts to the specified L1.
-*   Updates a local `state.json` file with the results of the deployment.
+```bash
+op-deployer inspect rollup --workdir .deployer <L2_CHAIN_ID> > .deployer/rollup.json
+```
 
-### Step 2: Generate your L2 genesis file and rollup file
+### Step 4: Verify the generated files
 
-After your L1 contracts have been deployed, generate the L2 genesis and rollup configuration files by inspecting the deployer's `state.json`
+Examine the generated files to ensure they contain the expected configuration:
 
 ```bash
-./bin/op-deployer inspect genesis --workdir .deployer <L2_CHAIN_ID> > .deployer/genesis.json
-./bin/op-deployer inspect rollup --workdir .deployer <L2_CHAIN_ID> > .deployer/rollup.json
+# View the genesis file structure
+jq . .deployer/genesis.json | head -20
+
+# View the rollup configuration
+jq . .deployer/rollup.json
 ```
 
-*   genesis.json is the file you will provide to your execution client (e.g. op-geth).
-*   rollup.json is the file you will provide to your consensus client (e.g. op-node).
+The `genesis.json` file contains the initial state of your L2 blockchain, including:
+
+*   Chain configuration parameters
+*   Initial account states
+*   Genesis block properties
 
-### Step 3: Initialize your off-chain components
+The `rollup.json` file contains the rollup protocol parameters, including:
 
-Once you have `genesis.json` and `rollup.json`:
+*   L1 contract addresses
+*   Sequencing settings
+*   Finality parameters
 
-1.  Initialize op-geth using genesis.json.
-2.  Configure op-node with rollup.json.
-3.  Set up additional off-chain infrastructure as needed (block explorer, indexers, etc.). For more on architecture, see [Architecture overview](/operators/chain-operators/architecture).
+## Troubleshooting
+
+If you encounter issues with the generated files:
+
+*   [Verify](/operators/chain-operators/tools/op-deployer#verify-verify-contract-source-code-on-block-explorers) that your L1 contract deployment was successful
+*   Check that you're using the correct **L2 chain ID** in the generation commands
+*   Ensure your `state.json` file is up-to-date with your latest deployment
+
+<Callout type="warning">
+  Never manually edit the generated genesis or rollup files unless you fully understand the implications. Incorrect configurations can lead to consensus failures or chain security issues.
+</Callout>
 
-## Next steps
+## Next Steps
 
-*   Learn how to [initialize](/operators/node-operators/configuration/base-config#initialization-via-genesis-file)
-    `op-geth` with your `genesis.json` file.
-*   Learn how to [initialize](/operators/node-operators/configuration/base-config#configuring-op-node) `op-node` with your `rollup.json` file.
-*   Learn more about the off chain [architecture](/operators/chain-operators/architecture).
+*   Learn how to [initialize](/operators/node-operators/configuration/base-config#initialization-via-genesis-file) `op-geth` with your `genesis.json` file
+*   Learn how to [configure](/operators/node-operators/configuration/base-config#configuring-op-node) `op-node` with your `rollup.json` file
+*   Learn more about the off-chain [architecture](/operators/chain-operators/architecture)
@@ -1,5 +1,5 @@
 ---
-title: OP Stack deployment overview
+title: Deployment overview
 lang: en-US
 description: Learn about the different components of deploying a standard OP Stack chain.
 content_type: guide
@@ -20,7 +20,7 @@ is_imported_content: 'false'
 
 import { Callout } from 'nextra/components'
 
-# OP Stack deployment overview
+# Deployment overview
 
 When deploying a **standard OP Stack chain**, you'll be setting up several key
 components. It's useful to understand what each of these components does before

@@ -1,5 +1,5 @@
 ---
-title: OP Stack Smart Contract Deployment
+title: Smart contract deployment
 lang: en-US
 description: Learn how to deploy the OP Stack L1 smart contracts.
 content_type: guide
@@ -20,12 +20,10 @@ is_imported_content: 'false'
 
 import { Callout, Steps } from 'nextra/components'
 
-# OP Stack smart contract deployment
+# Overview
 
 This guide outlines the process for deploying the OP Stack L1 smart contracts using `op-deployer`.
 
-## Overview
-
 Deploying OP Stack L1 contracts is a critical step in setting up your rollup.
 
 <Callout type="warning">

@@ -1,5 +1,5 @@
 ---
-title: Validating your OP Stack deployment
+title: Validate your contract deployment
 lang: en-US
 description: Learn how to validate your OP Stack deployment using op-validator
 content_type: guide