From 1122f216200387f98f011655676a3927b49512a1 Mon Sep 17 00:00:00 2001 From: asymmetric <101816+asymmetric@users.noreply.github.com> Date: Wed, 12 Feb 2025 14:37:16 +0100 Subject: [PATCH] genesis: fix formatting --- pages/operators/chain-operators/deploy/genesis.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/operators/chain-operators/deploy/genesis.mdx b/pages/operators/chain-operators/deploy/genesis.mdx index a980149e8..50f733b73 100644 --- a/pages/operators/chain-operators/deploy/genesis.mdx +++ b/pages/operators/chain-operators/deploy/genesis.mdx @@ -80,7 +80,7 @@ Once you have `genesis.json` and `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: -````bash +```bash ./bin/op-deployer inspect l1 --workdir .deployer # outputs all L1 contract addresses for an L2 chain ./bin/op-deployer inspect deploy-config --workdir .deployer # outputs the deploy config for an L2 chain ``` @@ -98,7 +98,7 @@ provided to the consensus client (op-node). -## Solidity script (Legacy) +### Solidity script (Legacy) You can also use the foundry script located in the monorepo to generate an "L2 state dump" and then pass this into the op-node genesis subcommand.