diff --git a/pages/operators/chain-operators/architecture.mdx b/pages/operators/chain-operators/architecture.mdx
index 2a9d9a34d..22d7a9774 100644
--- a/pages/operators/chain-operators/architecture.mdx
+++ b/pages/operators/chain-operators/architecture.mdx
@@ -178,7 +178,7 @@ The [op-conductor](/operators/chain-operators/tools/op-conductor) RPC can act as
### op-challenger
-The [op-challenger](/operators/chain-operators/tools/op-challenger) verifies the correctness of the L2 state by challenging invalid state transitions. This ensures the network's security and validity.
+The [op-challenger](/operators/chain-operators/deploy/op-challenger) verifies the correctness of the L2 state by challenging invalid state transitions. This ensures the network's security and validity.
### Ethereum L1 nodes
diff --git a/pages/operators/chain-operators/deploy.mdx b/pages/operators/chain-operators/deploy.mdx
index ee408564e..72da80410 100644
--- a/pages/operators/chain-operators/deploy.mdx
+++ b/pages/operators/chain-operators/deploy.mdx
@@ -38,5 +38,7 @@ This section provides information on OP Stack genesis creation, deployment overv
+
+
diff --git a/pages/operators/chain-operators/deploy/_meta.json b/pages/operators/chain-operators/deploy/_meta.json
index da35b2252..61f001ab4 100644
--- a/pages/operators/chain-operators/deploy/_meta.json
+++ b/pages/operators/chain-operators/deploy/_meta.json
@@ -5,6 +5,7 @@
"validate-deployment": "Validate your contract deployment",
"sequencer-node": "Spinning up the sequencer",
"proposer-setup-guide": "Spinning up the proposer",
- "spin-batcher": "Spinning up the batcher"
+ "spin-batcher": "Spinning up the batcher",
+ "op-challenger": "Spinning up the op-challenger"
}
diff --git a/pages/operators/chain-operators/deploy/op-challenger.mdx b/pages/operators/chain-operators/deploy/op-challenger.mdx
new file mode 100644
index 000000000..7e72b1b4e
--- /dev/null
+++ b/pages/operators/chain-operators/deploy/op-challenger.mdx
@@ -0,0 +1,637 @@
+---
+title: How to configure challenger for your chain
+description: Learn how to configure challenger for your OP Stack chain.
+lang: en-US
+content_type: tutorial
+topic: configure-challenger-for-your-chain
+personas:
+ - chain-operator
+categories:
+ - mainnet
+ - testnet
+ - fault-proofs
+ - op-challenger
+ - chain-configuration
+is_imported_content: 'false'
+---
+
+import { Callout, Steps, Tabs, Tab } from 'nextra/components'
+
+# How to configure challenger for your chain
+
+This guide provides step-by-step instructions for setting up the configuration and monitoring options for `op-challenger`. The challenger is a critical fault proofs component that monitors dispute games and challenges invalid claims to protect your OP Stack chain.
+
+See the [OP-Challenger Explainer](/stack/fault-proofs/challenger) for a general overview of this fault proofs feature.
+
+The challenger is responsible for:
+
+* Monitoring dispute games created by the fault proof system
+* Challenging invalid claims in dispute games
+* Defending valid state transitions
+* Resolving games when possible
+
+## Prerequisites
+
+### Essential requirements
+
+Before configuring your challenger, complete the following steps:
+
+
+
+### Deploy OP Stack chain with fault proofs enabled
+* L1 contracts deployed with dispute game factory
+* Fault proof system active on your chain
+* Access to your chain's contract addresses
+* [Generate an absolute prestate](/operators/chain-operators/tutorials/absolute-prestate#generating-the-absolute-prestate) for your network version - This is critical as the challenger will refuse to interact with games if it doesn't have the matching prestate
+
+### Set up required infrastructure access
+* L1 RPC endpoint (Ethereum, Sepolia, etc.)
+* L1 Beacon node endpoint (for blob access)
+* L2 archive node with debug API enabled
+* Rollup node (op-node) with historical data
+
+### Prepare configuration files
+* `rollup.json` - Rollup configuration file
+* `genesis-l2.json` - L2 genesis file
+* `prestate.json` - The absolute prestate file generated in step 1
+
+
+
+### Software requirements
+
+* Git (for cloning repositories)
+* Go 1.21+ (if building from source)
+* Docker and Docker Compose (optional but recommended)
+* Access to a funded Ethereum account for challenger operations
+
+### Finding the current stable releases
+
+To ensure you're using the latest compatible versions of OP Stack components, always check the official releases page:
+
+[OP Stack releases page](https://github.com/ethereum-optimism/optimism/releases)
+
+Look for the latest `op-challenger/v*` release. The challenger version used in this guide (op-challenger/v1.5.0) is a verified stable version.
+
+Always check the release notes to ensure you're using compatible versions with your chain's deployment.
+
+## Software installation
+
+For challenger deployment, you can either build from source (recommended for better control and debugging) or use Docker for a containerized setup.
+
+
+
+### Build and Configure
+
+Building from source gives you full control over the binaries and is the preferred approach for production deployments.
+
+**Clone and build op-challenger**
+
+```bash
+# Clone the optimism monorepo
+git clone https://github.com/ethereum-optimism/optimism.git
+cd optimism
+
+# Check out the latest release of op-challenger
+git checkout op-challenger/v1.5.0
+
+# Install dependencies and build
+just op-challenger
+
+# Binary will be available at ./op-challenger/bin/op-challenger
+```
+
+### Verify installation
+
+Check that you have properly installed the challenger component:
+
+```bash
+# Make sure you're in the optimism directory
+./op-challenger/bin/op-challenger --help
+
+# You should see the challenger help output with available commands and flags
+```
+
+## Configuration setup
+
+
+
+### Organize your workspace
+
+After building the binaries, create your challenger working directory:
+
+```bash
+# Create challenger directory (this should be at the same level as optimism directory)
+mkdir challenger-node
+cd challenger-node
+
+# Create necessary subdirectories
+mkdir scripts
+mkdir challenger-data
+
+# Verify the optimism directory is accessible
+# Directory structure should look like:
+# /optimism/ (contains the built binaries)
+# /challenger-node/ (your working directory)
+```
+
+### Copy configuration files
+
+```bash
+# Copy configuration files to your challenger directory
+# Adjust paths based on your deployment setup
+cp /path/to/your/rollup.json .
+cp /path/to/your/genesis-l2.json .
+```
+
+### Set up environment variables
+
+You'll need to gather several pieces of information before creating your configuration. Here's where to get each value:
+
+**L1 network access:**
+
+* L1 RPC URL: Your L1 node endpoint (Infura, Alchemy, or self-hosted)
+* L1 Beacon URL: Beacon chain API endpoint for blob access
+
+**L2 network access:**
+
+* L2 RPC URL: Your op-geth archive node endpoint
+* Rollup RPC URL: Your op-node endpoint with historical data
+
+**Challenger wallet:**
+
+* Private key for challenger operations (must be funded)
+
+**Network configuration:**
+
+* Game factory address from your contract deployment
+* Network identifier (e.g., op-sepolia, op-mainnet, or custom)
+
+Copy and paste in your terminal, to create your env file.
+
+```bash
+# Create .env file with your actual values
+cat > .env << 'EOF'
+# L1 Configuration - Replace with your actual RPC URLs
+L1_RPC_URL=https://sepolia.infura.io/v3/YOUR_ACTUAL_INFURA_KEY
+
+# L2 Configuration - Replace with your actual node endpoints
+L2_RPC_URL=http://localhost:8545
+ROLLUP_RPC_URL=http://localhost:8547
+L1_BEACON=http://sepolia-cl-1:5051
+
+# Wallet configuration - Choose either mnemonic + HD path OR private key
+MNEMONIC="test test test test test test test test test test test junk"
+HD_PATH="m/44'/60'/0'/0/0"
+# PRIVATE_KEY=0xYOUR_ACTUAL_PRIVATE_KEY # Alternative to mnemonic
+
+# Network configuration
+NETWORK=op-sepolia
+GAME_FACTORY_ADDRESS=0xYOUR_GAME_FACTORY_ADDRESS
+
+# Trace configuration
+TRACE_TYPE=permissioned,cannon
+
+# Data directory
+DATADIR=./challenger-data
+
+# Cannon configuration
+# Path to the cannon binary (built from optimism repo)
+CANNON_BIN=/cannon/bin/cannon
+
+# Configuration files
+CANNON_ROLLUP_CONFIG=
+CANNON_L2_GENESIS=
+CANNON_SERVER=/op-program/bin/op-program
+CANNON_PRESTATE=
+EOF
+```
+
+**Important:** Replace ALL placeholder values (`YOUR_ACTUAL_*`) with your real configuration values.
+
+
+### Understanding key configuration flags
+
+
+--l1-eth-rpc
+
+* This is the HTTP provider URL for a standard L1 node, can be a full node. `op-challenger` will be sending many requests, so chain operators need a node that is trusted and can easily handle many transactions.
+* Note: Challenger has a lot of money, and it will spend it if it needs to interact with games. That might risk not defending games or challenging games correctly, so chain operators should really trust the nodes being pointed at Challenger.
+
+
+
+--l1-beacon
+
+* This is needed just to get blobs from.
+* In some instances, chain operators might need a blob archiver or L1 consensus node configured not to prune blobs:
+ * If the chain is proposing regularly, a blob archiver isn't needed. There's only a small window in the blob retention period that games can be played.
+ * If the chain doesn't post a valid output root in 18 days, then a blob archiver running a challenge game is needed. If the actor gets pushed to the bottom of the game, it could lose if it's the only one protecting the chain.
+
+
+
+--l2-eth-rpc
+
+* This needs to be `op-geth` archive node, with `debug` enabled.
+* Technically doesn't need to go to bedrock, but needs to have access to the start of any game that is still in progress.
+
+
+
+--rollup-rpc
+
+* This needs to be an `op-node` archive node because challenger needs access to output roots from back when the games start. See below for important configuration details:
+
+1. Safe Head Database (SafeDB) Configuration for op-node:
+
+ * The `op-node` behind the `op-conductor` must have the SafeDB enabled to ensure it is not stateless.
+
+ * To enable SafeDB, set the `--safedb.path` value in your configuration. This specifies the file path used to persist safe head update data.
+
+ * Example Configuration:
+
+ ```
+ --safedb.path # Replace with your actual path
+ ```
+
+
+ If this path is not set, the SafeDB feature will be disabled.
+
+
+2. Ensuring Historical Data Availability:
+
+ * Both `op-node` and `op-geth` must have data from the start of the games to maintain network consistency and allow nodes to reference historical state and transactions.
+ * For `op-node`: Configure it to maintain a sufficient history of blockchain data locally or use an archive node.
+ * For `op-geth`: Similarly, configure to store or access historical data.
+ * Example Configuration:
+
+ ```
+ op-node \
+ --rollup-rpc \
+ --safedb.path
+ ```
+
+
+ Replace `` with the URL of your archive node and `` with the desired path for storing SafeDB data.
+
+
+
+
+--private-key
+
+* Chain operators must specify a private key or use something else (like `op-signer`).
+* This uses the same transaction manager arguments as `op-node` , batcher, and proposer, so chain operators can choose one of the following options:
+ * a mnemonic
+ * a private key
+ * `op-signer` endpoints
+
+
+
+--network
+
+* This identifies the L2 network `op-challenger` is running for, e.g., `op-sepolia` or `op-mainnet`.
+* 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).
+* 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.
+* 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:
+
+ ```
+ --cannon-rollup-config rollup.json \
+ --cannon-l2-genesis genesis-l2.json \
+ # use this if running challenger outside of the docker image
+ --cannon-server ./op-program/bin/op-program \
+ # json or url, version of op-program deployed on chain
+ # if you use the wrong one, you will lose the game
+ # if you deploy your own contracts, you specify the hash, the root of the json file
+ # op mainnet are tagged versions of op-program
+ # make reproducible prestate
+ # challenger verifies that onchain
+ --cannon-prestate ./op-program/bin/prestate.json \
+ # load the game factory address from system config or superchain registry
+ # point the game factory address at the dispute game factory proxy
+ --game-factory-address
+ ```
+
+
+ These options vary based on which `--network` is specified. Chain operators always need to specify a way to load prestates and must also specify the cannon-server whenever the docker image isn't being used.
+
+
+
+
+--datadir
+
+* This is a directory that `op-challenger` can write to and store whatever data it needs. It will manage this directory to add or remove data as needed under that directory.
+* If running in docker, it should point to a docker volume or mount point, so the data isn't lost on every restart. The data can be recreated if needed but particularly if challenger has executed cannon as part of responding to a game it may mean a lot of extra processing.
+
+
+
+--cannon-prestates-url
+
+The pre-state is effectively the version of `op-program` that is deployed on chain. And chain operators must use the right version. `op-challenger` will refuse to interact with games that have a different absolute prestate hash to avoid making invalid claims. If deploying your own contracts, chain operators must specify an absolute prestate hash taken from the `make reproducible-prestate` command during contract deployment, which will also build the required prestate json file.
+
+All governance approved releases use a tagged version of `op-program`. These can be rebuilt by checking out the version tag and running `make reproducible-prestate`.
+
+* There are two ways to specify the prestate to use:
+ * `--cannon-prestate`: specifies a path to a single Cannon pre-state Json file
+ * `--cannon-prestates-url`: specifies a URL to load pre-states from. This enables participating in games that use different prestates, for example due to a network upgrade. The prestates are stored in this directory named by their hash.
+* Example final URL for a prestate:
+ * [https://example.com/prestates/0x031e3b504740d0b1264e8cf72b6dde0d497184cfb3f98e451c6be8b33bd3f808.json](https://example.com/prestates/0x031e3b504740d0b1264e8cf72b6dde0d497184cfb3f98e451c6be8b33bd3f808.json)
+ * This file contains the cannon memory state.
+
+
+ Challenger will refuse to interact with any games if it doesn't have the matching prestate.
+ Check this [guide](/operators/chain-operators/tutorials/absolute-prestate#generating-the-absolute-prestate) on how to generate a absolute prestate.
+
+
+
+
+
+### Create challenger startup script
+
+Create `scripts/start-challenger.sh`:
+
+```bash
+#!/bin/bash
+source .env
+
+# Path to the challenger binary
+../optimism/op-challenger/bin/op-challenger \
+ --trace-type permissioned,cannon \
+ --l1-eth-rpc=$L1_RPC_URL \
+ --l2-eth-rpc=$L2_RPC_URL \
+ --l1-beacon=$L1_BEACON \
+ --rollup-rpc=$ROLLUP_RPC_URL \
+ --game-factory-address $GAME_FACTORY_ADDRESS \
+ --datadir=$DATADIR \
+ --cannon-bin=$CANNON_BIN \
+ --cannon-rollup-config=$CANNON_ROLLUP_CONFIG \
+ --cannon-l2-genesis=$CANNON_L2_GENESIS \
+ --cannon-server=$CANNON_SERVER \
+ --cannon-prestate=$CANNON_PRESTATE \
+ --mnemonic "$MNEMONIC" \
+ --hd-path "$HD_PATH"
+```
+
+## Initializing and starting the challenger
+
+### Start the challenger
+
+```bash
+# Make sure you're in the challenger-node directory
+cd challenger-node
+
+# Make script executable
+chmod +x scripts/start-challenger.sh
+
+# Start challenger
+./scripts/start-challenger.sh
+```
+
+### Verify challenger is running
+
+Monitor challenger logs to ensure it's operating correctly:
+
+```bash
+# Check challenger logs
+tail -f challenger-data/challenger.log
+
+# Or if running in foreground, monitor the output
+```
+
+The challenger should show logs indicating:
+
+* Successful connection to L1 and L2 nodes
+* Loading of prestates and configuration
+* Monitoring of dispute games
+
+
+
+### Docker Setup
+
+The Docker setup provides a containerized environment for running the challenger. This method uses the official Docker image that includes embedded `op-program` server and Cannon executable.
+
+
+
+### Create environment file
+First, create a `.env` file with your configuration values. This file will be used by Docker Compose to set up the environment variables:
+
+```bash
+# Create .env file with your actual values
+cat > .env << 'EOF'
+# L1 Configuration - Replace with your actual RPC URLs
+L1_RPC_URL=https://sepolia.infura.io/v3/YOUR_ACTUAL_INFURA_KEY
+L1_BEACON=http://sepolia-cl-1:5051
+
+# L2 Configuration - Replace with your actual node endpoints
+L2_RPC_URL=http://localhost:8545
+ROLLUP_RPC_URL=http://localhost:8547
+
+# Wallet configuration - Choose either mnemonic + HD path OR private key
+MNEMONIC="test test test test test test test test test test test junk"
+HD_PATH="m/44'/60'/0'/0/0"
+
+# Network configuration
+NETWORK=op-sepolia
+GAME_FACTORY_ADDRESS=0xYOUR_GAME_FACTORY_ADDRESS
+EOF
+```
+**Important:** Replace ALL placeholder values (`YOUR_ACTUAL_*`) with your real configuration values.
+
+### Understanding configuration flags
+Each environment variable maps to a specific challenger configuration flag. Here's what each one does:
+
+
+--l1-eth-rpc
+
+* This is the HTTP provider URL for a standard L1 node, can be a full node. `op-challenger` will be sending many requests, so chain operators need a node that is trusted and can easily handle many transactions.
+* Note: Challenger has a lot of money, and it will spend it if it needs to interact with games. That might risk not defending games or challenging games correctly, so chain operators should really trust the nodes being pointed at Challenger.
+
+
+
+--l1-beacon
+
+* This is needed just to get blobs from.
+* In some instances, chain operators might need a blob archiver or L1 consensus node configured not to prune blobs:
+ * If the chain is proposing regularly, a blob archiver isn't needed. There's only a small window in the blob retention period that games can be played.
+ * If the chain doesn't post a valid output root in 18 days, then a blob archiver running a challenge game is needed. If the actor gets pushed to the bottom of the game, it could lose if it's the only one protecting the chain.
+
+
+
+--l2-eth-rpc
+
+* This needs to be `op-geth` archive node, with `debug` enabled.
+* Technically doesn't need to go to bedrock, but needs to have access to the start of any game that is still in progress.
+
+
+
+--rollup-rpc
+
+* This needs to be an `op-node` archive node because challenger needs access to output roots from back when the games start. See below for important configuration details:
+
+1. Safe Head Database (SafeDB) Configuration for op-node:
+
+ * The `op-node` behind the `op-conductor` must have the SafeDB enabled to ensure it is not stateless.
+
+ * To enable SafeDB, set the `--safedb.path` value in your configuration. This specifies the file path used to persist safe head update data.
+
+ * Example Configuration:
+
+ ```
+ --safedb.path # Replace with your actual path
+ ```
+
+
+ If this path is not set, the SafeDB feature will be disabled.
+
+
+2. Ensuring Historical Data Availability:
+
+ * Both `op-node` and `op-geth` must have data from the start of the games to maintain network consistency and allow nodes to reference historical state and transactions.
+ * For `op-node`: Configure it to maintain a sufficient history of blockchain data locally or use an archive node.
+ * For `op-geth`: Similarly, configure to store or access historical data.
+ * Example Configuration:
+
+ ```
+ op-node \
+ --rollup-rpc \
+ --safedb.path
+ ```
+
+
+ Replace `` with the URL of your archive node and `` with the desired path for storing SafeDB data.
+
+
+
+
+--private-key
+
+* Chain operators must specify a private key or use something else (like `op-signer`).
+* This uses the same transaction manager arguments as `op-node` , batcher, and proposer, so chain operators can choose one of the following options:
+ * a mnemonic
+ * a private key
+ * `op-signer` endpoints
+
+
+
+--network
+
+* This identifies the L2 network `op-challenger` is running for, e.g., `op-sepolia` or `op-mainnet`.
+* 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).
+* 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.
+* 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:
+
+ ```
+ --cannon-rollup-config rollup.json \
+ --cannon-l2-genesis genesis-l2.json \
+ # use this if running challenger outside of the docker image
+ --cannon-server ./op-program/bin/op-program \
+ # json or url, version of op-program deployed on chain
+ # if you use the wrong one, you will lose the game
+ # if you deploy your own contracts, you specify the hash, the root of the json file
+ # op mainnet are tagged versions of op-program
+ # make reproducible prestate
+ # challenger verifies that onchain
+ --cannon-prestate ./op-program/bin/prestate.json \
+ # load the game factory address from system config or superchain registry
+ # point the game factory address at the dispute game factory proxy
+ --game-factory-address
+ ```
+
+
+ These options vary based on which `--network` is specified. Chain operators always need to specify a way to load prestates and must also specify the cannon-server whenever the docker image isn't being used.
+
+
+
+
+--datadir
+
+* This is a directory that `op-challenger` can write to and store whatever data it needs. It will manage this directory to add or remove data as needed under that directory.
+* If running in docker, it should point to a docker volume or mount point, so the data isn't lost on every restart. The data can be recreated if needed but particularly if challenger has executed cannon as part of responding to a game it may mean a lot of extra processing.
+
+
+
+--cannon-prestates-url
+
+The pre-state is effectively the version of `op-program` that is deployed on chain. And chain operators must use the right version. `op-challenger` will refuse to interact with games that have a different absolute prestate hash to avoid making invalid claims. If deploying your own contracts, chain operators must specify an absolute prestate hash taken from the `make reproducible-prestate` command during contract deployment, which will also build the required prestate json file.
+
+All governance approved releases use a tagged version of `op-program`. These can be rebuilt by checking out the version tag and running `make reproducible-prestate`.
+
+* There are two ways to specify the prestate to use:
+ * `--cannon-prestate`: specifies a path to a single Cannon pre-state Json file
+ * `--cannon-prestates-url`: specifies a URL to load pre-states from. This enables participating in games that use different prestates, for example due to a network upgrade. The prestates are stored in this directory named by their hash.
+* Example final URL for a prestate:
+ * [https://example.com/prestates/0x031e3b504740d0b1264e8cf72b6dde0d497184cfb3f98e451c6be8b33bd3f808.json](https://example.com/prestates/0x031e3b504740d0b1264e8cf72b6dde0d497184cfb3f98e451c6be8b33bd3f808.json)
+ * This file contains the cannon memory state.
+
+
+ Challenger will refuse to interact with any games if it doesn't have the matching prestate.
+ Check this [guide](/operators/chain-operators/tutorials/absolute-prestate#generating-the-absolute-prestate) on how to generate a absolute prestate.
+
+
+
+### Set up Docker Compose
+Create a `docker-compose.yml` file that defines the challenger service:
+
+```yaml
+version: '3.8'
+
+services:
+ challenger:
+ image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-challenger:v1.5.0
+ user: "1000"
+ volumes:
+ - ./challenger-data:/data
+ - ./rollup.json:/workspace/rollup.json:ro
+ - ./genesis-l2.json:/workspace/genesis-l2.json:ro
+ environment:
+ - L1_RPC_URL=${L1_RPC_URL}
+ - L1_BEACON=${L1_BEACON}
+ - L2_RPC_URL=${L2_RPC_URL}
+ - ROLLUP_RPC_URL=${ROLLUP_RPC_URL}
+ - MNEMONIC=${MNEMONIC}
+ - HD_PATH=${HD_PATH}
+ - NETWORK=${NETWORK}
+ - GAME_FACTORY_ADDRESS=${GAME_FACTORY_ADDRESS}
+ command:
+ - "op-challenger"
+ - "--l1-eth-rpc=${L1_RPC_URL}"
+ - "--l1-beacon=${L1_BEACON}"
+ - "--l2-eth-rpc=${L2_RPC_URL}"
+ - "--rollup-rpc=${ROLLUP_RPC_URL}"
+ - "--selective-claim-resolution"
+ - "--mnemonic=${MNEMONIC}"
+ - "--hd-path=${HD_PATH}"
+ - "--network=${NETWORK}"
+ - "--game-factory-address=${GAME_FACTORY_ADDRESS}"
+ - "--datadir=/data"
+ - "--cannon-prestate=/workspace/prestate-proof.json"
+ restart: unless-stopped
+ ports:
+ - "8548:8548" # If challenger exposes metrics endpoint
+```
+
+### Launch the challenger
+Start the challenger service and monitor its logs:
+
+```bash
+# Start the challenger service
+docker-compose up -d
+
+# View logs
+docker-compose logs -f challenger
+```
+
+
+
+
+
+
+### Monitoring with op-dispute-mon
+
+Consider running [`op-dispute-mon`](/operators/chain-operators/tools/chain-monitoring#dispute-mon) for enhanced security monitoring:
+
+* Provides visibility into all game statuses for the last 28 days
+* Essential for production challenger deployments
+* Create Grafana dashboards using: [Download the Dispute Monitor JSON](/resources/grafana/dispute-monitor-1718214549035.json)
+
+## Next steps
+
+* Read the [OP-Challenger Explainer](/stack/fault-proofs/challenger) for additional context and FAQ
+* Review the detailed [challenger specifications](https://specs.optimism.io/fault-proof/stage-one/honest-challenger-fdg.html) for implementation details
+* If you experience any problems, reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions)
diff --git a/pages/operators/chain-operators/deploy/proposer-setup-guide.mdx b/pages/operators/chain-operators/deploy/proposer-setup-guide.mdx
index 734d9771a..6b620580f 100644
--- a/pages/operators/chain-operators/deploy/proposer-setup-guide.mdx
+++ b/pages/operators/chain-operators/deploy/proposer-setup-guide.mdx
@@ -111,7 +111,7 @@ cd proposer-node
cp ../.deployer/state.json .
# Extract the DisputeGameFactory address
-GAME_FACTORY_ADDRESS=$(cat state.json | jq -r '.opChainDeployments[0].disputeGameFactoryProxyAddress')
+GAME_FACTORY_ADDRESS=$(cat state.json | jq -r '.opChainDeployments[0].DisputeGameFactoryProxy')
echo "DisputeGameFactory Address: $GAME_FACTORY_ADDRESS"
```
diff --git a/pages/operators/chain-operators/tools.mdx b/pages/operators/chain-operators/tools.mdx
index d46a54afa..1952fdf2a 100644
--- a/pages/operators/chain-operators/tools.mdx
+++ b/pages/operators/chain-operators/tools.mdx
@@ -32,12 +32,8 @@ This section provides information on chain monitoring options, deploying a block
-
-
-
-
diff --git a/pages/operators/chain-operators/tools/op-challenger.mdx b/pages/operators/chain-operators/tools/op-challenger.mdx
deleted file mode 100644
index 7d7f8c025..000000000
--- a/pages/operators/chain-operators/tools/op-challenger.mdx
+++ /dev/null
@@ -1,234 +0,0 @@
----
-title: How to configure challenger for your chain
-description: Learn how to configure challenger for your OP Stack chain.
-lang: en-US
-content_type: tutorial
-topic: configure-challenger-for-your-chain
-personas:
- - chain-operator
-categories:
- - mainnet
- - testnet
- - fault-proofs
- - op-challenger
- - chain-configuration
-is_imported_content: 'false'
----
-
-import { Callout, Steps } from 'nextra/components'
-
-# How to configure challenger for your chain
-
-This guide provides a walkthrough of setting up the configuration and monitoring options for `op-challenger`. See the [OP-Challenger Explainer](/stack/fault-proofs/challenger) for a general overview of this fault proofs feature.
-
-
- ### Build the executable
-
- * Clone the monorepo
-
- ```bash
- git clone https://github.com/ethereum-optimism/optimism.git
- ```
-
- * Check out the [latest release of `op-challenger`](https://github.com/ethereum-optimism/optimism/releases) and use the commit to deploy. Alternatively, chain operators can use the prebuilt challenger docker images included in the release notes.
- If a Docker image is used, it already comes with `op-program` server and an executable for Cannon embedded, so the Cannon bin doesn't need to be specified.
-
- ```bash
- git checkout op-challenger/vX.Y.Z
- ```
-
-
- Chain operators need to specify the arguments and `op-program` server if `op-challenger` is running outside of Docker, but there's a Cannon server option which points to `op-program`'s executable.
-
-
- * Build challenger
-
- ```bash
- cd optimism
- pnpm install
- make op-challenger
- ```
-
- ### Configure challenger
-
- * Configure challenger with the required flags. Tip: Use the `op-challenger --help` to view all subcommands, command line, and environment variable options.
- * The example config file below shows the flags to configure in this step:
-
- ```docker
- challenger:
- user: "1000"
- image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-challenger:v0.2.11
- command:
- - "op-challenger"
- - "--l1-eth-rpc=http://sepolia-el-1:8545"
- - "--l1-beacon=http://sepolia-cl-1:5051"
- - "--l2-eth-rpc=http://op-sepolia-el-1:8545"
- - "--rollup-rpc=http://op-sepolia-cl-1:5051"
- - "--selective-claim-resolution"
- - "--private-key=...."
- - "--network=..."
- - "--datadir=/data"
- - "--cannon-prestates-url=..."
- volumes:
- - "./challenger-data:/data"
- ```
-
- #### `--l1-eth-rpc`
-
- * This is the HTTP provider URL for a standard L1 node, can be a full node. `op-challenger` will be sending many requests, so chain operators need a node that is trusted and can easily handle many transactions.
- * Note: Challenger has a lot of money, and it will spend it if it needs to interact with games. That might risk not defending games or challenging games correctly, so chain operators should really trust the nodes being pointed at Challenger.
-
- #### `--l1-beacon`
-
- * This is needed just to get blobs from.
- * In some instances, chain operators might need a blob archiver or L1 consensus node configured not to prune blobs:
- * If the chain is proposing regularly, a blob archiver isn't needed. There's only a small window in the blob retention period that games can be played.
- * If the chain doesn't post a valid output root in 18 days, then a blob archiver running a challenge game is needed. If the actor gets pushed to the bottom of the game, it could lose if it's the only one protecting the chain.
-
- #### `--l2-eth-rpc`
-
- * This needs to be `op-geth` archive node, with `debug` enabled.
- * Technically doesn't need to go to bedrock, but needs to have access to the start of any game that is still in progress.
-
- #### `--rollup-rpc`
-
- * This needs to be an `op-node` archive node because challenger needs access to output roots from back when the games start. See below for important configuration details:
-
- 1. Safe Head Database (SafeDB) Configuration for op-node:
-
- * The `op-node` behind the `op-conductor` must have the SafeDB enabled to ensure it is not stateless.
- * To enable SafeDB, set the `--safedb.path` value in your configuration. This specifies the file path used to persist safe head update data.
- * Example Configuration:
-
- ```
- --safedb.path # Replace with your actual path
- ```
-
-
- If this path is not set, the SafeDB feature will be disabled.
-
-
- 2. Ensuring Historical Data Availability:
-
- * Both `op-node` and `op-geth` must have data from the start of the games to maintain network consistency and allow nodes to reference historical state and transactions.
- * For `op-node`: Configure it to maintain a sufficient history of blockchain data locally or use an archive node.
- * For `op-geth`: Similarly, configure to store or access historical data.
- * Example Configuration:
-
- ```
- op-node \
- --rollup-rpc \
- --safedb.path
- ```
-
-
- Replace `` with the URL of your archive node and `` with the desired path for storing SafeDB data.
-
-
- #### `--private-key`
-
- * Chain operators must specify a private key or use something else (like `op-signer`).
- * This uses the same transaction manager arguments as `op-node` , batcher, and proposer, so chain operators can choose one of the following options:
- * a mnemonic
- * a private key
- * `op-signer` endpoints
-
- #### `--network`
-
- * This identifies the L2 network `op-challenger` is running for, e.g., `op-sepolia` or `op-mainnet`.
- * 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).
- * 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.
- * 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:
-
- ```
- --cannon-rollup-config rollup.json \
- --cannon-l2-genesis genesis-l2.json \
- # use this if running challenger outside of the docker image
- --cannon-server ./op-program/bin/op-program \
- # json or url, version of op-program deployed on chain
- # if you use the wrong one, you will lose the game
- # if you deploy your own contracts, you specify the hash, the root of the json file
- # op mainnet are tagged versions of op-program
- # make reproducible prestate
- # challenger verifies that onchain
- --cannon-prestate ./op-program/bin/prestate.json \
- # load the game factory address from system config or superchain registry
- # point the game factory address at the dispute game factory proxy
- --game-factory-address
- ```
-
-
- These options vary based on which `--network` is specified. Chain operators always need to specify a way to load prestates and must also specify the cannon-server whenever the docker image isn't being used.
-
-
- #### `--datadir`
-
- * This is a directory that `op-challenger` can write to and store whatever data it needs. It will manage this directory to add or remove data as needed under that directory.
- * If running in docker, it should point to a docker volume or mountpoint, so the data isn't lost on every restart. The data can be recreated if needed but particularly if challenger has executed cannon as part of responding to a game it may mean a lot of extra processing.
-
- #### `--cannon-prestates-url`
-
- The pre-state is effectively the version of `op-program` that is deployed on chain. And chain operators must use the right version. `op-challenger` will refuse to interact with games that have a different absolute prestate hash to avoid making invalid claims. If deploying your own contracts, chain operators must specify an absolute prestate hash taken from the `make reproducible-prestate` command during contract deployment, which will also build the required prestate json file.
-
- All governance approved releases use a tagged version of `op-program`. These can be rebuilt by checking out the version tag and running `make reproducible-prestate`.
-
- * There are two ways to specify the prestate to use:
- * `--cannon-prestate`: specifies a path to a single Cannon pre-state Json file
- * `--cannon-prestates-url`: specifies a URL to load pre-states from. This enables participating in games that use different prestates, for example due to a network upgrade. The prestates are stored in this directory named by their hash.
- * Example final URL for a prestate:
- * [https://example.com/prestates/0x031e3b504740d0b1264e8cf72b6dde0d497184cfb3f98e451c6be8b33bd3f808.json](https://example.com/prestates/0x031e3b504740d0b1264e8cf72b6dde0d497184cfb3f98e451c6be8b33bd3f808.json)
- * This file contains the cannon memory state.
-
-
- Challenger will refuse to interact with any games if it doesn't have the matching prestate.
-
-
- ### Execute challenger
-
- The final step is to execute challenger with the required flags. It will look something like this (but with required flags added):
-
- ```bash
- ./op-challenger/bin/op-challenger \
- --trace-type permissioned,cannon \
- --l1-eth-rpc http://localhost:8545 \
- --rollup-rpc http://localhost:9546 \
- --game-factory-address $DISPUTE_GAME_FACTORY \
- --datadir temp/challenger-data \
- --cannon-rollup-config .devnet/rollup.json \
- --cannon-l2-genesis .devnet/genesis-l2.json \
- --cannon-bin ./cannon/bin/cannon \
- --cannon-server ./op-program/bin/op-program \
- --cannon-prestate ./op-program/bin/prestate.json \
- --l2-eth-rpc http://localhost:9545 \
- --mnemonic "test test test test test test test test test test test junk" \
- --hd-path "m/44'/60'/0'/0/8" \
- ```
-
- ### Test and debug challenger (optional)
-
- This is an optional step to use `op-challenger` subcommands, which allow chain operators to interact with the Fault Proof System onchain for testing and debugging purposes. For example, it is possible to test and explore the system in the following ways:
-
- * create games yourself, and it doesn't matter if the games are valid or invalid.
- * perform moves in games and then claim and resolve things.
-
- Here's the list of op-challenger subcommands:
-
- | subcommand | description |
- | --------------- | -------------------------------------------------------- |
- | `list-games` | List the games created by a dispute game factory |
- | `list-claims` | List the claims in a dispute game |
- | `list-credits` | List the credits in a dispute game |
- | `create-game` | Creates a dispute game via the factory |
- | `move` | Creates and sends a move transaction to the dispute game |
- | `resolve` | Resolves the specified dispute game if possible |
- | `resolve-claim` | Resolves the specified claim if possible |
-
- Additionally, chain operators should consider running `op-dispute-mon`. It's an incredibly useful security monitoring service to keep an eye on games, basically giving chain operators visibility into all the status of the games for the last 28 days.
- Chain operators can easily create their grafana dashboard for Dispute Monitor using the following json file: [Download the Dispute Monitor JSON](/resources/grafana/dispute-monitor-1718214549035.json).
-
-
-## Next steps
-
-* Additional questions? See the FAQ section in the [OP Challenger Explainer](/stack/fault-proofs/challenger).
-* For more detailed info on `op-challenger`, see the [specs](https://specs.optimism.io/fault-proof/stage-one/honest-challenger-fdg.html?utm_source=op-docs&utm_medium=docs).
-* If you experience any problems, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions).
diff --git a/pages/stack/fault-proofs/challenger.mdx b/pages/stack/fault-proofs/challenger.mdx
index 06f6e7d1a..c9088135c 100644
--- a/pages/stack/fault-proofs/challenger.mdx
+++ b/pages/stack/fault-proofs/challenger.mdx
@@ -101,7 +101,7 @@ The `FaultDisputeGame` does not put a time cap on resolution - because of the li
## Next steps
-* Ready to get started? Read our guide on how to [configure `op-challenger` on your OP Stack chain](/operators/chain-operators/tools/op-challenger).
+* Ready to get started? Read our guide on how to [configure `op-challenger` on your OP Stack chain](/operators/chain-operators/deploy/op-challenger).
* For more info about how `op-challenger` works under the hood, [check out the specs](https://specs.optimism.io/fault-proof/stage-one/honest-challenger-fdg.html?utm_source=op-docs&utm_medium=docs).
## FAQs
diff --git a/pages/stack/fault-proofs/explainer.mdx b/pages/stack/fault-proofs/explainer.mdx
index 52eefd5c0..19960474e 100644
--- a/pages/stack/fault-proofs/explainer.mdx
+++ b/pages/stack/fault-proofs/explainer.mdx
@@ -96,7 +96,7 @@ Users would generally just propose a single output root if they need to withdraw
The [`create-game`](https://github.com/ethereum-optimism/optimism/tree/develop/op-challenger#create-game) subcommand of `op-challenger` is **for testing purposes only** and should not be used in production environments. It is not intended as a replacement for proper `op-proposer` infrastructure.
-For detailed guidance on running `op-challenger`, see the [OP-Challenger explainer](/stack/fault-proofs/challenger) and [how to configure challenger for your chain](/operators/chain-operators/tools/op-challenger).
+For detailed guidance on running `op-challenger`, see the [OP-Challenger explainer](/stack/fault-proofs/challenger) and [how to configure challenger for your chain](/operators/chain-operators/deploy/op-challenger).
### How much ETH should a chain operator put aside to operate the Fault Proof System?
diff --git a/public/_redirects b/public/_redirects
index 826a3dd7d..252eb6d7b 100644
--- a/public/_redirects
+++ b/public/_redirects
@@ -81,6 +81,8 @@
/operators/node-operators/tutorials/testnet /operators/node-operators/tutorials/run-node-from-source
/stack/dev-net /chain-operators/tutorials/chain-dev-net
+/operators/chain-operators/tools/op-challenger /operators/chain-operators/deploy/op-challenger
+
# ----------------------------------------------------------------------------
# Stack Documentation Migration
# ----------------------------------------------------------------------------
diff --git a/words.txt b/words.txt
index 05708699c..73d3392c3 100644
--- a/words.txt
+++ b/words.txt
@@ -224,7 +224,6 @@ Monitorism
monitorism
Moralis
Mordor
-mountpoint
MOVN
MOVZ
MTHI