Skip to content

Commit 9661fc1

Browse files
committed
fix broken links
1 parent ec0c4d0 commit 9661fc1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

pages/builders/chain-operators/tools/op-challenger.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -94,9 +94,9 @@ This guide provides a walkthrough of setting up the configuration and monitoring
9494
#### `--network`
9595

9696
* This identifies the L2 network `op-challenger` is running for, e.g., `op-sepolia` or `op-mainnet`.
97-
* When using the `--network` flag, the `--game-factory-address` will be automatically pulled from the [`superchain-registry`](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/chainList.json).
97+
* When using the `--network` flag, the `--game-factory-address` will be automatically pulled from the [`superchain-registry`](https://github.com/ethereum-optimism/superchain-registry/blob/main/chainList.json).
9898
* When cannon is executed, challenger needs the roll-up config and the L2 Genesis, which is op-geth's Genesis file. Both files are automatically loaded when Cannon Network is used, but custom networks will need to specify both Cannon L2 Genesis and Cannon rollup config.
99-
* For custom networks not in the [`superchain-registry`](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/chainList.json), the `--game-factory-address` and rollup must be specified, as follows:
99+
* For custom networks not in the [`superchain-registry`](https://github.com/ethereum-optimism/superchain-registry/blob/main/chainList.json), the `--game-factory-address` and rollup must be specified, as follows:
100100

101101
```
102102
--cannon-rollup-config rollup.json \

0 commit comments

Comments
 (0)