From 153b1b05f5a6310293c3d8bb61ce6110ea4826e7 Mon Sep 17 00:00:00 2001 From: alan <652732310@qq.com> Date: Sat, 16 Nov 2024 12:36:23 +0800 Subject: [PATCH] fix op-deployer commands --- pages/builders/chain-operators/tools/op-deployer.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/pages/builders/chain-operators/tools/op-deployer.mdx b/pages/builders/chain-operators/tools/op-deployer.mdx index 6f5aba921..cd522696f 100644 --- a/pages/builders/chain-operators/tools/op-deployer.mdx +++ b/pages/builders/chain-operators/tools/op-deployer.mdx @@ -138,16 +138,16 @@ Inspect the `state.json` file by navigating to your working directory. With the ``` cd .deployer -op-deployer --workdir .deployer inspect genesis > genesis.json -op-deployer --workdir .deployer inspect rollup > rollup.json +op-deployer inspect genesis --workdir .deployer > genesis.json +op-deployer inspect rollup --workdir .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: ``` -op-deployer --workdir .deployer inspect l1 # outputs all L1 contract addresses for an L2 chain -op-deployer --workdir .deployer inspect deploy-config # outputs the deploy config for an L2 chain -op-deployer --workdir .deployer inspect l2-semvers # outputs the semvers for all L2 chains +op-deployer inspect l1 --workdir .deployer # outputs all L1 contract addresses for an L2 chain +op-deployer inspect deploy-config --workdir .deployer # outputs the deploy config for an L2 chain +op-deployer inspect l2-semvers --workdir .deployer # outputs the semvers for all L2 chains ```