From 235cc14a4e46b7d0bcd75bf4aea84a836d80a5f8 Mon Sep 17 00:00:00 2001 From: Tess Rinearson Date: Sun, 1 Dec 2024 14:54:16 +0100 Subject: [PATCH] op-deployer: fix inspect commands --- pages/builders/chain-operators/tools/op-deployer.mdx | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/pages/builders/chain-operators/tools/op-deployer.mdx b/pages/builders/chain-operators/tools/op-deployer.mdx index 4739e2fe..0a814a46 100644 --- a/pages/builders/chain-operators/tools/op-deployer.mdx +++ b/pages/builders/chain-operators/tools/op-deployer.mdx @@ -111,12 +111,11 @@ address as other chains on the Superchain. To add your chain to the [Superchain Registry](https://github.com/ethereum-optimism/superchain-registry) you will need to provide the chain artifacts. To get these chain artifacts, you will need to write the output of these commands to new files. -Inspect the `state.json` file by navigating to your working directory. With the contracts deployed, generate the genesis and rollup configuration files by running the following commands:" +Inspect the `state.json` file by navigating to your working directory. With the contracts deployed, generate the genesis and rollup configuration files by running the following commands: ``` -cd .deployer -op-deployer inspect genesis --workdir .deployer > genesis.json -op-deployer inspect rollup --workdir .deployer > rollup.json +op-deployer inspect genesis --workdir .deployer > .deployer/genesis.json +op-deployer inspect rollup --workdir .deployer > .deployer/rollup.json ``` Now that you have your `genesis.json` and `rollup.json` you can spin up a node on your network. You can also use the following inspect subcommands to get additional data: